mirror of
https://github.com/ajisaacs/OpenNest.git
synced 2026-11-17 08:43:54 -05:00
fix(geometry): let parts push off a frame whose contour misses closing by 1e-6
PEP-rounded drawings can leave a contour 1e-6 short of closing. ShapeBuilder chains it as a loop at Tolerance.ChainTolerance, but the slide classifier re-recovered loops at 1e-7, so the whole part became unresolved and every contact with it blocked. Parts placed in its cutout at exactly the part spacing could not be pushed (Y/X keys) in any direction, even away from the wall. Recover loops with the same tolerance ShapeBuilder uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c6b6678a2f
commit
b8e8cc387d
3 files changed
+40
-2
No files matched your search
@@ -6,7 +6,7 @@ For initially non-overlapping closed material boundaries, a directional slide st
|
||||
|
||||
`SpatialQuery.DirectionalDistance` overloads and CPU best-fit batches use the same event sources and contact resolver. Events carry both contact points in their initial world frames, rather than only a snapped distance. The classifier uses closed-loop material sectors, native-curve containment for hole depth, and the curvature of the supporting boundary at a tangential contact. A full-circle arc has no physical corner at its seam. Raw ray helpers remain first-touch primitives, not material-aware slide queries.
|
||||
|
||||
Open/incomplete chains and ambiguous contacts conservatively block. This is not an overlap-repair operation or a general replacement for layout validation. Caller-provided contact topology must represent the same boundaries and offsets as the query. Prepared geometry must not be mutated; prepare a classifier before sharing it between parallel queries. Edge-array queries still sort their arrays, and recover loop order from private copies before classifying contacts.
|
||||
Open/incomplete chains and ambiguous contacts conservatively block. Loops are recovered with ShapeBuilder's `Tolerance.ChainTolerance`, so a source contour that closes within it (PEP-rounded drawings can miss by 1e-6) stays a closed loop; a stricter closure test would leave the whole part unresolved and freeze any part resting against it. This is not an overlap-repair operation or a general replacement for layout validation. Caller-provided contact topology must represent the same boundaries and offsets as the query. Prepared geometry must not be mutated; prepare a classifier before sharing it between parallel queries. Edge-array queries still sort their arrays, and recover loop order from private copies before classifying contacts.
|
||||
|
||||
## Callers
|
||||
|
||||
|
||||
Reference in new issue
Block a user