Spaces:
Running on Zero
Running on Zero
Commit History
16 days ago
-
The arms fitted on the final mini-beatrix-3 core, the lookup arm's versions, and the four control twins of 2s. On mini-beatrix-3's final checkpoint (step 245,674, still opening bare) the arm list now holds the arm sets (stages 1-4, stages 1-8, the caption set, the research sets; two seeds each), served one row per set with a box per arm so any subset runs; the sixteen solo arms; and every version of the lookup arm (softmax attention after blocks 2, 6, 12 and 20, born at zero), mounted through amoe 0.2.12 from the arm's own tensors, which are read from the checkpoint by range request when no arm-only file exists. The lookup rows get recall prompts in the Completion tab and an activity line per site; the set rows get each member stage's prompts. The run's own stage programs (the checkpoints to step 148,000) use the same member switch. New crafts: mini-beatrix-2s-control (the original softmax twin) and its re-runs -attn-fp16-r10k (still training), -attn-fp16 and -bf16 (stopped), decoded in fp32. Pin: amoe-lora 5c934cf -> 9b1942d (v0.2.12); geolip-alephllm unchanged.
Verified signature70c3e58
-
ready for the arm-file conversion: amoe-lora pinned to 0.2.6 (5c934cf), whose load_anchor reads a block anchor in either format by content, so the mission's arm files may become real safetensors files at any time and this Space keeps serving them. Provenance is read per format: a real safetensors anchor through load_anchor, every other arm file (anchor, dispatch, relay-EMA, recurrent torch archives) as a torch archive. Tested on torch 2.13 with 0.2.6: the v3 arm gives bit-identical outputs from either format, a program with one member of each format mounts, and the 2s anchor, stack, routed, relay_ema and recurrent rows mount, write and detach bit-exact. Previous commit: fix: mini-beatrix-3's stage arm was downloaded at boot but never mounted. torch 2.13 (what this Space installs) reads any PATH ending in .safetensors as a safetensors file, and the mission's arm files are torch archives under that name, so reading their metadata failed and the provenance check refused the arm without a word. Every arm file is now read by content through an open handle (all six mount types retested on torch 2.13: the v3 program, and the 2s anchor, stack, routed, relay_ema and recurrent rows mount, write and detach bit-exact), a refused arm now says why in the log, and every arm file fetched and every mount is logged. Previous commit: mini-beatrix-3's stage arms: the arms the mission trains WITH the core ship beside every checkpoint, and the Space now serves each checkpoint's arms together as one program (arm_mount 'program': nested in stage order as the trainer attached them, all on by default, each switchable exactly; 'only' and 'without' rows appear once there are two). v3 decodes in fp32 in every row: measured on the 4090, bf16 changed greedy text between arm on and off where the arm's true effect is ~1e-9 nats/byte, fp32 did not (and fp32 is not slower here). After each run the stats line reads each live arm's activity on that text (KL of arm-off vs the program, fp32). Stage prompts in Completion, shown only for a program. Pins unchanged: the pinned model code is bit-identical to the mission's on the step-94,000 core, bare, armed, masked, detached and cached
Verified signature0665cc0 -
fix: mini-beatrix-3's stage arm was downloaded at boot but never mounted. torch 2.13 (what this Space installs) reads any PATH ending in .safetensors as a safetensors file, and the mission's arm files are torch archives under that name, so reading their metadata failed and the provenance check refused the arm without a word. Every arm file is now read by content through an open handle (all six mount types retested on torch 2.13: the v3 program, and the 2s anchor, stack, routed, relay_ema and recurrent rows mount, write and detach bit-exact), a refused arm now says why in the log, and every arm file fetched and every mount is logged. Previous commit: mini-beatrix-3's stage arms: the arms the mission trains WITH the core ship beside every checkpoint, and the Space now serves each checkpoint's arms together as one program (arm_mount 'program': nested in stage order as the trainer attached them, all on by default, each switchable exactly; 'only' and 'without' rows appear once there are two). v3 decodes in fp32 in every row: measured on the 4090, bf16 changed greedy text between arm on and off where the arm's true effect is ~1e-9 nats/byte, fp32 did not (and fp32 is not slower here). After each run the stats line reads each live arm's activity on that text (KL of arm-off vs the program, fp32). Stage prompts in Completion, shown only for a program. Pins unchanged: the pinned model code is bit-identical to the mission's on the step-94,000 core, bare, armed, masked, detached and cached
Verified signature83bddd9 -
mini-beatrix-3's stage arms: the arms the mission trains WITH the core ship beside every checkpoint, and the Space now serves each checkpoint's arms together as one program (arm_mount 'program': nested in stage order as the trainer attached them, all on by default, each switchable exactly; 'only' and 'without' rows appear once there are two). v3 decodes in fp32 in every row: measured on the 4090, bf16 changed greedy text between arm on and off where the arm's true effect is ~1e-9 nats/byte, fp32 did not (and fp32 is not slower here). After each run the stats line reads each live arm's activity on that text (KL of arm-off vs the program, fp32). Stage prompts in Completion, shown only for a program. Pins unchanged: the pinned model code is bit-identical to the mission's on the step-94,000 core, bare, armed, masked, detached and cached
Verified signature8f2876d
-
serve the full 2s arm library (single, stacked, routed, gain, memory and recurrent arms) with the best-measured arm as default; text-frame arms get their own frame on the specials craft
Verified signature9f4bf83