- Car
- Car 2
- Controller
gap_follow- Driven
- 35.4 s, 78.2 m
- Top speed
- 3.75 m/s
- Stops
- 7
0.00 s
Why the car did this
Stops
What set the speed
On every decision, gap_follow computes several speed limits and commands the
lowest one. This is how often each limit was the binding one across the run.
| Binding limit | Decisions | Share | What it is |
|---|
How the car responded
These numbers compare each command with what the car did, measured by matching consecutive LiDAR scans rather than from odometry, whose turn rate is computed from the steering command itself.
How the replay is checked
Probe events
What race_diagnostics logged during the session. Times are
from the moment LB was pressed; negative times are before it.
Limitations
- The path is integrated from LiDAR scan matching, so it drifts over the run, and the same spot on different laps does not line up exactly.
- The replay is open-loop: it explains the decisions the car made on the scans it saw. It cannot show where a different decision would have taken the car.
- The scan view shows every third beam (361 of 1081), and only the longest LB hold of the session is replayed.
- Odometry speed comes from the wheels and reads high, most of all in tight turns. The measured speed on this page is the scan-matched one.