Unit 08 · lesson
Inspect a Launched System
Launching successfully means processes started.
It does not automatically prove the system has the graph you intended.
Diagrams open at a readable shape-aware scale. Zoom or expand when you need more detail.
Build an inspection routine
After:
ros2 launch robotnix_pubsub student_system.launch.py
open another sourced terminal and run:
ros2 node list
ros2 topic list -t
ros2 topic info /student_chatter --verbose
If you use namespaces/remaps, inspect the resolved topic instead.
Compare launch intent to runtime evidence
Create:
| Launch intent | Runtime evidence |
|---|---|
| talker started | node list / launch log |
| listener started | node list / launch log |
| shared topic | topic list/info |
| publisher endpoint | topic info verbose |
| subscriber endpoint | topic info verbose |
Use rqt_graph when helpful
The official launch tutorial demonstrates visualizing a launched Turtlesim system with rqt_graph.
For your two-node package, either graph view or CLI evidence is enough if it proves the same relationship.
Checkpoint
What evidence would catch a launch file that successfully started both nodes but accidentally remapped the listener to the wrong topic?