The first adjusted model I've used that actually seems to be equal-or-better to previous alternatives

#2
by Tribbler - opened

Just wanted to say - good stuff. From my usage it seems equal-or-better to IQ3_XXS while being notably smaller.

Actually, upon further usage, there's something I did notice - this model seems significantly worse at vision than IQ3_XXS. It starts looping, cutting off output, etc. Might be worth checking out. Also looping propensity in general, possibly as a target for optimization.

This is something I've noticed too. It's very good at one shot tool calls, and is very good at interaction. So I need to do another ablation review targeting thinking, as that is what seems to cause the most loops. Thanks for trying it out, I hope it's of some use.

Thanks for the report — I investigated this today.

Short version: It is likely quantization damage from v1 being too aggressive, not a C++ bug. v1 put attention QKV and all routed expert weights at Q2_K across all 40 layers, which explains both vision degradation and reasoning looping.

v2 overrides already exist that protect attn_qkv + routed experts at Q3_K_M. I just need to build and test V2
Will update this thread when v2 is available.

Glad to hear that! Looking forward to it, and thank you for sharing the results of your work.

Correction after more testing: the vision issue was not confirmed quantization damage in the main v1 GGUF. The original upload was missing the required mmproj-F16.gguf vision projector, so image input was not packaged correctly.

I uploaded the missing mmproj-F16.gguf and updated the README with the proper llama.cpp command:

llama-server \
  --model Qwen3.6-35B-A3B-Cerebellum.gguf \
  --mmproj mmproj-F16.gguf \
  --n-gpu-layers 99 \
  --ctx-size 8192 \
  --reasoning off \
  --reasoning-budget 0

Retested with the projector attached:

Model Size Vision smoke RealWorldQA 200
Cerebellum v1 12 GB 36/36 156/200, 78.0%
Cerebellum v2 test build 15 GB 36/36 156/200, 78.0%
Stock Q3_K_M baseline 16 GB 36/36 155/200, 77.5%

So v1 with the proper vision file performs as well as the stock Q3_K_M baseline on this vision check. The v2 test build added about 3 GB and did not give a worthwhile gain, so I am keeping the corrected v1 package as the recommended release. Thanks again for catching/reporting the vision problem.

Sign up or log in to comment