How zju-fast-lab/visplanner works
Project Type and Purpose
• visPlanner is a ROS‑based full‑stack robotics framework for visibility‑aware trajectory planning in aerial tracking.
• It combines a multi‑package planner (src/planner) and a UAV simulator suite (src/uav_simulator), exposing ROS nodes/services/topics for end‑to‑end simulation, sensing, planning, and control.
High‑Level Architecture Components
a. ROS Middleware
• Central communication backbone (topics, services, actions).
• Manages message passing between planner, detector, simulator, controller.
b. Planner Suite (src/planner)
• plan_manage: orchestration node (ego_planner_node, FSM, planner_manager).
• bezier_predict: target motion prediction (CUDA‐optional).
• bspline_opt: trajectory optimizer (gradient/LBFGS).
• path_searching: coarse path generation (D* / dyn A*).
• plan_env: environment model (grid map, raycasting).
• drone_detect: vision‐based target detection node.
• traj_utils: common messages (Bspline, MultiBsplines) & visualization.
• rosmsg_tcp_bridge: bridge between ROS and external TCP interfaces.
c. UAV Simulator Suite (src/uav_simulator)
• so3_quadrotor_simulator: physics engine (Boost.odeint dynamics).
• so3_control: low‑level SO(3) controller nodelet.
• fake_drone: simple odom emulator.
• local_sensing: GPU‑accelerated depth/pointcloud simulator.
• map_generator, mockamap, multi_map_server: environment/map services.
• odom_visualization, pose_utils, rviz_plugins: visualization and utilities.
• quadrotor_msgs: custom ROS message definitions for UAV.
• waypoint_generator: scripted waypoint publisher.
Interaction and Data Flow
1. User via RViz → 3D Nav Goal topic → plan_manage node
2. plan_manage triggers path_searching → returns coarse waypoints
3. plan_manage calls bezier_predict (predictor) → future target state
4. plan_manage calls bspline_opt → optimized trajectory under visibility constraints
5. plan_manage publishes trajectory (Bspline.msg) to controller topic
6. so3_control nodelet → computes low‑level motor commands → publishes to simulator
7. so3_quadrotor_simulator → simulates physics → publishes Odometry.msg
8. local_sensing → simulates depth/pointcloud → publishes sensor topics
9. plan_env → subscribes to map & sensor topics → updates occupancy grid
10. drone_detect → subscribes to camera/image topics → publishes target pose
11. rosmsg_tcp_bridge → optionally bridges planner topics to external clients
Key Architectural Patterns
• Modular ROS nodes: each package encapsulates a well‑defined capability.
• Publish/subscribe for asynchronous data flow.
• Service/action calls for synchronous optimization routines.
• Separation of concerns: planning, prediction, control, simulation, sensing.
• Use of plugin patterns in so3_control (nodelet) and rviz_plugins.