Repository navigation
golem_slam: stop Nav2's inflation-radius errors (local 0.3 m, start-up footprint, global 0.22 m) - #35
Merged
Conversation
…bed radius The fixed footprint's rear edge sits at x = -0.20, so its inscribed radius equals the 0.2 m inflation exactly. dynamic_footprint adds the arm links' padded boxes, and arms hanging behind the pelvis push the rear edge back (~0.246 m in the H1-2 sim), so Nav2's local costmap logged "inflation radius smaller than the inscribed radius" on every footprint update, about once a second. Both robots' local costmaps, and the MPPI ObstaclesCritic that reads them, now inflate by 0.3 m. The global costmaps stay at 0.2 m, so the planner still plans through the same narrow kitchen gaps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… is up; global inflation past Nav2's padding dynamic_footprint publishes the body polygon alone until the first message on arms_ready_topic (default /left_ee_pose, which frame_task_server publishes once its start-up moves are done): those moves swing the arms behind the pelvis (an inscribed radius of 0.33-0.42 m on the H1-2), past the local costmap's 0.3 m, while the robot cannot drive yet. Both robots' global costmaps inflate by 0.22 m: Nav2 pads the fixed body footprint by its 0.01 m footprint_padding, so its inscribed radius is 0.21 m, and 0.2 m logged the same error once at start. On the Mac (H1-2 and G1 navigation stacks at 1.00x): no inflation error over start-up, named_config moves and Nav2 goals, from 13 (H1-2) with the 0.3 m local inflation alone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015EG7pDNJLWR31eQmyKaWhr
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
golem_slam: stop Nav2's "inflation radius smaller than the inscribed radius" errors
Nav2 logged
The configured inflation radius (0.200) is smaller than the computed inscribed radius (...) of your footprinton both robots. It came from three places:dynamic_footprintadds the arms. Arms hanging behind the pelvis push the inscribed radius to about 0.25 m, past the 0.2 m inflation.ObstaclesCriticat 0.3 m (8683be9, fromgolem_slam/local_inflation, rebased onmain)frame_task_server's start-up arm moves swing the arms behind the pelvis: 0.33–0.42 m on the H1-2dynamic_footprintpublishes the body polygon alone until the first/left_ee_pose, whichframe_task_serverpublishes once its start-up moves are done. The robot can't drive before then. New parameterarms_ready_topic(empty: the arms count from the start).footprint_padding, so the inscribed radius is 0.21 mMeasured on the Mac (MacBook Air M3, navigation stacks at real time, kitchen 9/9/42)
mainnamed_configmoves, both goals)The G1's goal back to start has aborted short on every run with this setup (0.62–0.85 m before this PR). This run doesn't show whether the change makes it better or worse.
Testing
golem_slamtests: 71 pass, including a newtest_the_arms_count_only_after_the_controller_starts_upand the example-config check.tests/sim/test_sim_stack.sh --h12/--g1,tests/g1/test_sim_nav.sh). Their goal clearances should still hold with 0.3 m local / 0.22 m global inflation, but that hasn't been checked.🤖 Generated with Claude Code
https://claude.ai/code/session_015EG7pDNJLWR31eQmyKaWhr