External validation: Clef-Flash Q4_K_M on Radeon RX 6800 (llama.cpp b11389, Vulkan, Windows) - finite typed probabilities, monotone confidence calibration on a robotics decision task

#1
by An2333 - opened

Setup

  • llama.cpp b11389, llama-server, win-vulkan-x64 build, AMD Radeon RX 6800 16 GB
  • Clef-Flash-Q4_K_M.gguf, flags: -ngl 99 -ub 32768 -c 16384 --host 0.0.0.0 --port 11435
    (the large physical batch matches what others found: the decision head wants the whole
    input covered by one batch)
  • Typed /v1/systemone-style decision requests; clients run inside WSL2 Ubuntu and reach
    the Windows-side server over the NAT gateway β€” no issues
  • output_tokens: 0 on every single request β€” the no-generation, no-parse property holds

Why llama.cpp and not Ollama: Ollama 0.35.1 (Windows) fails every systemone request on
this model with Clef: non-finite logit regardless of backend (CUDA/ROCm/Vulkan/CPU,
ollama#18769). Upstream llama.cpp b11389 with this GGUF is what works β€” including the
smaller Q4_K_M quant, which the issue had not tested.

Evaluation (n=35 recorded decision states, robotics action-selection)

Task: at each step the model must choose the next action among 5 typed options
(observe / pick / place / verify / abort) given a canonical world-state snapshot,
for a simulated robotic workcell. Ground truth = a frozen deterministic reference
policy; we score agreement per confidence bin (offline replay, no execution):

reported confidence n agreements (vs reference)
[0.0, 0.5) 11 0
[0.5, 0.8) 11 9
[0.8, 1.0] 8 8
  • Overall agreement 17/30 on the calibration split (baseline: a generative 1.5B model
    producing JSON text scored 4/30 with heavy truncation/parse failures β€” zero here)
  • The confidence bins are monotone: the model "knows when it does not know"
    (low-confidence picks are 0/11), and the top bin is clean (Wilson lower bound 0.676)
  • Median decision latency 1.9 s, max 6.8 s (Vulkan, 16 GB VRAM, Q4_K_M)

Takeaway: Q4_K_M quantization preserves the decision head's behavior, the
probabilities are meaningfully calibrated as a routing signal (we use them to decide
when to escalate to a larger LLM), and the vulkan build makes the model practical on
consumer AMD cards under Windows.

Happy to share the evaluation harness (a small Python client for the systemone
endpoint + the binning/Wilson script) if useful.

(Evaluation harness: a small typed /v1/systemone client + Wilson binned-agreement script, available on request.)

Sign up or log in to comment