[Non-record] CAGE5 Colab T4 smoke: strictly causal 5-gram mixer#804
[Non-record] CAGE5 Colab T4 smoke: strictly causal 5-gram mixer#804Devchandrasen wants to merge 3 commits intoopenai:mainfrom
Conversation
Community Review — [Non-record] CAGE5 Colab T4 smoke: strictly causal 5-gram mixerBPB: 2.6981 | Compliance: LOOKS CLEAN — score-first-per-chunk TTT (legal #1416/#1423 pattern) What I found in the code (head SHA The TTT path at line 1182 implements the score-first-per-chunk pattern: each chunk is scored under Per Issue #402 and Issue #677, TTT is legal when each token is scored before the adapter updates on it, and that's what the code does here — chunk CPU smoke test (CT2038 proteus-engine, 2026-04-11): import OK in 0.04s, dim=512, layers=11, vocab=1024, code=94276 B, SMOKE_TEST_PASS Verdict: LOOKS CLEAN. Recommendation to @cocohearts @valerio-oai @0hq @yuzhougu-oai @notapplica: MERGE pending standard checks (3-seed validation, 16MB artifact cap, 10-min wallclock on 8×H100 SXM). The compliance picture matches the legal reference frontier and no flags were raised by the classification pass. Auto-classification caveat: this review was drafted by the AST-based classifier against a template derived from manually-reviewed cluster PRs (#1420, #1450, #1487, #1541, #1529, #1533, #1518). If I've misread a subtlety in your eval path — e.g., multi-epoch TTT that I mistook for single-pass, or a target-in-key lookup I missed in a helper function — please flag it and I'll re-run the audit manually. Reviewed by @MatoTeziTanka — The Agora. CPU smoke test (CT2038 proteus-engine, 2026-04-11): import OK in 0.04s, dim=512, layers=11, vocab=1024, code=94276 B, SMOKE_TEST_PASS. Classification via deterministic AST-based |
This PR adds a non-record 16MB smoke submission under
records/track_non_record_16mb/2026-03-26_CAGE5_ColabT4_Smoke/.Summary:
train.log:final_int8_zlib_roundtrip_exact val_bpb=2.69806373656896bytesIncluded files:
train_gpt.pyflash_attn_interface.pytrain.logsubmission.jsonREADME.mdrequirements.txt