docs(vision): mlx0330nv campaign — nvfp4 fleet on 0.33.0, and the 12b/31b think-on split - #229
Open
glennneuber wants to merge 1 commit into
Open
docs(vision): mlx0330nv campaign — nvfp4 fleet on 0.33.0, and the 12b/31b think-on split#229glennneuber wants to merge 1 commit into
glennneuber wants to merge 1 commit into
Conversation
… 12b/31b think-on split First vsuite campaign on 0.33.0-maxusai-21cfe88e (b10488 / MLX 27fec909), nvfp4 tags only by operator direction. All five models fully functional think-off at the 16384 start rung (scene 6/6 across the fleet, IoU 0.954-0.999). Think-on splits the gemma4 family: 31b converges at rung 1 (27/27 arms, max eval 3,539 of 8,192) while 12b runs away on the bbox arms under the same card:gemma4+temp0 sampling — 20/27 arms still capped at num_predict 57,344 — and was descoped mid-ceiling after ~9.5h. The learnings-log entry records the runaway with its scope fence against the 2026-08-13 off-policy-sampling finding; the 12b think-on cell stays open per ADR 0012 conv 9. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The first vsuite campaign on the v0.33.0 fold's build (
0.33.0-maxusai-21cfe88e, llama.cpp b10488 / MLX 27fec909), scoped by operator direction to nvfp4 tags only (no GGUF, mxfp8, or bf16). Two files: the campaign doc with both summarizer tables pasted verbatim, and the learnings-log entry for the gemma4:12b think-on runaway.Findings
card:gemma4+temp0): 25/27 arms capped at 8,192; 20/27 still capped at num_predict 57,344; descoped mid-131072 after ~9.5 h wall for 7 scores. The learnings-log entry is deliberately scope-fenced against the 2026-08-13 finding (which blamed off-policy sampling, on a different build and models) — this is a new observation, not a refutation.Provenance
One host (
10.8.0.3, native serve on:11436viaserve-apple-mlx.sh, cold server per cell), one build, campaign tagmlx0330nv1, power mode stamped per cell (the 12b think-off cell predates the powermode 0→2 shift; noted in Limits). Scores untracked on-host per convention; the doc and log entry are the durable record.🤖 Generated with Claude Code