2 ms·
It's nothing that tool calling/feeding it the correct information can't solve
by alexandra_au 1mo ago
It's nothing that tool calling/feeding it the correct information can't solve
- embedding-shape 1mo agoEven so, in this case, author is using UD-Q3_K_S dynamic weights for Qwen3.6-35B-A3B, it will be dumb. Even the BF16 weights do stupid stuff like missing to confirm all parameters are defined when doing "rm -rf directory/$id", so it ends up deleting more than expected, I can't imagine the Q3 are actually useful for anything serious, even with tool calling or what not.
- petruspennanen 1mo agoI've been very impressed by it's intelligence and lack of hallucinations. The dynamic Q3 is a good balance between accuracy and size keeping the 35B just below 16 GB. It is not supposed to know everything, it is your car. It actively disengages from off topic chatter (too slow for that anyway), better spend that time feeling the car. It keeps itself grounded on sensor input. One principle per wheel. assert only what you can sense, claim only what is verified, label anything interim loudly, and report failure plainly with no silver lining. Everything above those four patches is just suspension.
- embedding-shape 1mo ago> . The dynamic Q3 is a good balance between accuracy and size keeping I'm having a hard time understanding how you find any sort of accuracy in Q3, when I use it with BF16 and it's hardly usable due to drastic hallucinations and inability for system prompt following. But, if it works for you, that's pretty good! Guess I'm jealous :)
- petruspennanen 1mo agoHmm we must be doing something different, I think the official accuracy measurement for the Q3 is more than 90%. Maybe some bug affecting your test?