anurag051194 commited on
Commit
7e1738b
·
verified ·
1 Parent(s): c4c0bcf

Update TwIL-LM3: weights, tokenizer and model card

Browse files
Files changed (1) hide show
  1. README.md +8 -5
README.md CHANGED
@@ -210,6 +210,8 @@ carried into the GGUF metadata, so chat mode works without extra flags.
210
  | file | quant | size | bits/weight | notes |
211
  |---|---|---:|---:|---|
212
  | `TwIL-LM3-Q4_K_M.gguf` | Q4_K_M | 1.78 GiB | 4.96 | recommended default; runs on CPU or 4 GB of VRAM |
 
 
213
  | `TwIL-LM3-Q8_0.gguf` | Q8_0 | 3.05 GiB | 8.50 | near-lossless, for quality-sensitive use |
214
  | `TwIL-LM3-F16.gguf` | F16 | 5.73 GiB | 16.00 | unquantized, for requantization or reference runs |
215
 
@@ -222,11 +224,12 @@ evaluation is greedy while the packaged sampling defaults are not. And leave the
222
  budget large — 2048 tokens or more — since the model emits a `<think>` block before answering
223
  and a short budget truncates it, which costs far more accuracy than the quantization does.
224
 
225
- F16 and Q8_0 were produced directly by `convert_hf_to_gguf.py` from the released bf16 weights;
226
- Q4_K_M was quantized from the F16 build with `llama-quantize`, without an importance matrix. All
227
- three were smoke-tested for load and generation on CPU. Note that F16 is not bit-identical to the
228
- released weights: bf16 and f16 carry the same 16 bits but trade exponent range against mantissa
229
- precision, so the conversion is a narrowing one, in practice negligible for inference.
 
230
 
231
  The published Track A and Track B numbers were measured on the **bf16** weights through vLLM, not
232
  on any of these GGUF builds, so expect small deviations — most likely at Q4_K_M — that have not
 
210
  | file | quant | size | bits/weight | notes |
211
  |---|---|---:|---:|---|
212
  | `TwIL-LM3-Q4_K_M.gguf` | Q4_K_M | 1.78 GiB | 4.96 | recommended default; runs on CPU or 4 GB of VRAM |
213
+ | `TwIL-LM3-Q5_K_M.gguf` | Q5_K_M | 2.06 GiB | 5.74 | a little more headroom than Q4_K_M |
214
+ | `TwIL-LM3-Q6_K.gguf` | Q6_K | 2.35 GiB | 6.56 | close to Q8_0 quality at two-thirds the size |
215
  | `TwIL-LM3-Q8_0.gguf` | Q8_0 | 3.05 GiB | 8.50 | near-lossless, for quality-sensitive use |
216
  | `TwIL-LM3-F16.gguf` | F16 | 5.73 GiB | 16.00 | unquantized, for requantization or reference runs |
217
 
 
224
  budget large — 2048 tokens or more — since the model emits a `<think>` block before answering
225
  and a short budget truncates it, which costs far more accuracy than the quantization does.
226
 
227
+ F16 and Q8_0 were produced directly by `convert_hf_to_gguf.py` from the released bf16 weights; the
228
+ K-quants (Q4_K_M, Q5_K_M, Q6_K) were quantized from the F16 build with `llama-quantize`, without
229
+ an importance matrix. All five were smoke-tested for load and generation on CPU. Note that F16 is
230
+ not bit-identical to the released weights: bf16 and f16 carry the same 16 bits but trade exponent
231
+ range against mantissa precision, so the conversion is a narrowing one, in practice negligible
232
+ for inference.
233
 
234
  The published Track A and Track B numbers were measured on the **bf16** weights through vLLM, not
235
  on any of these GGUF builds, so expect small deviations — most likely at Q4_K_M — that have not