The dataset viewer is not available because its heuristics could not detect any supported data files. You can try uploading some data files, or configuring the data files location manually.
Basalt BF16 KL-divergence bases
The full-precision references that Basalt scores its packs against. With these, anyone can run the same quality gate: PPL, mean KLD and top-1 agreement against the original model in BF16, on their own build or self-converted pack.
| File | Model | Made from | Base PPL | Size | sha256 |
|---|---|---|---|---|---|
flashnext-bf16-base.kld |
Qwen3.8-Flash-Next | unsloth's BF16 GGUF through llama-perplexity (llama.cpp 436f6f89e), -b 8192 -ub 8192 |
3.2749 | 13GB | c4e0221632607324d314556b8813d772867c300454ecdea37f1bf9d5555cf1a9 |
dsv41-bf16-base.kld |
DeepSeek-V4.1-Flash | a BF16 GGUF by @giveen (convert_hf_to_gguf --outtype bf16, llama.cpp 330f0189) |
2.7394 | 6.6GB | f3b1a7e2d6d9ab47b98f7c18de8558a2455f907aae2f26dd53144f484aa63608 |
Both bases cover wikitext-2 (wiki.test.raw) in 100 chunks of 512 tokens, written by llama-perplexity --kl-divergence-base. They store
the tokens and the full-vocabulary log-probabilities of every scored position.
Use
basalt-bench --model PACK.basalt --quality 100 --kld-base flashnext-bf16-base.kld
Use 20 chunks for a quick check and 100 for a numerics change. The method (scored rows, verify windows, pinned placement for identity) is in How quality is measured. Scores move slightly with placement, so pin the tiers when comparing two builds.
Credits
The DeepSeek base comes from @giveen's BF16 GGUF. The Flash-Next base comes from unsloth's BF16 GGUF. Both are derived from the original models and follow their licenses.
- Downloads last month
- 58