Costmap based precision controller for trajectory controller#2350
Draft
mustafab0 wants to merge 52 commits into
Draft
Costmap based precision controller for trajectory controller#2350mustafab0 wants to merge 52 commits into
mustafab0 wants to merge 52 commits into
Conversation
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.
Auto e_max governor for precision-nav
Adds a
CostmapPrecisionGovernormodule that watches the global costmap and continuously sets the precision path follower's corridor half-width (e_max) from how cluttered the area around the robot is. Open spaces relax the corridor so the robot can drive faster; tight cluttered areas tighten it so the robot slows and tracks the path closely.What's in this PR
dimos/navigation/costmap_precision_governor/module.py— the new governor module.Subscribes to
global_costmap: In[OccupancyGrid]andodom: In[PoseStamped],and publishes
e_max: Out[Float32].The governor is purely costmap-driven and does not read the characterization artifact. Plant-aware speed scaling stays in
PrecisionPathFollowerTask.How to test
On the robot:
Open rerun, click a goal, watch the robot drive. In open space
e_maxshould be near the high end (~0.9 m); near walls or in clutter it should drop toward the low end (~0.05 m). The robot visibly slows in tight areas and speeds up in open ones along the same path.Where to change the artifact path
The characterization artifact path is set in
dimos/robot/unitree/go2/blueprints/basic/unitree_go2_coordinator.pyon theprecision_followerTaskConfig(around line 100). Default points atdata/characterization/go2/go2_config_hw_concrete_2026-05-28_normal.json.To override per run without editing the file:
tasks[2]is theprecision_follower(aftervel_go2andpath_followerin the task list).Config knobs (governor)
All live on
CostmapPrecisionGovernorConfigand are overridable per-run with-o costmap_precision_governor.<knob>=...:d_neare_max_lowd_fare_max_highe_max_lowe_max_highhysteresis_deltalookahead_mobstacle_threshold