307ab0e194
Some checks are pending
CI Benchmark - Fusion Loop Timing / Fusion Loop Timing Benchmark (push) Waiting to run
Virtual nodes created without an explicit position carry the nodes-table DB defaults (pos_x=0, pos_y=0, pos_z=1), so SyncToRegistry/SyncOneNode wrote co-located origin positions into the fleet registry — and downstream into the fusion engine — collapsing Fresnel excess paths (core symptom in bf-18yn). Resolve positions through a new effectivePositions helper: nodes still at the default origin are reassigned distinct, spread-out geometry from DefaultNodePositions (sized to the full node count, across the store's space), while explicitly-placed nodes keep their position. Slot assignment is keyed by sorted node ID so it is deterministic regardless of map iteration order, and a single-node sync writes the same position a full sync would. The effective positions flow through SyncToRegistry, SyncOneNode, and ToRegistryRecords, so the registry and fusion-engine seeding observe non-degenerate geometry. Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| accuracy.go | ||
| engine.go | ||
| gdop.go | ||
| handler.go | ||
| node.go | ||
| node_positions_test.go | ||
| physics.go | ||
| propagation.go | ||
| registry_bridge.go | ||
| registry_bridge_test.go | ||
| session.go | ||
| simulator_test.go | ||
| space.go | ||
| space_test.go | ||
| types.go | ||
| virtual_state.go | ||
| virtual_state_test.go | ||
| walker.go | ||
| walker_test.go | ||