Profile operations (extrude/revolve) are derived but never exported to STEP/FCStd #6

New issue

Closed

opened 2026-06-10 15:42:29 +00:00 by Mark · 2 comments

Mark commented

2026-06-10 15:42:29 +00:00

Owner

See evaluation notes. Details to be expanded.

Mark

2026-06-10 15:42:38 +00:00

closed this issue
added the
triage-approved

bug

quickfix

blocked:needs-decision
labels

Mark reopened this issue

2026-06-17 18:22:53 +00:00

Mark commented

2026-06-17 18:23:19 +00:00

Author

Owner

Audit (reopened)

Reopened this issue. It was closed with quickfix + bug + triage-approved + blocked:needs-decision labels but with no close comment and no matching commit on main. Profile operations (extrude/revolve) being derived but not exported to STEP/FCStd is a real gap — I see profile extraction code in pc2cad.py but no path through export_step() / export_fcstd() that includes profiles as features.

Reopening so the export path can be added. Likely scope: pass section_profiles and profile_features through to the FreeCAD/build123d exporter and apply them as additional solids or cuts.

## Audit (reopened) Reopened this issue. It was closed with `quickfix + bug + triage-approved + blocked:needs-decision` labels but with no close comment and no matching commit on `main`. Profile operations (extrude/revolve) being derived but not exported to STEP/FCStd is a real gap — I see profile extraction code in `pc2cad.py` but no path through `export_step()` / `export_fcstd()` that includes profiles as features. Reopening so the export path can be added. Likely scope: pass `section_profiles` and `profile_features` through to the FreeCAD/build123d exporter and apply them as additional solids or cuts.

Mark referenced this issue

2026-06-17 18:24:23 +00:00

Refine pc2cad strategy: end-to-end ply → editable CAD pipeline review #15

Mark referenced this issue

2026-06-17 18:25:49 +00:00

Child of #15: mechanical reconstruction path (feature-based, the core path) #17

Mark removed the

quickfix

label

2026-06-17 20:03:30 +00:00

Mark referenced this issue

2026-06-18 19:29:48 +00:00

Child of #17: auto-extract 2D profile from segmented planar/axial point regions (prismatic + turned parts) #22

Mark commented

2026-06-18 19:30:03 +00:00

Author

Owner

Scope split (with #22)

To keep this issue tractable and prevent future confusion, splitting the profile work into two concerns:

#6 (this issue) — export-side fix. Profile extraction code already exists in pc2cad.py; the gap is the path from the derived section_profiles / profile_features through export_step() and export_fcstd(). Fix: pass the profiles through to the exporter, emit them as additional solids (for extrudes) or swept solids (for revolves) on top of the RANSAC-fitted primitives.
#22 — upstream profile extraction from segmented point regions. Wider scope: given a planar or axisymmetric point region (output of #11), recover a Sketch + sweep operation entirely from the points, including the prismatic vs revolved classification. This is the "scanning app" version of the work — no user-supplied cross-section, no user-supplied CAD.

#22 is the parent-of-#17 work that generates the profiles; #6 is the consumer that emits them. Both must land for the mechanical path (#17) to be feature-complete, but they are independent and can be worked in parallel. The integration test (synthetic L-bracket end-to-end → STEP opens in FreeCAD) lives on #22's acceptance list.

## Scope split (with #22) To keep this issue tractable and prevent future confusion, splitting the profile work into two concerns: - **#6 (this issue) — export-side fix.** Profile extraction code already exists in `pc2cad.py`; the gap is the path from the derived `section_profiles` / `profile_features` through `export_step()` and `export_fcstd()`. Fix: pass the profiles through to the exporter, emit them as additional solids (for extrudes) or swept solids (for revolves) on top of the RANSAC-fitted primitives. - **#22 — upstream profile extraction from segmented point regions.** Wider scope: given a planar or axisymmetric point region (output of #11), recover a `Sketch` + sweep operation *entirely from the points*, including the prismatic vs revolved classification. This is the "scanning app" version of the work — no user-supplied cross-section, no user-supplied CAD. #22 is the parent-of-#17 work that *generates* the profiles; #6 is the *consumer* that emits them. Both must land for the mechanical path (#17) to be feature-complete, but they are independent and can be worked in parallel. The integration test (synthetic L-bracket end-to-end → STEP opens in FreeCAD) lives on #22's acceptance list.

Mark

2026-06-19 15:59:14 +00:00