Summarize joined GPS route results

This commit is contained in:
2026-06-20 21:33:08 -05:00
parent 54f014b74d
commit bf72dcf6e3
3 changed files with 320 additions and 47 deletions
+31
View File
@@ -264,6 +264,37 @@ Route-record/resource correlation:
provider initialization site or a way to join search-side route points back to
`nodeRefHash`/lane flags before the edge cost is returned.
Latest full-route join:
- `logs/EdgeWeightGPS_query_route_probe_2308.log` contains nine solved route
results from the 23:08 user test. All 362 emitted route records matched
`worldTrafficLanePersistent.nodeRefHash` in
`work/raw-segment-json/all.traffic_persistent.json`.
- The log's wall timestamp currently wraps milliseconds without incrementing
the displayed second. Use the `+Nms` elapsed field when comparing submit and
result times.
- Representative solved route composition:
- side job: 12 records, 32 ms, 578.6 pavement length.
- Sinnerman: 23 records, 45 ms, 897.4 pavement, 160.4 highway, 89.8 road.
- Claire: 18 records, 34 ms, 1216.5 pavement.
- custom highway-ish pin: 17 records, 44 ms, 1006.3 pavement,
241.0 highway, 38.0 road.
- Aldecaldo camp: 80 records, 325 ms, 5853.5 road, 1492.9 highway,
1111.5 pavement, 24.6 gpsonly.
- far east gig: 81 records, 144 ms, 5086.2 road, 1523.0 highway,
1111.5 pavement, 24.6 gpsonly.
- Violence: 55 records, 97 ms, 1991.5 pavement, 358.5 highway,
86.1 road.
- cyberpsycho unfinished highway: 58 records, 147 ms, 2657.4 pavement,
519.0 highway, 113.2 road, 56.7 gpsonly.
- Search/provider aggregate in the same log: 159 searches, 4036 provider
filter calls, only 3 filter failures. Filter slot `+0x08` is therefore
almost never pruning this test graph.
- Search-side point classes observed by `0x44f838` are `{1,3,4,5,15}`. Final
route-record low-byte classes are `{0,1,2,3,4,5,7,8,9}`, and route-record
classes 7/8/9 are highway-heavy. These are different domains, which explains
why provider point-class tuning did not map cleanly to highway preference.
Current static producer lead:
- `0x70a908` packages the route endpoints and query settings, then calls