Repository navigation
docs(fold): milestone 2 accepted — proof runs, evaluation, width decision - #120
Merged
Merged
Conversation
…accepted Both proof runs stopped early (w128 at 34.2k, w256 at 21.6k): at step 20000 w256 beats w128 on CAMEO + CASP14 by +0.016 TM pooled, 95 % CI [0.013, 0.020], and the ESM-C checkpoints do not carry into M3. Acceptance uses 20k against 10k instead of 50k against 10k. Width 256. Records that both runs trained at an effective LR of 3.33e-4 (inherited adamw_lr_mult 0.333, #119), and fixes the eval script's empty pip-freeze.txt (uv is not installed in the eval venv). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #48
This PR records the milestone-2c proof runs, their offline evaluation and the pair-width decision. It accepts milestone 2.
Decision: pair width 256. At step 20000, w256 beats w128 on the held-out sets (
oplm fold compare, paired over targets, bootstrap 95 % CI):Deviations from the plan:
Acceptance:
docs/fold/m2/runs/.Finding (#119): both runs trained at an effective peak LR of 3.33e-4, not 1e-3. The fold configs inherit
adamw_lr_mult: 0.333from the MLM base recipe (483e91a, which landed after the configs were written). The width comparison is like for like, but spec §6.3's 1e-3 was never tried. M3 must setadamw_lr_mult: 1.0and settle its LR.Also in this PR:
docs/fold/b200-m2c-eval.sbatchwrote an emptypip-freeze.txt: it ranpython -m uvinside the venv, which doesn't have uv. The freeze step now runs before activation, with--python. This run's freeze was rebuilt from the venv's dist-info.Files:
docs/fold/m2/README.md: new section "Milestone 2c: proof runs and the width decision".docs/fold/m2/eval/: per-target CSVs, summaries, status, versions andvalid-curves.csv.docs/FOLD.md: status line, plus §10 Results.🤖 Generated with Claude Code