How mevans4/41068rs12025-group18 works
Project Type and Purpose
• This is a full-stack robotics simulation application:
– Uses Ignition Gazebo for world and robot/drone simulation.
– Runs ROS2 nodes for perception (LiDAR), mapping (SLAM), localization, navigation (Nav2), control (drone_controller), and a Qt-based UI.
– Objective: autonomously navigate plantation rows, detect/count/measure tree trunks, build a rich map, and produce a report.
File Structure
Top-level packages (ROS2 workspace):
• 41068_ignition_bringup
– Launch files (launch/…launch.py) to spin up Gazebo, SLAM, Nav2, localization, and robot/drone drivers.
– Models (models/…), URDFs (urdf/, urdf_drone/) define robot and drone.
– config/*.yaml for Gazebo–ROS bridge, Nav2 params, SLAM params, robot_localization params.
• drone_controller
– C++ nodes: altitude_controller, drone_controller (velocity commands), mission_node (goal publisher).
• drone_ui
• lidar_tree_detector
– C++ node subscribing to /scan, publishing TreeDetectionArray.msg.
Other artifacts:
• Saved maps (TreePlantation*.pgm/.yaml), .posegraph & .data for offline SLAM.
• Drone_UI.ui (Qt Designer file).
Key Insights from README
• Autonomous navigation through pine plantation.
• LiDAR-based tree trunk detection, counting, diameter estimation.
• Final outputs: enriched map + report for plantation manager.
1. Simulation Environment
– Ignition Gazebo + world files (worlds/) + models + gazebo_ros_bridges.
2. ROS2 Middleware (DDS) – the communication bus.
3. Perception
– lidar_tree_detector_node
– (SLAM) slam_toolbox node
– map_server node
4. Localization
– robot_localization (EKF)
5. Planning & Mission
– Nav2 stack (planner, controller, bt_navigator)
– mission_node (from drone_controller)
6. Control
– drone_controller (velocity & altitude)
– Gazebo plugins/drivers receive /cmd_vel
7. User Interface
– drone_ui_node (Qt GUI)
8. Data Storage / Reporting
– Map files (.pgm/.yaml)
– Report generator (could be offline script or incorporated in UI)
• Gazebo → (via gazebo_bridge) → /scan, /odom, /tf, sensor topics → ROS2
• /scan → slam_toolbox → /map → map_server → Nav2 & UI
• /odom, /imu → robot_localization → filtered /odom → Nav2 & slam_toolbox
• UI → mission_node → /goal_pose → Nav2
• Nav2 → /cmd_vel → drone_controller → /drone_velocity → Gazebo plugin
• /scan → lidar_tree_detector_node → /tree_detections → UI & logger
• Data outputs (map + detection logs) → report generator
c. Architectural Patterns & Principles
• Modular ROS2 nodes communicate over topics/services.
• Layered pipeline:
– Simulation → Perception → Localization → Planning → Control → Actuation
• Separation of concerns: perception vs. planning vs. control vs. UI
• Reusability: standard Nav2, robot_localization, slam_toolbox
d. Key Technologies & Frameworks
• ROS2 (Foxy/Galactic)
• Ignition Gazebo + gazebo_ros_bridge
• SLAM Toolbox
• robot_localization (EKF)
• Nav2 (nav2_bringup)
• C++ (colcon, ament_cmake)
• Python Qt (PyQt5 or PySide)
• Qt Designer (.ui)
• YAML for configs & map definitions