Go2 Speed vs Precision testing#2138
Draft
mustafab0 wants to merge 11 commits into
Draft
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
2fb6967 to
bfe69aa
Compare
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.
Problem
Tuning the Go2 base controller was guesswork: the FOPDT plant fit and feedforward gains were hand-vendored, with no single artifact telling an operator "for tolerance X cm, run at speed Y."
Issue: #921
Solution
Two CLI tools producing one versioned config artifact.
go2_characterizationruns a space-cheap velocity-step system-ID, fits FOPDT per axis (vx/vy/wz), and derives feedforward + a curvature velocity profile;go2_benchmarksweeps the hardcoded baseline controller across a speed ladder and writes back the operating-point map + tolerance→max-safe-speed inversion. One SI harness, sim vs hardware is just which plant the steps drive. Carries only the minimal verified dependency closure from the R&D branch (R&D archived off-repo).Breaking Changes
None
How to Test
uv run pytest dimos/utils/benchmarking/test_tuning.py -q→ 16 pass.uv run python -m dimos.utils.benchmarking.characterization --mode self-test→ artifact,valid_for_tuning=false.uv run python -m dimos.utils.benchmarking.benchmark --config <self-test artifact> --mode sim --speeds 0.5→ sim pre-check map.dimos run unitree-go2-webrtc-keyboard-teleopto position robot before each test