feat(cutting): route around tabbed parts before passing over them

A tabbed part stays in the sheet, so rapids were free to pass over it and
the planner never looked for a way around. Plan Cutting now searches first
with every tabbed outside as an obstacle once its part is cut. Where a pass
stalls at a part whose approach crosses a tabbed part, only the crossed
parts become crossable and the search goes on along the same order. A
capture that search cannot plan is planned as before. Plates without
tabbed outsides are searched once, unchanged.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
ajandClaude Fable 5.2 committed 2026-11-16 20:00:50 -05:00
1 parent a84f8d1298
commit 92bf653c8f
9 files changed
+305 -16

No files matched your search

+25 -1
View File
@@ -39,7 +39,7 @@ var result = CuttingPlanService.Plan(snapshot, cancellationToken);
the plate's own under `ForPlate`), each regenerated part the bed cannot hold level gets a
tabbed perimeter whose automatic entries prefer points where the tab steadies it. A tabbed
part counts as steady wherever its tab is: it is never warned about and stays crossable once
cut. A tab in an inside corner is noted on the plan without changing its status. A part no
cut, though the plan [goes around it where it can](#tabbed-parts-are-avoided-first). A tab in an inside corner is noted on the plan without changing its status. A part no
longer than `TabHeldMaxLength` is held by its tab
alone, so any tab clear of inside corners steadies it. Without a bed, or with
`CuttingParameters.TabBySize`, the parts whose width is in `TabSizeMinWidth`..`TabSizeMaxWidth`
@@ -294,6 +294,30 @@ expansion budget; exhausting it still returns a refusal from the service, never
best-effort upgrade. Only the batch then looks for the separate
[safest route](#safest-route-fallback-when-the-search-runs-out).
### Tabbed parts are avoided first
A tabbed part stays in the sheet, so a rapid may pass over it, but a route around it is safer.
When any regenerated part's outside is tabbed (support tabs or the settings' own tabs),
`CuttingPlanService.Plan` first searches with every tabbed outside as an obstacle once its part
is cut, closed across its tab gap (`CuttingPlanSnapshot.WithTabbedPartsAvoided`,
`ReleasedContourState.AvoidTabbedPart`). Entry backtracking then leaves a tabbed part on a
side that clears it, where its catalog has one.
A pass along the order that stalls at a part whose approach crosses a tabbed part still avoided
makes just the crossed parts crossable (`CuttingPlanSnapshot.CrossableTabbedParts`) and goes on
from there along the same order. It learns no order rule from a tabbed part: on a plate of
tabbed parts, reordering around each one spent the whole budget without finding a plan. So a
tabbed part is passed over only where no entry of the parts on that order avoids it, typically
a part whose only level-holding tab point faces away from the next cut. The checkers of that
search, cut-off placement and the independent replay all read the same set, so the replayed
plan is the one searched. Its hard obstacles are unchanged: a tabbed part's holes, parts cut
free, and tabbed outsides whose lead-out may cut the tab free.
A capture this search cannot plan is planned again as before, with every tabbed part crossable.
The desktop batch's short first pass is kept only when it passed over no tabbed part; otherwise
the full pass looks for a route around them. The safest-route fallback and the pre-post review
do not avoid tabbed parts. A plate with no tabbed outside is searched once, exactly as before.
### Cutoff segments
A cutoff segment is a fixed open cut that is cut the same way wherever it goes and is
+3 -1
View File
@@ -184,7 +184,9 @@ its steadying entries.
A tabbed part counts as steady wherever its tab is: the steadiest entries above are preferences,
never a warning. No message says a tab cannot steady its part, and once cut a tabbed part stays
crossable, as its retained material allows, whether or not its tab holds it level. The pre-post
crossable, as its retained material allows, whether or not its tab holds it level. Plan Cutting
still routes around tabbed parts where it can and passes over only those it finds no way around
(see [tabbed parts are avoided first](cutting-planner.md#tabbed-parts-are-avoided-first)). The pre-post
review does not read support settings for rapids, so it checks rapid crossings against untabbed
contours only.