Process
Logging and replay
You might say: rosbag, data recording
Logging records timestamped messages and other state so a run can be inspected or replayed after the robot stops.
- What it does
- It turns a one-off failure into evidence that can be reproduced and compared after a code change.
- Ask
- Did we record the topics, timestamps, transforms, commands and environment needed to reproduce the failure?
What to look for
- Timestamped messages and robot state
- Topics, transforms and commands in a record
- Replay after the robot stops
Sources
- Jason M. O'Kane, A Gentle Introduction to ROS, Ch. 9, Recording and replaying messages
We can run the robot itself only a few times, recording the topics we care about, and then replay the messages on those topics many times.
- MCAP, Introduction, Heterogeneous timestamped data, append-only writing, indexed seeking and self-contained schemas
It is ideal for robotics applications, as it can record multiple streams of structured and unstructured data (e.g. ROS, Protobuf, JSON Schema, etc.) in a single file.
Use it on your project
teardown-apply: hold "Logging and replay" (logging-and-replay) from the teardown at https://teardownatlas.com/robotics/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal