6L Depth Minimalism + U-Net + Sliding Window — val_bpb 1.2026#1527
6L Depth Minimalism + U-Net + Sliding Window — val_bpb 1.2026#1527alphastar1111 wants to merge 2 commits intoopenai:mainfrom
Conversation
Community Review — 6L Depth Minimalism + U-Net + Sliding Window — val_bpb 1.2026BPB: 1.2026 | Compliance: LOOKS CLEAN — pure-neural submission, no TTT/SLOT/n-gram-cache What I found in the code (head SHA Static code review found no TTT adaptation function, no SLOT optimization loop, no n-gram-cache class, and no pre-quant val-token fine-tune. The eval path uses the standard sliding-window stride-64 pattern. The submission is a pure-neural architecture iteration on the standard SP1024/SP4096/SP8192 baseline. CPU smoke test (CT2038 proteus-engine, 2026-04-11): import OK in 0.03s, dim=512, layers=6, vocab=1024, code=56975 B, SMOKE_TEST_PASS Verdict: LOOKS CLEAN. Recommendation to @cocohearts @valerio-oai @0hq @yuzhougu-oai @notapplica: MERGE pending the usual record-track checks (3-seed validation, under-16MB artifact cap, ≤600s train + ≤600s eval on 8×H100 SXM). No compliance flags from the classification pass — this looks like a clean pure-neural iteration on the standard baseline. Auto-classification caveat: this review was drafted by the AST-based classifier. If there's a non-standard eval mechanism (logit postprocessing, hedge mixing, etc.) that I missed because it's factored into a helper file or a non-standard function name, 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.03s, dim=512, layers=6, vocab=1024, code=56975 B, SMOKE_TEST_PASS. Classification via deterministic AST-based |
Summary
parameters
705.97ms/43.54ms = 16.2x)
Approach
Five architectural bets compensate for extreme depth reduction:
Credits
records/track_10min_16mb/2026-03-19_SlidingWindowEval/README.md submission
records/track_10min_16mb/2026-03-18_LongContextSeq2048/README.md
Hardware details
Trained on 1xA100 80GB (not 8xH100). Calibration math and caveats about small-batch GPU inefficiency are
detailed in the README. MAX_WALLCLOCK_SECONDS=600 warmdown handles graceful cutoff if timing estimate is
off.
Test plan