Views
No views yet
Qwen/Qwen3.6-27B, which means a 52 GB
download before anything can run. Under llama.cpp the same adapter attaches to a
quantized base:| Base | Download | VRAM with this adapter |
|---|---|---|
Qwen3.6-27B-Q4_K_M.gguf | 15.7 GB | ~19 GB |
Qwen3.6-27B-IQ4_XS.gguf | 14.4 GB | ~18 GB |
Qwen3.6-27B-UD-Q3_K_XL.gguf | 13.5 GB | ~17 GB |
Qwen3.6-27B-UD-IQ2_M.gguf | 10.1 GB | ~13 GB |
| File | Size | Notes |
|---|---|---|
MiniMax-H3-Prompt-Rewriter-LoRA-F16.gguf | 3.48 GB | 992 tensors, rank 256, adapter.lora.alpha = 512 |
MiniMax-H3-Prompt-Rewriter-LoRA-Q8_0.gguf | 1.85 GB | the same adapter, quantised |
Q8_0 unless you have a reason not to. It is quantised from the F16 in
this repository rather than converted separately, so tensor names, their order
and every metadata field are identical — only the stored values differ, by a
mean of 0.001 relative across all 992 tensors and 0.004 on the worst one.[Shot 2] At 00:06.500, while the
unadapted base model writes plain ranges like (0s-4s) instead.1llama-cli \
2 -m Qwen3.6-27B-Q4_K_M.gguf \
3 --lora MiniMax-H3-Prompt-Rewriter-LoRA-Q8_0.gguf \
4 -sysf system_prompt.txt \
5 -p "resolution: 16:9
6duration: 15s
7original_prompt: A red fox walks through a snowy forest at dawn." \
8 -st -n 1400 --temp 0 -ngl 99 -c 8192 --reasoning offsystem_prompt.txt must hold the exact system prompt from
prompt_template.py
in the source repository — the adapter was trained on that wording, and changing
it degrades the rewrite.--reasoning off matters: it corresponds to the enable_thinking=False that the
reference infer.py passes. Without it the model spends hundreds of tokens
reasoning before starting the rewrite.Q4_K_M: 50 tok/s with the adapter, 78 tok/s
without it. That ~35% difference is llama.cpp computing the adapter's matmuls,
which is the simplest confirmation that it is actually applied.llama-cpp-python is installed. It fetches F16 by default; name
MiniMax-H3-Prompt-Rewriter-LoRA-Q8_0.gguf in the options node's adapter
field to take the smaller one instead and it is downloaded from here.convert_lora_to_gguf.py from llama.cpp, plus a one-hunk fix to
conversion/qwen.py.in_proj_qkv, in_proj_z, in_proj_a and in_proj_b that reorder lands on the
output dimension and a LoRA passes through untouched. For out_proj it lands on
the input dimension, where LoraTorchTensor.reshape refuses — it cannot
reshape the axis that lives on the A factor.reshape/permute/reshape. LoraTorchTensor.__getitem__ already routes a
last-axis index onto A, and(B @ A)[..., p] == B @ A[..., p]1elif ".out_proj." in name:
2 col_perm = self._reorder_v_heads(
3 torch.arange(num_v_heads * head_v_dim, dtype=torch.long).unsqueeze(0),
4 1, num_k_heads, num_v_per_k, head_v_dim,
5 ).squeeze(0)
6 data_torch = data_torch[..., col_perm]