base_model: MaziyarPanahi/calme-2.2-qwen2-72b
datasets:
- MaziyarPanahi/truthy-dpo-v0.1-axolotl
language:
- en
library_name: transformers
license: other
license_name: tongyi-qianwen
license_link: https://huggingface.co/Qwen/Qwen2-72B-Instruct/blob/main/LICENSE
pipeline_tag: text-generation
tags:
- chat
- qwen
- qwen2
- finetune
- chatml
quantized_by: bartowski
inference: false
model_creator: MaziyarPanahi
model-index:
- name: calme-2.2-qwen2-72b
results:
- task:
type: text-generation
name: Text Generation
dataset:
name: IFEval (0-Shot)
type: HuggingFaceH4/ifeval
args:
num_few_shot: 0
metrics:
- type: inst_level_strict_acc and prompt_level_strict_acc
value: 80.08
name: strict accuracy
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
- task:
type: text-generation
name: Text Generation
dataset:
name: BBH (3-Shot)
type: BBH
args:
num_few_shot: 3
metrics:
- type: acc_norm
value: 56.8
name: normalized accuracy
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
- task:
type: text-generation
name: Text Generation
dataset:
name: MATH Lvl 5 (4-Shot)
type: hendrycks/competition_math
args:
num_few_shot: 4
metrics:
- type: exact_match
value: 41.16
name: exact match
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
- task:
type: text-generation
name: Text Generation
dataset:
name: GPQA (0-shot)
type: Idavidrein/gpqa
args:
num_few_shot: 0
metrics:
- type: acc_norm
value: 16.55
name: acc_norm
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
- task:
type: text-generation
name: Text Generation
dataset:
name: MuSR (0-shot)
type: TAUR-Lab/MuSR
args:
num_few_shot: 0
metrics:
- type: acc_norm
value: 16.52
name: acc_norm
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
- task:
type: text-generation
name: Text Generation
dataset:
name: MMLU-PRO (5-shot)
type: TIGER-Lab/MMLU-Pro
config: main
split: test
args:
num_few_shot: 5
metrics:
- type: acc
value: 49.27
name: accuracy
source:
url: >-
https://huggingface.co/spaces/open-llm-leaderboard/open_llm_leaderboard?query=MaziyarPanahi/calme-2.2-qwen2-72b
name: Open LLM Leaderboard
Llamacpp imatrix Quantizations of calme-2.2-qwen2-72b
Using llama.cpp release b3634 for quantization.
Original model: https://huggingface.co/MaziyarPanahi/calme-2.2-qwen2-72b
All quants made using imatrix option with dataset from here
Run them in LM Studio
Prompt format
<|im_start|>system
{system_prompt}<|im_end|>
<|im_start|>user
{prompt}<|im_end|>
<|im_start|>assistant
Download a file (not the whole branch) from below:
| Filename | Quant type | File Size | Split | Description |
|---|---|---|---|---|
| calme-2.2-qwen2-72b-Q8_0.gguf | Q8_0 | 77.26GB | true | Extremely high quality, generally unneeded but max available quant. |
| calme-2.2-qwen2-72b-Q6_K.gguf | Q6_K | 64.35GB | true | Very high quality, near perfect, recommended. |
| calme-2.2-qwen2-72b-Q5_K_M.gguf | Q5_K_M | 54.45GB | true | High quality, recommended. |
| calme-2.2-qwen2-72b-Q4_K_M.gguf | Q4_K_M | 47.42GB | false | Good quality, default size for must use cases, recommended. |
| calme-2.2-qwen2-72b-Q4_K_S.gguf | Q4_K_S | 43.89GB | false | Slightly lower quality with more space savings, recommended. |
| calme-2.2-qwen2-72b-Q4_0.gguf | Q4_0 | 41.38GB | false | Legacy format, generally not worth using over similarly sized formats |
| calme-2.2-qwen2-72b-Q4_0_4_4.gguf | Q4_0_4_4 | 41.23GB | false | Optimized for ARM inference. Should work well on all ARM chips, pick this if you're unsure. |
| calme-2.2-qwen2-72b-Q3_K_XL.gguf | Q3_K_XL | 40.60GB | false | Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability. |
| calme-2.2-qwen2-72b-IQ4_XS.gguf | IQ4_XS | 39.71GB | false | Decent quality, smaller than Q4_K_S with similar performance, recommended. |
| calme-2.2-qwen2-72b-Q3_K_L.gguf | Q3_K_L | 39.51GB | false | Lower quality but usable, good for low RAM availability. |
| calme-2.2-qwen2-72b-Q3_K_M.gguf | Q3_K_M | 37.70GB | false | Low quality. |
| calme-2.2-qwen2-72b-IQ3_M.gguf | IQ3_M | 35.50GB | false | Medium-low quality, new method with decent performance comparable to Q3_K_M. |
| calme-2.2-qwen2-72b-Q3_K_S.gguf | Q3_K_S | 34.49GB | false | Low quality, not recommended. |
| calme-2.2-qwen2-72b-IQ3_XXS.gguf | IQ3_XXS | 31.85GB | false | Lower quality, new method with decent performance, comparable to Q3 quants. |
| calme-2.2-qwen2-72b-Q2_K_L.gguf | Q2_K_L | 31.03GB | false | Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable. |
| calme-2.2-qwen2-72b-Q2_K.gguf | Q2_K | 29.81GB | false | Very low quality but surprisingly usable. |
| calme-2.2-qwen2-72b-IQ2_M.gguf | IQ2_M | 29.34GB | false | Relatively low quality, uses SOTA techniques to be surprisingly usable. |
| calme-2.2-qwen2-72b-IQ2_XS.gguf | IQ2_XS | 27.06GB | false | Low quality, uses SOTA techniques to be usable. |
| calme-2.2-qwen2-72b-IQ2_XXS.gguf | IQ2_XXS | 25.49GB | false | Very low quality, uses SOTA techniques to be usable. |
| calme-2.2-qwen2-72b-IQ1_M.gguf | IQ1_M | 23.74GB | false | Extremely low quality, not recommended. |
Q4_0_X_X
If you're using an ARM chip, the Q4_0_X_X quants will have a substantial speedup. Check out Q4_0_4_4 speed comparisons on the original pull request
To check which one would work best for your ARM chip, you can check AArch64 SoC features(thanks EloyOn!).
Embed/output weights
Some of these quants (Q3_K_XL, Q4_K_L etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.
Some say that this improves the quality, others don't notice any difference. If you use these models PLEASE COMMENT with your findings. I would like feedback that these are actually used and useful so I don't keep uploading quants no one is using.
Thanks!
Credits
Thank you kalomaze and Dampf for assistance in creating the imatrix calibration dataset
Thank you ZeroWw for the inspiration to experiment with embed/output
Downloading using huggingface-cli
First, make sure you have hugginface-cli installed:
pip install -U "huggingface_hub[cli]"
Then, you can target the specific file you want:
huggingface-cli download bartowski/calme-2.2-qwen2-72b-GGUF --include "calme-2.2-qwen2-72b-Q4_K_M.gguf" --local-dir ./
If the model is bigger than 50GB, it will have been split into multiple files. In order to download them all to a local folder, run:
huggingface-cli download bartowski/calme-2.2-qwen2-72b-GGUF --include "calme-2.2-qwen2-72b-Q8_0/*" --local-dir ./
You can either specify a new local-dir (calme-2.2-qwen2-72b-Q8_0) or download them all in place (./)
Which file should I choose?
A great write up with charts showing various performances is provided by Artefact2 here
The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.
If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.
If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.
Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.
If you don't want to think too much, grab one of the K-quants. These are in format 'QX_K_X', like Q5_K_M.
If you want to get more into the weeds, you can check out this extremely useful feature chart:
But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQX_X, like IQ3_M. These are newer and offer better performance for their size.
These I-quants can also be used on CPU and Apple Metal, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.
The I-quants are not compatible with Vulcan, which is also AMD, so if you have an AMD card double check if you're using the rocBLAS build or the Vulcan build. At the time of writing this, LM Studio has a preview with ROCm support, and other inference engines have specific builds for ROCm.
Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski