Views
No views yet
[!TIP] The method is a REAP × REAM hybrid — not purely either. Experts are pruned REAP-style: ranked by how much they actually contribute on real traffic, with the survivors copied over byte-for-byte, untouched. But the keep-list isn't a plain top-N — every domain (Russian, code, tool use, math…) gets a protected quota of its own specialists. And the few experts that turned out to be near-duplicates were merged REAM-style instead of dropped. The router is then re-balanced so the smaller crew is used the way the original was. All of it in one step from the original model — no cascades.
[!IMPORTANT] This checkpoint keeps the original packed FP4/FP8 weight layout and the custom 0731 architecture. It is not loadable with stocktransformersgeneration, vLLM or SGLang — it exists for the DS4 fork toolchain and for making quantized builds. Want something you can just run? Grab the ready 2-bit build: DeepSeek-V4-Flash-0731-REAM144-163B-DS4-GGUF.
[!WARNING] Live smoke testing passed 7/10 scenarios on the first run. Independent reruns show the failures (Tool calling (DSML), Code refactoring, Tool call → code chain) are intermittent, not absolute — see the Stability column below for per-scenario pass rates. Multilingual chat, reasoning and long dialogs are consistently healthy.
AutoConfig / AutoTokenizer; per-layer
pruning choices are recorded in SELECTION.json.mtp.* tensor namespace. In the GGUF release
it ships as a separate optional file — see the companion repo.deepseek-ai/DeepSeek-V4-Flash-0731
over a ~5-million-token calibration mix (multi-turn dialogs, thinking and direct modes,
rendered with the model's own chat encoder). The strongest experts of every domain were
protected from pruning, the survivors were carried over byte-identical, and the
router was re-balanced to keep the original selection behavior.| Calibration domain | Share |
|---|---|
| Code | 35% |
| Agentic / tool use | 19% |
| Multilingual chat | 16% |
| Math | 8% |
| General chat | 6% |
| Roleplay | 6% |
| Russian | 5% |
| Long docs | 4% |
-exp names),
which degraded badly in multi-turn use.SMOKE_REPORT.json).| Scenario | First run | Stability (reruns) |
|---|---|---|
| Russian wordplay, multi-turn | ✅ | — |
| English → Russian code-switching | ✅ | — |
| Code Q&A over a 4k-token file | ✅ | — |
| Tool calling (DSML) | ❌ | 5/10 |
| Russian multi-turn reasoning | ✅ | — |
| Spanish creative writing | ✅ | — |
| Code refactoring | ❌ | 8/10 |
| Chinese summarization | ✅ | — |
| Long-dialog focus (drift check) | ✅ | — |
| Tool call → code chain | ❌ | 5/10 |