Add pi05_droid_jointpos config serving absolute joint actions - #7
Merged
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.
Summary
pi05_droid_jointpostrain config: DROID with absolute joint-position actions — the recipe RoboLab's leaderboard serves for its pi0-family policies (theirpolicies/pi0_family/README.mdruns the xuningy/openpi fork; this ports the one difference into ours).pi05_droidplus anAbsoluteActions(make_bool_mask(7, -1))output transform: the model still predicts joint deltas, the transform adds back the observed joint position, so served chunks are absolute joint positions (gripper stays absolute).gs://openpi-assets-simeval/pi05_droid_jointpos(action_horizon=15).Test plan
scripts/serve_policy.py.pi0_familyclient against this same server process) — success rates matched per task.