Auto Tune module#3121
Draft
mustafab0 wants to merge 8 commits into
Draft
Conversation
Drives one autotune run against a known synthetic plant: profile -> probe -> excitation battery -> fit -> tune -> artifact. Exercises the external APIs the module binds to (Twist/Vector3, EpisodeStatus) as part of the flow so drift in those surfaces fails here rather than on the robot. In-process and synthetic; the process-level run against a booted blueprint belongs in dimos/e2e_tests/ once the live drive wiring exists.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
❌ 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 |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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 a mobile base's velocity controller is manual and expert-only. There's no single path from a robot to its gains.
Issue: #2755
Closes DIM-1116
Solution
Adds
dimos/control/autotune/. You declare a RobotProfile (command interface, odometry domain, channels, limits, fitter); it probes stream timing, drives a step/ramp battery through the ControlCoordinator recording one episode per run, fits a first-order-plus-deadtime model per axis, derives bandwidth plus Bode and pole-zero plots, then lambda-tunes PI gains with a robustness sweep.Emits a tuned artifact in the shape the control task already loads, plus a separate characterization report. Fitters and tuner were ported from the characterization branches and made robot-agnostic. Live drive wiring is not included.
Breaking Changes
None. Additive module.
How to Test
pytest dimos/control/autotune(~2s).valid_for_tuningis false for non-hardware data.Checklist