fix: fill junction core and connect cluster lane trajectories
This commit is contained in:
1 parent
695bf21a84
commit
6a8f026d12
12 files changed
+527
-83
No files matched your search
+23
@@ -0,0 +1,23 @@
|
||||
# Center pavement and vehicle trajectory audit — 2026-09-14
|
||||
|
||||
Scope: investigation and implementation plan only; no implementation changes.
|
||||
|
||||
Reproduced with workbench-data/import-fE8XI7/source.osm and its active area-config.snapshot.json: four nodes (8005332807, 8024512135, 8024512145, 8024512147), core radius 21 m. Do not substitute the older five-node/24 m script.
|
||||
|
||||
## Confirmed findings
|
||||
|
||||
- Actual compilation publishes no complex-core. Diagnostic: complex-junction-core-closure-unsupported / core-closure-invalid. Eight complex-approach surfaces and four complex-corner-fillet surfaces remain.
|
||||
- complex-junction.js constructs each corner fill as [...curve, center, curve[0]]. With the core absent, these center-directed fans explain the triangular gaps. This is not evidence of a triangulation-rendering defect.
|
||||
- buildCoreClosure in junction-boundary-graph.js selects one section per arm when arms contain multiple carriageways, discarding other entry seams from the candidate core. It then sorts endpoints by angle and rejects zero edges, unpaired edges, insufficient area or self-intersection with the same generic reason. Which individual predicate fails must be instrumented before changing construction.
|
||||
- compileConnectors in native-road.js works on enabled model.connections by node. Four-segment nodes use a quadratic curve through an endpoint node as control; other through movements use a straight chord; other turns use cubic curves with lane endpoint tangents. Fixed sampling is 12 segments. Existing tangent-based construction therefore does exist, but is not used consistently.
|
||||
- validateConnectorContainment checks samples against one junction exterior ring and skips kind=cluster; it does not establish swept vehicle clearance from island holes or authoritative complex pavement. No claim yet that a particular observed connector joins the wrong lane; that requires source/destination tracing and measured evidence.
|
||||
|
||||
## Implementation sequence
|
||||
|
||||
1. Establish reproducible metrics for this saved configuration: all entry section IDs, core failure predicate, pavement connected components and unexplained gap regions; each movement's source/destination lane and endpoint/tangent errors. Export pavement and trajectory overlays separately and together. Preserve current four islands as a regression invariant.
|
||||
2. Repair core closure using every valid carriageway entry seam and explicit connecting boundary edges. Reuse BoundaryGraph and polygon-clipping; validate a simple closed boundary, union with approach/turn pavement, and subtract justified non-drivable islands/exclusions. Crosswalks are markings on pavement, not holes. Do not force-fill a convex hull or disable closure validation.
|
||||
3. Trace cluster movements across internal source connections to external lane ports, preserving turn restrictions and source provenance. Determine whether current node-level connectors duplicate or omit these movements before replacing them. Lane endpoints/tangents and pavement must consume the same entry sections.
|
||||
4. Use lane endpoint positions and tangent directions for all connector shapes, including offset through movements. Begin with existing cubic machinery; constrain/control curvature and adapt sampling by geometric error. A cubic with tangent continuity does not automatically give curvature continuity across road joins. Add curvature limits or curvature-transition construction where required. Validate the full path and, with an explicit vehicle envelope, swept clearance against final drivable region and islands. Crossings between different traffic streams are not automatically errors.
|
||||
5. Acceptance: all expected external entries connect to continuous pavement; no unexplained holes; four islands/green polygons retained; movement IDs and permitted lane pairings correct; endpoint error <= 1 cm, measured endpoint tangent error <= 1 degree; no self-return/cusp or island penetration. Establish vehicle-specific minimum radius before declaring trajectories physically drivable. Include T/Y/oblique/multi-carriageway and short-source counterexamples.
|
||||
|
||||
Deliver as one reviewed change across pavement and trajectories after real-workbench visual verification. Do not archive parent task from local facility tests. Remaining uncertainty: exact closure rejection predicate, abnormal connector IDs, whether those displayed lines include lane separators as well as connectors, and necessary vehicle curvature assumptions.
|
||||
Reference in new issue
Block a user