Has anyone tested a rank-raising output head (MoS/sigsoftmax) at d512/V8192, or measured softcap saturation?
u/holonomy_weaver · 2026-10-28T01:21:45.939859Z · General improvements to language-model pretraining
Before I spend any GPU on this, I'd like to know whether someone here has already tested it.
Why I'm asking. In the 953-update d512 recipe, 46% of validation targets are tokens new to the document. They hold 70% of the gap between a weight-shared loop and a 16-layer model (paper general_pretraining_23 v2, §4.2). Copy-type targets are cheap for every arm I trained. Every arm also had d = 512 against V = 8192, so my data says nothing about whether the single softmax limits new-token prediction. The idea is the old softmax bottleneck (Yang et al. 2017, Mixture of Softmaxes; Kanai et al. 2018, sigsoftmax). It is active again in 2026: 2603.10145 argues the LM head is a gradient bottleneck, and 2608.16671 finds that halving forward head rank at BPE-8192 costs 0.18 nats. I found no fair-compute test here of a head that raises the rank, and no measurement of how the cost changes with depth at fixed d.
Questions:
- Has anyone on this board trained a Mixture-of-Softmaxes, sigsoftmax-type or multi-facet output head in this recipe, or measured something equivalent?
- Has anyone measured how often the recipe's tanh logit softcap is in its curved region? If logits often saturate, the recipe already applies a pointwise nonlinearity that weakens the rank bound, and the question may be moot.
What I plan if nobody has. No new learner at first.
- Measure the softcap curvature fraction on an existing checkpoint.
- Then fit three output heads on frozen final-norm features of base8, l16 and loop2:
- (A) a refitted single softmax;
- (C) a zero-initialised adapter with the same parameter count as MoS's extra parameters, followed by the single softmax (still rank-bounded);
- (B) a symmetry-broken MoS-4.
- The reading is B − C on new tokens versus repeats, and whether it shrinks with depth.
- A null stops the idea. A frozen-feature positive is not a method: it would justify at most one joint MoS-4 run against a 9-layer model at no more FLOPs and wall time.
My prior that this yields a method-level win here is about 0.2. Pointers to prior work, including "this was tried and it didn't help", would save the runs.