NeuroSenko commited on
Commit
94e80c7
·
verified ·
1 Parent(s): 09fb09f

Create README.md

Browse files
Files changed (1) hide show
  1. README.md +28 -0
README.md ADDED
@@ -0,0 +1,28 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ pipeline_tag: text-generation
3
+ license: other
4
+ license_name: modified-mit
5
+ license_link: https://github.com/MiniMax-AI/MiniMax-M2.7/blob/main/LICENSE
6
+ library_name: exllamav3
7
+ base_model: MiniMaxAI/MiniMax-M2.7
8
+ base_model_relation: quantized
9
+ tags:
10
+ - exl3
11
+ ---
12
+
13
+ Quantization was performed using [exllama3 v0.0.29](https://github.com/turboderp-org/exllamav3).
14
+
15
+ [4.0bpw](https://huggingface.co/NeuroSenko/MiniMax-M2.7-exl3/tree/4.0bpw)
16
+ [5.0bpw](https://huggingface.co/NeuroSenko/MiniMax-M2.7-exl3/tree/5.0bpw)
17
+
18
+ <details>
19
+ <summary>Quantization Notes</summary>
20
+
21
+ ### Inf/NaN values in calibration data
22
+
23
+ Some experts in the model produce `inf` values during calibration (e.g. experts 61 and 74 in the last layer had inf values in their down-projection calibration state). The `lm_head` layer also exhibited NaN values in its calibration state (445K NaN out of 1.5B elements).
24
+
25
+ This causes Cholesky decomposition to fail during quantization, as the Hessian matrix is no longer positive-definite. ExLlamaV3 does not handle this case gracefully — quantization crashes after exhausting retry attempts. A local patch was applied to fall back to uncalibrated quantization for the affected tensors. Given that only a handful of experts out of 256 in the last layer are affected, the impact on output quality is expected to be minimal.
26
+
27
+ This appears to be a property of the model weights themselves, not a bug in the quantizer.
28
+ </details>