Add the single-GPU verl-style OPD plan and run path - #61
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
miniverl planand validatedminiverl runworkflows for the pinned verl v0.8-style single-GPU OPD profileWhy
The compiler and loss conformance work had no cohesive user path from source Parquet to a resumable local run and loadable adapter. This change exposes that path while keeping every scientific result frozen and making measured versus estimated planning fields explicit.
Validation
ruff check .ruff format --check .mypy src/miniverlactionlintpytest -q -m "not gpu and not network" --cov=miniverl— 2174 passed, 8 skipped, 85% branch coveragepytest -q -m gpu— 8 passedpytest -q -m network— 15 passed7aed6b230776f963fa09509c10d9c3a767d1102cmkdocs build --stricttwine check53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbcScope boundary
The measured record proves one local single-GPU runtime and artifact path. It does not evaluate alignment quality, compare OPD with SFT/DPO/KD, or claim distributed verl execution.