ROS 2 devs share workflows for untangling large workspace architectures
From rqt_graph to ros2_info, here's how pros parse hundreds of packages
Deep Dive
A ROS 2 developer asked the community how they go about understanding the architecture of a large, unfamiliar workspace—especially projects with dozens or hundreds of packages. They wanted to know how to map package dependencies, which nodes communicate, what topics, services, and actions are used, and whether the implementation still matches the intended architecture. The poster also asked whether people rely on runtime tools like rqt
Key Points
- rqt_graph and Foxglove are the go-to runtime tools for visualizing node/topic communication in large ROS 2 workspaces.
- Design docs like design.ros2.org and ADRs help reconstruct intended architecture when docs are missing or outdated.
- Newer CLI tools ros2_graph and ros2_info offer terminal-based dependency and interface mapping without launching a GUI.
Why It Matters
For ROS 2 devs joining big projects, these workflows cut onboarding time and prevent architecture drift in industrial-scale codebases.