R1D1 ROS2 simulation source

Project notes

Keep the documented environment and package routes together

The README names ROS 2 Humble or Jazzy, MoveIt2, Gazebo and OpenCV with ArUco support. It documents colcon build and sourcing the resulting workspace, then separate simulation and MoveIt demo launches. It says the project was tested upstream in a Docker/Humble environment; this does not establish a reproduced Jazzy or host installation here. No package was built. [1]

A bounded source investigation is r1d1_description's sim launch alongside r1d1_moveit2_config's demo launch, followed by inspecting move_at_position.cpp and the detector before running them. The arm example creates a MoveGroupInterface named arm and supplies a fixed target pose. That example target is not an automatically verified object location or a safe pose for different hardware. No planning or motion was performed. [1] [3]

Inspect perception assumptions instead of assuming calibration

The detector subscribes to image data, while the sampled source has its CameraInfo subscription commented out. The README's camera-calibration discussion should therefore not be treated as proof that this node automatically consumes a live calibration stream. The callback assigns hard-coded camera intrinsics and distortion coefficients, reads /camera/camera/color/image_raw, publishes poses on /detected_marker/marker_pose, selects DICT_4X4_1000, and passes marker length 0.1 to pose estimation. These settings must match the actual camera and markers. More seriously, the sampled publisher assigns both x and y from tvec[0] and fills frame_id with marker-ID/distance text. These source observations require correction or investigation before integrating a pose; they are not reproduced runtime failures. [1] [4]

The root notice is MIT. Component-specific rights for robot meshes, external libraries and purchased components were not established in this review and require separate checking. No camera, marker pose, collision check, navigation, complete hardware design or real robot behavior was validated. [2]