feat(eval): integrate LIBERO-PRO code-policy benchmark - #3439
Draft
TomCC7 wants to merge 5 commits into
Draft
Conversation
❌ 3 Tests Failed:
View the top 2 failed test(s) by shortest run time
View the full list of 1 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
TomCC7
force-pushed
the
cc/feat/libero-code-policy-eval
branch
from
August 14, 2026 20:30
42732cd to
311d76e
Compare
1 task
TomCC7
changed the base branch from
cc/feat/eval-code-as-policy
to
cc/eval/nav-benchmark
August 14, 2026 20:34
TomCC7
force-pushed
the
cc/feat/libero-code-policy-eval
branch
from
August 14, 2026 20:42
311d76e to
19823a7
Compare
TomCC7
force-pushed
the
cc/feat/libero-code-policy-eval
branch
from
August 14, 2026 21:00
19823a7 to
3b02904
Compare
TomCC7
force-pushed
the
cc/feat/libero-code-policy-eval
branch
from
August 14, 2026 21:02
3b02904 to
9014638
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.
Contribution path
Problem
DimOS needs a LIBERO-PRO evaluation whose score remains comparable with the original benchmark while exercising the same unified, realtime policy interface intended for physical robots. LIBERO and its simulator dependencies must stay out of the host Python environment, and submitted policies must not access benchmark lifecycle or scoring state.
Solution
Integrate one end-to-end LIBERO-PRO single-trial evaluation on top of #3471:
code-policy-v1runtime, strict smoke case, CLI coverage, generated blueprints, documentation, and architecture decisionsThe first integration evaluates one initialization of one task. Parallel and batched execution remain out of scope.
This PR remains draft until a smoke policy produces nonzero arm-joint motion. Trial completion, a score, and gripper-only motion do not satisfy that readiness gate.
How to Test
uv sync --extra agents npm --prefix packages/pi-code-policy-extension install npm --prefix packages/pi-code-policy-extension run build dimos eval run \ dimos/benchmark/libero_pro/cases/goal-task-0-single-trial/evaluation.json \ --output /tmp/dimos-libero-pro-smoke \ --json --quietFocused checks:
Validated after restacking: 46 focused tests pass, the generated blueprint registry is current, and mypy reports no issues across 21 source files. The prior Podman smoke completed 300 policy ticks, emitted a native
0.0score, and produced a valid 301-frame, 20 FPS MP4; it did not move the arm and therefore does not clear the readiness gate.AI assistance
Codex with GPT-5.6 assisted with design discussion, implementation, diagnosis, stack restructuring, tests, documentation, and PR drafting. The author reviewed the benchmark-parity and runtime decisions interactively.
Checklist