How zju-fast-lab/ego-planner-swarm works
Project type and purpose
• This is a ROS‐based, full‐stack multi‐agent (swarm) navigation system with two main domains:
a. Planner stack (“src/planner”) implementing local mapping, path search, trajectory optimization, multi‐robot planning, and detection.
b. Simulator stack (“src/uav_simulator”) providing sensor simulation, map servers, vehicle dynamics (fake or SO3), visualization, message definitions, and utilities.
• Purpose: decentralized, asynchronous quadrotor swarm navigation in unknown, cluttered environments using onboard resources only.
File structure
• Top‐level src splits into:
• planner/… packages: bspline_opt, drone_detect, path_searching, plan_env, plan_manage, rosmsg_tcp_bridge, traj_utils
• uav_simulator/… packages: Utils (multi_map_server, odom_visualization, pose_utils, quadrotor_msgs, rviz_plugins, uav_utils, waypoint_generator), local_sensing, map_generator, mockamap, so3_control, so3_quadrotor_simulator, fake_drone
• Each subfolder is a ROS package (CMakeLists.txt + package.xml) with nodes, headers, launch files, configs, and tests.
• Key patterns:
• ROS pub/sub and service/launch architecture
• Nodelet plugins for zero‐copy in local_sensing and SO3 control
• TCP bridge for inter‐drone communication
• Catkin workspace build scripts
README for additional insights
• The system uses Catkin (ROS1), Armadillo, optional CUDA for local_sensing, and optional physics‐based dynamics vs. fake_drone for scalability.
• Launch files orchestrate the full swarm (swarm.launch), single drone (simple_run.launch), RViz (rviz.launch), simulator only (simulator.xml), etc.
• The system is modular—users can swap GPU vs CPU sensor, fake vs physics simulator, enable or disable control nodelets.
Details
• 7 planner packages and 10+ simulator packages as separate components.
• Launch files that bring them together (e.g., simple_run.launch, swarm.launch, simulator.xml).