AI正在发生 未来正在更新orcarouter_GLM-5.3-Flash-Uncensored-GGUF
GGUF quantizations of **orcarouter/GLM-5.3-Flash-Uncensored-FP8**, built with a custom importance matrix and measured rather than assumed. > ⚠️ **Uncensored model.** Safety refusals were removed by OrcaRouter. It will comply with > harmful, unethical, and illegal requests. Released for research — red-teaming, refusal- > mechanism study, robustness evaluation. You are responsible for what you do with it. > 🔧 **What happened, and where it stands (2026-09-06).** On 2026-09-05 a user reported > looping and incoherent output from `IQ2_S` (discussion #1). They were > right. The original build pinned only the `blk.45` MTP block at high precision; attention, > the **shared** experts, the three dense FFN blocks, and the embeddings were all quantized > down with the routed experts. The shared experts and attention run on every token. > > **`IQ2_S` was rebuilt on 2026-09-06** with those tensors held at `q8_0` (+7 GB) and tested > against the original on a rented H200: 12 tasks × 2 seeds × 2 samplers, same scorer, same > settings. Full table in **Coherence gate** below. Short version: the original failed 3 of 8 > coding tasks by reasoning to the output cap without ever answering; the rebuild passed > all 48, matching `IQ3_XXS`, which also passed all 48 on its original recipe. > **`IQ2_XXS` is being rebuilt the same way** and stays flagged until it passes the same gate. > > **Two corrections to earlier versions of this page.** The imatrix has **10 chunks, not 60** > (the run checkpointed at 10 and stopped; numerically sound, one uncovered expert row in > `blk.29`). And the repetition-penalty workaround I posted **did not change the outcome** on > this failure mode — 21/24 → 21/24 for the original file with and without it. It helps > n-gram repetition; it does not help a model that cannot emit the literal it intends. > The rebuilt files carry `repeat_penalty 1.1` in their metadata anyway, because it is cheap. > > Only `IQ3_XXS` had been benchmarked before publication, and I shipped all three off that. > That was the actual mistake. The gate below is the fix for the process, not just the file.
译文尚未就绪，显示来源原文
GGUF quantizations of **orcarouter/GLM-5.3-Flash-Uncensored-FP8**, built with a custom importance matrix and measured rather than assumed. > ⚠️ **Uncensored model.** Safety refusals were removed by OrcaRouter. It will comply with > harmful, unethical, and illegal requests. Released for research — red-teaming, refusal- > mechanism study, robustness evaluation. You are responsible for what you do with it. > 🔧 **What happened, and where it stands (2026-09-06).** On 2026-09-05 a user reported > looping and incoherent output from `IQ2_S` (discussion #1). They were > right. The original build pinned only the `blk.45` MTP block at high precision; attention, > the **shared** experts, the three dense FFN blocks, and the embeddings were all quantized > down with the routed experts. The shared experts and attention run on every token. > > **`IQ2_S` was rebuilt on 2026-09-06** with those tensors held at `q8_0` (+7 GB) and tested > against the original on a rented H200: 12 tasks × 2 seeds × 2 samplers, same scorer, same > settings. Full table in **Coherence gate** below. Short version: the original failed 3 of 8 > coding tasks by reasoning to the output cap without ever answering; the rebuild passed > all 48, matching `IQ3_XXS`, which also passed all 48 on its original recipe. > **`IQ2_XXS` is being rebuilt the same way** and stays flagged until it passes the same gate. > > **Two corrections to earlier versions of this page.** The imatrix has **10 chunks, not 60** > (the run checkpointed at 10 and stopped; numerically sound, one uncovered expert row in > `blk.29`). And the repetition-penalty workaround I posted **did not change the outcome** on > this failure mode — 21/24 → 21/24 for the original file with and without it. It helps > n-gram repetition; it does not help a model that cannot emit the literal it intends. > The rebuilt files carry `repeat_penalty 1.1` in their metadata anyway, because it is cheap. > > Only `IQ3_XXS` had been benchmarked before publication, and I shipped all three off that. > That was the actual mistake. The gate below is the fix for the process, not just the file.