---
name: project-rebar-pipeline-program
description: User plans to build a program that generates rebar (DXF drawings → Rhino rebar → audit → material-table DXF); full validated method saved in rebar_pipeline/ folder
metadata:
  node_type: memory
  type: project
  originSessionId: 888d28a0-dc6f-4081-9e33-fb12bd0121be
  modified: 2026-10-02T03:08:53.758Z
---

User (2026-10-02) asked to save the entire workflow because they intend to **build a program that generates rebar this way** later.

Saved at `D:\Rhino-MCP\rhino-mcp-main\rebar_pipeline\`:
- `README.md` — full method: environment limits, DXF reading (awk), material-table rules (V형 L=2A+2B+2C, 할증/겹이음 6.80%, unit weights), coping local frame + section, offset-120 centerline construction, KDS fillet+pipe, block/color rules, audit (isocurve centerline, LineLine virtual corners, BrepFace.PointAt cover sampling, box lid/base/lap measurement), R12 CP949 table writer, proposed module split.
- `awk/txt.awk, geo.awk, ins.awk` — DXF text / line / insert extractors.
- `rhino/01_section_profile.py, 02_build_shape_VII.py, 03_audit.py, 04_table_writer.py` — validated IronPython snippets.

**Why:** these were hard-won in sessions on 대호지교 P1 ([[project_p1_pier_structure]]); the program should reuse them rather than re-derive.
**How to apply:** when the user starts the program or any new pier/bridge rebar job, read that README first and extend the scripts; update the README whenever a new method is validated. Related: [[feedback_kds_rebar_bend_radius]], [[feedback_ironpython_exec_scoping]], [[feedback_coping_haunch_rebar_method]].