Non-record: SP8192 + RandProj384 tied embeddings + Pairwise-QK Muon -- Single-seed negative result#2149
Open
YaseenHQ wants to merge 1 commit into
Open
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
This is a non-record submission testing two new ideas on the SP8192 / CaseOps / legal-TTT stack:
RandProj384)PairMuonQK)This run completed training and quantization on 8xH100 SXM within the 10-minute training cap and produced a legal sub-16MB artifact, but it was not competitive with the frontier. I am submitting it as a negative result because the failure is clear and informative.
Single-seed result
Seed:
421724599714 msval_loss 2.4662,val_bpb 1.1269val_loss 2.47020597,val_bpb 1.1286893615,399,365bytes15,438,770bytes561,230bytesWhat happened
The artifact fit comfortably under the size limit, but model quality regressed too far from the public frontier before quantization and before TTT could help.
The post-training legal TTT eval path also did not complete robustly on this stack:
As a result, I am explicitly not claiming a final post-TTT score.
Why this is still useful
This result directly constrains the design space:
1.1269pre-TTT BPB, more than0.06worse than the strongest open public frontier)Why this is non-record
Included files
train_gpt.pyrequirements.txttrain_seed42.logttt_eval_seed42_fail.logsubmission.json