Release RecoveryBench v1 - #27
Merged
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
Result
Under eight equal continuation updates, frozen-student KD reached 23.2% strict task success and 22.8% recovery after error; strict fresh-state OPD reached 10.9% and 9.1%. The paired fresh-minus-frozen differences are -12.24 points (95% paired bootstrap -15.89 to -8.59; 384 tasks) and -13.79 points (-20.69 to -6.90; 116 paired error cases).
Fresh OPD averaged 686.80 continuation seconds versus 52.10 seconds for frozen KD. The budget-50 selector queried 49.77% of model-generated positions but did not reduce teacher backbone forwards or wall time. The nominal 50-second artifact is explicitly reported as a cycle-capped diagnostic, not exact equal-time evidence.
Frozen artifacts
6ce2e6837e12b99ebc4fad6d27ce3e69c92e295ff3b9b60e0f68c2d308022384fe4c9afc799724dfe7a32e631676a1e5177c44559a7374d2ea31da135354f137425b0fa568f37b09e61af731d3da5009bd3833bddde6efaf2c66e9dba8355cbeaff96bffc6da27240a852410ac041bd4d95badf34cad030e6f437be1491a55ad8a6891f74aed80f07ec00d5ea1909895c579346e1abbb1d5d95a354bb46c6b81c506300599942445f24b30a4e0d7e01972c75daa7834f6d1eff5b8132dce93af53fc1d4d5b7adee09618d77ad62d4086ba56b78569832d6fc7c3bcd5c2695bbcAudit scope: 36 task artifacts, 4,608 trajectories and 101,787,618 raw bytes; every embedded digest/size matched, every arm has 128 paired test tasks, frozen checkpoints/datasets are reused exactly, and all 75 fresh updates have matching rollout/current parameter versions.
Validation
mypy src/miniverl, actionlint andgit diff --checkScope
This is a mechanism study on one Qwen3 pair, one SQLite recovery task family, three seeds and one RTX 4080. It is not an alignment benchmark and does not claim OPD universally loses, offline KD always wins, or local miniVERL execution is equivalent to distributed verl.