How imrclab/crazyswarm2 works
Project type and purpose
• This is a multi-package ROS 2 “stack” (monorepo) for driving and simulating Bitcraze Crazyflie multirotor robots.
• Core packages:
• crazyflie: C++ ROS 2 node to talk to real Crazyflie hardware
• crazyflie_interfaces: custom ROS 2 message & service definitions
• crazyflie_py: Python client library & nodes
• crazyflie_sim: simulation backends (pinocchio, dynobench, neuralswarm) and visualization
• crazyflie_examples: demo nodes & launch files
• ros_ws: a ROS 1-style workspace that pulls everything together under a “crazyswarm” meta-package
File structure
• Top-level directories map to ROS 2 packages. Each has its own CMakeLists.txt and package.xml.
• crazyflie: folder with config/*.yaml, launch/*.py, URDF models, C++ src/scripts.
• crazyflie_interfaces: your pub/sub & srv definitions that decouple client and server.
• crazyflie_py: Python API & helper nodes (genericJoystick, uav_trajectory).
• crazyflie_sim: backends + sim node crazyflie_sil + visualization scripts.
• crazyflie_examples: sample ROS 2 nodes that import everything above to run “hello_world”, SLAM, Nav2 demos.
• ros_ws: “crazyswarm” ROS 1/ROS 2 hybrid wrapper with launch files and sequence CSVs.
• systemtests: end-to-end Python tests + plotting helpers.
README insights
• Confirms ROS 2 based stack, multiple CI pipelines for ROS 2 distributions.
• Central docs reference has overview, “internals” section for architectural guidance.