DeepSeek-V4.1-Flash-1017 RANMA Engram GGUF

[!WARNING] Requires ranma.cpp ranma_20261013 or newer (github.com/saturnsky/ranma.cpp). This is not a model on its own: it holds only the engram tables that the DeepSeek-V4.1-Flash-1017 GGUF files of ranma.cpp need. These are the 1017 tables: they do not work with the earlier DeepSeek-V4.1-Flash, and its tables do not work with 1017.

ranma.cpp is a llama.cpp fork developed with RDNA4 as its main target. It runs MoE models on a three-tier expert cache: VRAM, host RAM and SSD. It supports EXL3 quantization to keep memory traffic as low as possible at a given quality.

What this is

The two engram tables of deepseek-ai/DeepSeek-V4.1-Flash-1017 (layers 1 and 14, about 384 million rows each), taken from the original FP8 checkpoint without changing a value: each row is the FP8 E4M3 values and their E8M0 scales, stored as MXFP8. Every quantization of the model uses the same tables, so they live here once and the model repositories link to this one.

manifest.json lists the size and SHA-256 of every file.

Used by

• SaturnHeaven/DeepSeek-V4.1-Flash-1017-EXL3-2.9bpw-RANMA-EXL3-GGUF (2.9 bpw, LibertAIDAI)

Download the folder once and give ranma its first file, --engram-tables .../DeepSeek-V4.1-Flash-1017-engram-MXFP8-00001-of-00007.gguf; the other files are found by name. At load the tables are checked against the model (table names, rows, row width) and every piece is checked at both ends. The earlier tables have the same names, rows and row width, so this check cannot tell the two sets apart: keep them in separate folders. How the set is found and checked: engram-tables.md.

License

Same as the original model: MIT, see the original repository.