Docs menu
Record and analyze runs
Capture everything a run did, then explain every stop and measure how the car responded to its commands.
A run that went wrong is explained from its recording, not from memory. race_diagnostics records a run: the logs, a machine-readable event stream, a rosbag and the exact code and parameters that ran. tools/run_analysis turns that recording into a report that names the cause of every stop. Both only read: neither publishes a drive topic.
- Record a runWhere recordings come from, how to start one by hand, and what each file in the run folder answers.
- Analyze a runTurn a recorded run into a report that names the cause of every stop, check how SLAM built its map, replay a run with changed parameters or through SLAM again, and fit the simulator to the car.
Checked against
car 1 commit 881c409
and
car 2 commit 779c060, before the two workspaces merged.