How 6-robot/robocon25_proof works
Main Components
• Simulation Environment ("robocon25_sim"):
• Contains the simulated world, robot model, and field configuration.
• Key files include the CMakeLists.txt, package.xml, and world files located under the worlds folder.
• This module is likely integrated with Gazebo or a similar simulator (common in ROS) based on the file organization (models, worlds, simulation settings).
• Localization Module ("robocon_localization"):
• Implements various localization algorithms and calibration routines.
• Contains separate nodes and launch files for routines such as calibration (calibrate_dist.launch), HSV adjustments (hsv_adjust.launch), side-line detection (loc_sidelines.launch), and re-localization (test_relocalization.launch).
• The source (src) and include directories show a clear separation between interface headers and implementation of key algorithms like distance lookup, lines mapping, and matching.
• Configuration files (dist_table.txt) and various launch files indicate different operational modes/testing setups for the localization process.
• External Tools & ROS Ecosystem:
• ROS middleware is the backbone of communication. The project uses ROS Noetic on Ubuntu 20.04.
• Additional ROS tools such as rqt_robot_steering (mentioned in the README) are used to manually steer or interface with the simulated robot.
• The README includes links to demonstration videos and tutorials which indicate that the project leverages standard ROS practices in deploying nodes, topics, and services.
Relationships and Interactions
• The simulation package (robocon25_sim) acts as the “world” or environment provider, running the simulated scene (field, robot models, and dynamic entities) and publishing sensor data.
• The localization package (robocon_localization) runs as a separate ROS node or set of nodes that subscribe to sensor data or simulation topics to perform calibration and localization tasks. In a typical setup, these nodes would interact via ROS topics, services, or actions.
• The launch system is used to wire these components together, specifying which nodes should run and how they interact.
Important Architectural Patterns and Design Principles
• Modularity & Separation of Concerns: The simulation and localization functionalities are isolated in their own packages. This separation should be highlighted by grouping them as distinct components.
• ROS-Centric Pattern: Use of launch files, package.xml, and CMakeLists.txt indicate adherence to ROS best practices. Emphasize the middleware as the integration layer.
Technologies and Frameworks
• ROS Noetic: All nodes communicate over ROS topics.
• Gazebo (implied): Given the simulation assets and world descriptions, it is likely that a simulation engine like Gazebo is used.
• C++ for node implementations (as seen in the “src” directory for localization).
• Additional visualization/control tools (rqt_robot_steering).
• “World Configuration” (world files, models, materials).
• “Launch Configurations” (balls.launch, field.launch).
• “Configuration & Calibration” (configuration files, calibrate_dist.launch).
• “Vision & Data Processing” (hsv_adjust.launch, localization.cpp, and related files).
f. Optionally, add blocks for additional tools (e.g., “rqt_robot_steering”) and annotate how they interact with the system.