meta-models/Muse-Glimmer-30B in TheFormalEra.Spec.Registry. The constants below are transcribed from its published config.json, and the official transformers.MuseGlimmerForConditionalGeneration is checked against them.
At a glance
What to watch for
- Layer
iis global iffi % 4 = 3: 13 global layers and 39 sliding-window layers with a window of 2048. The global layers are exactly the NoPE layers (museGlimmer_global_iff_nope): they use no position encoding. - 32 query heads and 2 KV heads (16 query heads per KV head), head dim 128. Queries and keys get an unweighted RMSNorm; queries are then multiplied by 3.87.
- Every layer has a sigmoid output gate from a separate projection (
attn.gate). - RMSNorm weights are applied as
(1 + w)(rmsnormOffset), except the final norm, which usesw. Sandwich norms use ε = 1e-8. - The embedding is followed by an unweighted RMSNorm. Logits are multiplied by 0.19611613513818404, then soft-capped:
20 · tanh(z / 20). - Scope: the text-only path. The vision tower is out of scope.
Compute-graph nodes
Use these paths in Spec Keys:meta-models/Muse-Glimmer-30B@1.0:layers[*].<node> for per-layer nodes, meta-models/Muse-Glimmer-30B@1.0:<node> for the others.
Nodes listed twice have different constants in different layers (for example, sliding-window and global attention). A kernel annotated with
layers[*].<node> is verified against each variant.
Tensors of the main nodes
Conformance
The officialtransformers.MuseGlimmerForConditionalGeneration agrees with this spec, layer by layer in float64, to a maximum relative error of 7.7e-15 (reduced-width profile, 2 weight draws × 2 lengths).
Published configuration
The hyperparameters as the spec renders them (config.json form)
The hyperparameters as the spec renders them (config.json form)
