feat(cam): eta3 blend geometry in scene dump and viewer #97
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "patman/cam-blend-viz"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR 2/2 (UI round 3, base = PR 1/2). First visualization of the G3 blends: nonzero blend corridors chosen per tool radius (1um for r=0.5mm scenes a/b, 4um for r=1.0mm scene c) so plan_rings certifies engagement for blended execution with the exact corridor blend_pass is gated against. Emits per-pass blendPts polylines (8 samples/blend, 10um grid) + blendCorridorM/blendCount; viewer renders mint G3-blend ribbons (ribbonHw*1.4) with cut-progress dim states, legend + HUD count. Measured visibility: ~15px at default zoom on scene c, no exaggeration. Pass-count deltas from corridor cost: a 430->469, b 620->795, c 61->68 (scene stories preserved by tests). KNOWN LIMITATION documented in-code: cam_blend seam_matches debug-assert panics on scene d acute-corner ring geometry at ANY corridor magnitude, so scene d ships corridor ZERO via a skip_blends guard; cam_blend follow-up issue filed. a/b dumps now ~1.6MB (blend data + corridor pass growth). cam-blend dep in both manifests. Full //CAM/... suite 8/8 green.