feat(eval): integrate LIBERO-PRO code-policy benchmark - #3439
Draft
TomCC7 wants to merge 1 commit into
Draft
Conversation
❌ 4 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
1 task
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 is comparable with the original benchmark while exercising the same unified, realtime policy interface intended for physical robots. LIBERO and its simulator dependencies must not leak into the host Python environment, and benchmark-owned lifecycle and scoring state must remain unavailable to submitted policies.
Solution
Integrate one end-to-end LIBERO-PRO single-trial evaluation on top of #3434:
libero-proevaluation, strict smoke-case JSON, CLI coverage, documentation, and architecture decisionsThe first integration intentionally evaluates one initialization of one task. Parallel and batched execution remain out of scope for this PR.
How to Test
Build prerequisites and run the actual evaluation:
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 automated tests:
Validated locally with Podman: one scored trial completed 300 policy ticks, emitted the native
0.0score, and produced a 301-frame, 20 FPS MP4 with valid frames from both cameras. The focused suite passes 21 tests.AI assistance
Codex with GPT-5.6 assisted with design discussion, implementation, diagnosis, tests, documentation, and PR drafting. The architecture and benchmark-parity decisions were reviewed interactively by the author.
Checklist