Skip to content

golem_slam: the local costmap's footprint follows the arms - #13

Merged
maxconwa merged 1 commit into
mainfrom
dynamic_footprint
Nov 16, 2026
Merged

maxconwa merged 1 commit into
mainfrom
dynamic_footprint

Conversation

@maxconwa

Copy link
Copy Markdown
Contributor

What

  • New node golem_slam/dynamic_footprint: it publishes the local costmap's footprint at 5 Hz. The footprint is the convex hull of the body polygon (nav2.yaml's local footprint) and the padded collision boxes of the arm links, as TF places them. It never shrinks below the body polygon.
    • The arm links are each robot's pipeline.yaml footprint.arm_links, with footprint.padding 0.05 m.
    • It publishes geometry_msgs/Polygon on /local_costmap/footprint, the type Humble's costmap subscribes to.
  • The arms drop out:
    • while a /frame_task or /named_config goal is accepted, executing or cancelling, so a hand reaching for a handle or counter doesn't read as a collision and stop the base;
    • while an arm link has no TF within 0.5 s.
  • The global costmap keeps the fixed footprint, so planned paths don't change with the arms.
  • The H1-2's body footprint has its front edge moved from 0.20 m to 0.45 m (ahead of base_footprint).

Testing

  • golem_slam unit tests: 67 passed, including the new test_dynamic_footprint.py and the updated launch tests.
  • tests/sim/test_sim_stack.sh --h12: 14/14.
  • tests/sim/test_sim_stack.sh --g1: 14/14 (walking to a Nav2 goal while doing t_pose → home).
  • Measured by hand in the sims (/local_costmap/published_footprint followed every change):
Robot home T-pose During an arm goal
H1-2 0.52 m² (front 0.54 m, sides ±0.36 m) 0.94 m² the body polygon
G1 0.31 m² (its body box) 0.68 m² the body polygon

To note

The H1-2's forearms at home reach past the body box, so its footprint at rest is about 45% larger than the box. Reduce footprint.padding or drop the elbows from arm_links if that is too conservative.

🤖 Generated with Claude Code

https://claude.ai/code/session_015EG7p8sgY1ZVi6unbbLp4J

dynamic_footprint publishes the local costmap's footprint (Humble's
geometry_msgs/Polygon on /local_costmap/footprint) at 5 Hz: the convex hull
of nav2.yaml's local footprint (the body, never shrunk) and the padded
collision boxes of pipeline.yaml's footprint.arm_links, posed by TF. During a
/frame_task or /named_config goal, and while an arm link has no fresh TF, it
is the body alone, so a hand reaching for a handle does not stop the base.
The global costmap keeps the fixed footprint.

The H1-2's body footprint's front edge moves from 0.20 m to 0.45 m.

Checked in the RoboCasa sims: tests/sim/test_sim_stack.sh --h12 and --g1
pass 14/14; the H1-2's footprint is 0.52 m2 at home and 0.94 m2 in T-pose,
the G1's 0.31 m2 (its body box) at home and 0.68 m2 in T-pose.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015EG7p8sgY1ZVi6unbbLp4J
@maxconwa
maxconwa merged commit e89d5c7 into main Nov 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant