fix: fill junction core and connect cluster lane trajectories

This commit is contained in:
que01 committed 2026-09-14 10:47:25 +08:00
1 parent 695bf21a84
commit 6a8f026d12
12 files changed
+527 -83

No files matched your search

+29 -4
View File
@@ -452,10 +452,15 @@ constraints and legacy constraints containing both offsets must be evaluated
with both effective offsets present.
Boundary closure reports `sharedSeamErrors` per carriageway and
`maxSharedSeamErrorMeters` as the maximum endpoint distance in local metres
between the core ring edge and its BoundaryGraph `inner` edge. Missing or
non-contiguous edges remain `Infinity`; the value is not a boolean adjacency
placeholder. Explicit transition stations are clamped to the source polyline
`maxSharedSeamErrorMeters` against the authoritative BoundaryGraph inner
section. For a simple closure the section is an exact ring edge. For overlapping
multi-carriageway entries, the center is the union of center-to-entry cells;
a complete inner seam may then lie inside that union. Such a seam is accepted
only after splitting it at every polygon boundary intersection and checking
all resulting intervals (0.1 mm numerical boundary tolerance), then measuring
its endpoint mismatch against its authoritative graph edge. Missing or
uncovered seams remain `Infinity`; valid overlap must not discard carriageways
or falsify the connected-entry count. Explicit transition stations are clamped to the source polyline
range for legacy/direct compiler inputs and marked
`insufficient-source-length` when the requested length cannot fit. The solver
rejects such values before they can be saved.
@@ -472,3 +477,23 @@ and inner section edges, preserving the fixed source width when the inner width
changes. Unsupported, invalid or excluded transitions do not publish preview
lanes or their derived markings. This contract does not yet replace the separate
corner sidewalk overrun geometry or validate all short-road suppression paths.
## Complex cluster vehicle paths
Cluster connectors trace enabled lane movements through internal roads to
external lane ports. Use breadth-first traversal per incoming lane; avoid
cycling through internal lanes. Preserve source movement IDs and existing lane
restrictions. A published whole-cluster path references visible approach lanes
and their travel-oriented endpoints (outbound preview polylines are stored in
reverse travel order). Do not retain per-node connector fragments as if they
were whole-cluster trajectories.
Curves preserve endpoint tangents and use adaptive sampling (2 cm chord error,
2 m maximum segment length, 1 degree tangent/chord error). These are geometric
sampling tolerances, not proof of curvature continuity or vehicle turning
radius. Published cluster paths must be non-self-intersecting, fully inside the
published pavement region and avoid island edges/interiors. Failed candidate
paths remain diagnostic/deferred movements, never fake safe curves. Current
implementation explores a bounded set of cubic control lengths; it is not a
complete motion planner and does not prove vehicle swept-envelope clearance.