Self-quantized from Liquid's original weights with our own importance matrix. The
measurements
behind this card are public.
24B mixture of experts with 2B active per token: the 15.4 GB build fits a 24 GB machine with room for context.
We checked llama.cpp against Liquid's PyTorch code on the preview's first revision: llama.cpp's BF16 is closer to the exact fp32 model than PyTorch's own bf16 is.
This model is unusually sensitive to numerical precision. Read the KLD below against its floor, not against other models'.
AD-Q4_K_M
is the one to take
on a 24 GB machine. With 32 GB,
AD-Q6_K
is
nearly as close to the original as
AD-Q8_0
at 5 GB less. Below 16 GB, the
3-bit builds lose noticeably more; on this model the step from 4 to 3 bits
nearly doubles the divergence.
Every number is against the BF16 model's own logits, measured on one machine.
"Same top-1" is how often the build picks the same next token as the BF16 model.
Why the numbers look high
This model's output moves when the arithmetic changes, even when the weights do
not. We ran the same BF16 weights several ways, on the tokens and positions of
the reference above. This table was measured on the preview's first revision
(
c715ae25
); the current weights behave the same way at Q8_0 (0.063 against
0.064 then).
Comparison
Mean KLD
Median KLD
Same top-1
llama.cpp BF16, the same GPU twice
0.000
0.000
100.0%
llama.cpp BF16, CPU against GPU
0.019
0.002
95.2%
llama.cpp BF16 against exact fp32 (PyTorch)
0.024
0.006
92.1%
Liquid's PyTorch bf16 against exact fp32
0.053
0.018
89.7%
our
AD-Q8_0
against llama.cpp BF16
0.064
0.016
89.7%
Rounding the activations to bf16 alone moves this model by 0.02-0.05 KLD, where
most models move by around a thousandth. A Q8_0 at 0.064 is therefore the floor
here, not a defect of the build. It also means llama.cpp runs this architecture
correctly: its BF16 sits closer to the exact model than Liquid's own bf16 code
path. Compare the builds with each other and with
AD-Q8_0
; comparing these KLD
values with those of other models says more about the models than the quants.
How these were made
BF16
from Liquid's original safetensors (revision
f772950c
, the
"agentic checkpoint" of 12 October), converted with llama.cpp
980aef8c
. The source is BF16, so nothing is requantized; the chat template
is embedded.
Importance matrix
on the BF16 model, never on a quantized proxy: 8,994
chunks of 512 tokens from our calibration corpus, rendered through this
model's own chat template, with
--parse-special
. Agentic sessions and tool
calls 24%, code 18%, multilingual text 20%, reasoning 13%, long documents
11%, structured data 4%, graphics code 4%, vocabulary sweep 6%. Every one of
the 64 experts in all 38 MoE blocks saw at least 12.3k tokens, so no expert
is quantized blind.
Layout.
The rungs differ in the experts, which are nearly all of the
weights. Attention, the short-convolution mixers and the two dense blocks
stay at Q8_0 in every build, and the router is not quantized at all. The
embeddings are tied to the
output, so they stay at Q8_0 too (F16 in
AD-Q8_0
and
AD-Q6_K
). Blocks 34
and 36-39 get a step up, chosen by where the importance matrix saw the most
activation energy, not by a fixed fraction of the depth.
The importance matrix matters: on the first revision, the same
AD-Q4_K_M
layout without it measured 0.134 instead of 0.125.
Pass
--jinja
so the embedded chat template is used; without it llama.cpp falls
back to a generic one. Liquid's recommended sampling: temperature 0.1, top_k 50,
repetition penalty 1.05. Context goes up to 131,072 tokens. Needs a llama.cpp
build with
lfm2moe
and the LFM2.5 tokenizer, which upstream has.
In
Atomic Chat
:
search
AtomicChat/LFM2.5-24B-A2B-GGUF
, pick a build, hit
Use this model
.
Measurement
The reference is the BF16 model's logits over our held-out neutral set: 93
chunks of 4,096 tokens in 30 languages, BF16 PPL 15.67 ± 0.12. The calibration
corpus shares no 13-gram with it. One machine for everything: 1× H100 PCIe,
llama.cpp
980aef8c
. All logs, the importance matrix and the comparison above
are in the
metrics repository
.
Limitations
Built from the preview's revision
f772950c
(12 October); the public release
has the same weights, checked file by file.
Measured on general text only. Tool calling, long context and the thinking
channel were not tested on the quantized builds.
Not run yet on a Mac, in LM Studio or in Ollama.
License
LFM Open License v1.0, see
LICENSE
. Released by Liquid AI; quantized by Atomic Chat.
Runs of AtomicChat LFM2.5-24B-A2B-GGUF on huggingface.co
2.4K
Total runs
0
24-hour runs
263
3-day runs
2.4K
7-day runs
2.4K
30-day runs
More Information About LFM2.5-24B-A2B-GGUF huggingface.co Model
LFM2.5-24B-A2B-GGUF huggingface.co is an AI model on huggingface.co that provides LFM2.5-24B-A2B-GGUF's model effect (), which can be used instantly with this AtomicChat LFM2.5-24B-A2B-GGUF model. huggingface.co supports a free trial of the LFM2.5-24B-A2B-GGUF model, and also provides paid use of the LFM2.5-24B-A2B-GGUF. Support call LFM2.5-24B-A2B-GGUF model through api, including Node.js, Python, http.
LFM2.5-24B-A2B-GGUF huggingface.co is an online trial and call api platform, which integrates LFM2.5-24B-A2B-GGUF's modeling effects, including api services, and provides a free online trial of LFM2.5-24B-A2B-GGUF, you can try LFM2.5-24B-A2B-GGUF online for free by clicking the link below.
AtomicChat LFM2.5-24B-A2B-GGUF online free url in huggingface.co:
LFM2.5-24B-A2B-GGUF is an open source model from GitHub that offers a free installation service, and any user can find LFM2.5-24B-A2B-GGUF on GitHub to install. At the same time, huggingface.co provides the effect of LFM2.5-24B-A2B-GGUF install, users can directly use LFM2.5-24B-A2B-GGUF installed effect in huggingface.co for debugging and trial. It also supports api for free installation.
LFM2.5-24B-A2B-GGUF install url in huggingface.co: