Loading system evidence
Loading system evidence
Learn ROS 2 by diagnosing and repairing robot systems that fail the way real ones do.
Preview first lessonOutcome
Build
A verified warehouse incident report with a repaired ROS graph and a reproducible evidence bundle.
Sample incident
Determine why `/scan_filter` is absent without reinstalling or rebuilding the workspace.
Full syllabus
Bound the failing system, separate observations from assumptions, and choose the smallest useful diagnostic command.
Trace fully qualified names through launch scopes, remaps, and component containers.
Separate discovery, publication, transport, and callback processing using rate and type evidence.
Reason about reliability, durability, history, depth, and rate as an endpoint contract.
Trace configuration ownership through YAML roots, namespaces, launch substitutions, and override order.
Relate message stamps, simulation clocks, transform publication, and buffer windows.
Inspect callback queues, blocking work, callback groups, and executor thread availability.
Capture reproducible evidence, align clocks, and reconstruct an incident timeline from multiple sources.
Playgrounds
Small, functional experiments that reveal the math and evidence behind this course’s failures. Open them alongside the labs.
Compose parent-child transforms and see how rotation units and direction affect the final frame.
TF2 visualizer / transform composition / ROS 2
Live controlsTest reliability, durability, history, queue depth, and slow subscribers against live message flow.
ROS 2 QoS compatibility / DDS / subscriber
Live controlsCompare wall time, simulation time, TF buffers, and timestamp age to diagnose extrapolation.
ROS 2 simulation time / TF buffer / extrapolation