Skip to content

Add start depth for pocket operations - #157

Open
DarkBiscuits wants to merge 1 commit into
mountainarcwelding:mainfrom
DarkBiscuits:codex/pocket-start-depth
Open

DarkBiscuits wants to merge 1 commit into
mountainarcwelding:mainfrom
DarkBiscuits:codex/pocket-start-depth

Conversation

@DarkBiscuits

Copy link
Copy Markdown
Contributor

Refs #88.

Adds optional start_depth to campanion-job/1 pocket operations, measured downward from the original stock surface in job units. For start_depth: 3, depth: 8 and step_down: 2, pocket passes cut at Z -5, -7 and -8. The final depth retains its existing meaning. Omitting the field or setting it to zero preserves existing output; other operation kinds reject it.

Both pocket area passes and wall-finishing passes use the remaining depth interval. Floor stock and onion skins stay referenced to the original final floor. Invalid starts, starts at or below the roughing stop, and excessive remaining pass counts are rejected. Finishing-only continuation is outside this scope.

Clearance and retract heights stay unchanged. Plunge, ramp and helix entries still feed from the configured retract height, with entry-angle and fit checks preserved. The caller must ensure the pocket area has already been cleared to start_depth; this field does not infer remaining stock or add rapids below the retract height.

Validation: scripts/check.sh passes (formatting, Clippy, workspace tests, wasm and license checks). New coverage includes an analytic NC golden, randomized remaining-interval checks, roughing/floor/wall finishing, onion skins, inch conversion, ramp/helix slopes including a zero retract height, invalid input and pass limits, rejection on other operation kinds, and unchanged output at zero start depth. CLI output also passes read-back, modal audit and IR verification. Existing golden files are unchanged.

DarkBiscuits, co-authored with Codex. Implemented from CAMpanion's own sources and synthetic fixtures. No physical machining tests have been performed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant