How alliander-opensource/rcdt_robotics works
Project Type and Purpose
• This is a robotics framework and toolkit (“RCDT Robotics”) built around ROS 2. It provides:
• A set of ROS 2 packages for robot control (Franka, Panther, mobile manipulators)
• Perception (rcdt_detection) and action orchestration (rcdt_actions)
• Simulation support via Gazebo (rcdt_gazebo)
• Utilities (rcdt_utilities, rcdt_sensors, rcdt_messages)
• A Python-based workflow/orchestration engine (pyflow)
• Docker/devcontainer setup for reproducible development and CI
Key Architectural Areas (based on file structure)
• Dev Environment & CI
• .devcontainer, Dockerfiles, .github/workflows
• Local_run, get_image_tag, scripts in dockerfiles/install_scripts
• Documentation
• docs/ with Sphinx configuration, content folders, images/videos
• Workflow Engine
• pyflow/ (default_config, graphs, packages/RCDT)
• ROS 2 Workspace
• ros2_ws/src containing ~12 ROS 2 packages:
– rcdt_messages (action/srv definitions)
– rcdt_actions (action servers/clients)
– rcdt_detection (vision pipelines)
– rcdt_franka (+MoveIt config)
– rcdt_mobile_manipulator
– rcdt_gazebo (Gazebo models/launch)
– rcdt_joystick (joystick interfaces)
– rcdt_panther (+navigation)
– rcdt_sensors
– rcdt_utilities (launch utils, RViz configs)
a. Development & Deployment Layer
– Docker Engine & Devcontainer
– CI/CD Workflows (Lint, Docs, Docker Build)
b. Workflow Orchestrator
– Pyflow Core Engine
– Graph definitions (pyflow/graphs)
– Package plugins (pyflow/packages/RCDT)
c. ROS 2 Communication Layer
– Core message definitions (rcdt_messages)
– Topics, Services, Actions
d. Functional Subsystems (each as a module of ROS 2 nodes & plugins)
1. Perception: rcdt_detection
2. Action Execution: rcdt_actions
3. Manipulator Control: rcdt_franka + rcdt_franka_moveit_config
4. Mobile Base + Manipulator: rcdt_mobile_manipulator
5. Simulation: rcdt_gazebo
6. Joystick Interface: rcdt_joystick
7. Navigation (Panther): rcdt_panther
8. Sensor Utilities: rcdt_sensors
9. General Utilities & RViz: rcdt_utilities
Relationships & Interactions
• Pyflow triggers sequences of ROS 2 actions by calling rcdt_actions through ROS 2 action clients.
• rcdt_detection publishes sensor topics (RGBD images, masks) using rcdt_sensors utilities.
• rcdt_messages defines the contract for all inter-package communication (topics/services/actions).
• rcdt_franka (and /panther) subscribe to commands (MoveHandToPose, MoveToConfiguration) and drive hardware or simulation via MoveIt or Gazebo plugins.
• rcdt_utilities provides shared launch files (rviz.launch, utils.launch) and helper libraries.
• CI pipelines build Docker images, run tests (conftest.py), lint code, and generate docs.
Architectural Patterns & Principles
• Modular ROS 2 microservices: each robot capability is its own package with clear message/service boundaries.
• Message-driven communication: topics for streaming data, services for RPC, actions for long-running tasks.
• Plugin architecture in Pyflow for extensibility (node_loader, pin_loader).
• Containerized development and reproducibility via Docker/devcontainer.