Skip to content

Commit 0067100

Browse files
kaiaaiclaude
andcommitted
oomwoo_clean/nav: use the world-aligned living_room map
nav.launch.py defaulted to oomwoo_gazebo/map/living_room.yaml (origin -1.33,-2.76), which does NOT cover the sim's default spawn (-2.0,-0.5) -- the robot came up outside the map, so the global costmap logged "Invalid frame ID map" / "out of map bounds" and navigation never worked. Default to the world-aligned oomwoo_sim_support/maps/living_room.yaml (origin -2.75,-2.75) that the coverage regression uses; it covers the spawn. Verified headless: robot localizes at spawn, in bounds, and a NavigateToPose goal plans and SUCCEEDS. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent d4246d5 commit 0067100

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

src/oomwoo_clean/launch/nav.launch.py

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,8 +76,11 @@ def generate_launch_description() -> LaunchDescription:
7676
true_robot_radius = 0.1745
7777
coverage_target = 0.90
7878

79+
# the WORLD-ALIGNED living_room map (origin -2.75, covers the spawn); the
80+
# oomwoo_gazebo copy has a different origin that excludes the -2,-0.5 spawn
7981
default_map = os.path.join(
80-
get_package_share_directory('oomwoo_gazebo'), 'map', 'living_room.yaml')
82+
get_package_share_directory('oomwoo_sim_support'),
83+
'maps', 'living_room.yaml')
8184
x0 = LaunchConfiguration('x_pose')
8285
y0 = LaunchConfiguration('y_pose')
8386
yaw0 = LaunchConfiguration('yaw')

0 commit comments

Comments
 (0)