How nitic-robot-club/nhk2025b_ros2 works
Project type and purpose
• This is a ROS2-based robotics software stack (“nhk2025b_ros2”) for controlling and simulating a robot platform, including perception, localization, planning, control, behavior, and visualization, all organized into ROS2 packages.
File structure
• Top-level directories correspond to key ROS2 domains:
• src/message: custom ROS2 message definitions (nhk2025b_msgs)
• src/common: hardware interfaces, utility libraries, URDF/meshes
• src/localization: odometry, EKF, MCL, ICP, pose initialization
• src/planning: path planner node
• src/control: pure pursuit & swerve kinematics calculators
• src/behavior: high-level state machine driving the robot
• src/simulation: simulated sensors/actuators for test runs
• src/launch: XML/Python launch definitions with parameter files
• Build and deploy artifacts (CMakeLists.txt, package.xml, setup.py) indicate a standard ROS2/CMake + Python package layout.
README for additional insights
• The README confirms ROS2 Humble, simulation vs. real-hardware launches, dependencies (xacro, joint-state-publisher, can-utils), and CAN/V-CAN setup.
• It implies a layered ROS graph: sensor → perception → localization → planning → control → actuation/behavior, with supporting visualization.