Skip to content

Design code chapters

RC / steel / SRC design-code chapters (ch24-27) live under midas_nx.design — a different namespace from /db/*, mixing DbResource-style config/member-CRUD endpoints with plain POST-action functions (design-execution/table/report/image) that reuse post/base.py's NodeElemsSelector/TableUnit/TableStyles.

See ROADMAP.md for the full per-chapter endpoint list.

Steel KDS 41 30:2022 (ch25)

midas_nx.design.steel_kds

Source: docs/manual/25_Design_Steel_KDS41302022.md, items 1-27.

Steel design code KDS 41 30:2022 — setup, per-member design parameters, material overrides, and design-execution/result endpoints. Endpoint prefix: /DESIGN/STEEL/KDS-41-30-2022/<CODE> (not /db/*).

The manual documents 3 method patterns and 4 endpoint groups (see the chapter's own intro section):

  1. Config-singleton (그룹 1/3 mostly) — no POST; PUT sets/updates the one record. Most of these use GET_PUT_DELETE_METHODS; LCTB is GET/DELETE-only (GET_DELETE_METHODS).
  2. Member-CRUD (그룹 2, plus a few 그룹 1 endpoints) — full POST/GET/PUT/ DELETE, ID-keyed by element/member (the DbResource default).
  3. POST-action (그룹 4) — design-execution/result-table/report/image endpoints; POST only, "Argument"-wrapped (not ID-keyed "Assign"), implemented as plain functions via post_argument (mirrors post/design.py and ope.py/view.py for deeply-nested bodies).

SteelDesignCodeOption

Bases: DbResource

perform_steel_code_check(argument, client=None)

docs/manual/25_Design_Steel_KDS41302022.md #23 — CODE-ANAL — Steel Code Check Perform. Executes the design calculation; response is {"message": "success"} on success.

⚠️ Never independently tested. The RC equivalent (design.rc_kds.checks.perform_column_check, CC-ANAL) was confirmed to hang Gen NX 2026 (v2.1), build 06/23/2026 (stuck at "Converting Design Results... 0%", required a forced process kill), then ran clean on that same build on 2026-07-25 — the trigger is unidentified, not fixed; see docs/live_verification_notes.md. Every test on both sides used the KDS 41 20:2022 RC code, so nothing is confirmed either way for this steel-code path. Use a short timeout and read get_steel_code_check_table regardless of whether this call returns.

get_steel_code_check_table(argument, client=None)

docs/manual/25_Design_Steel_KDS41302022.md #24 — CODE-TABLE — Steel Code Check Table. Response: {table_name_or_"Result Table": {"FORCE": ..., "DIST": ..., "HEAD": [...], "DATA": [[...], ...]}}.

RC KDS 41 20:2022 (ch26)

design/rc_kds/ splits the largest chapter in the project into four files by natural endpoint-group boundary — setup.py, rebar.py, design_forces.py, checks.py — following the same DbResource-class / plain-function split as steel_kds.py.

SRC AIK-SRC2K (ch27)

design/src_aiksrc2k.py mirrors the same DCO/DCTL/LLRF/... setup + check-triplet structure, kept fully self-contained (no cross-chapter TypedDict reuse with steel_kds.py/rc_kds/*).