You can deploy this model and start earning money today!

bartowski/
endless-frontier_BigBang-v1-GGUF

Name: endless-frontier_BigBang-v1-GGUF
Availability: InStock

gguf

image-text-to-text

endless-frontier/BigBang-v1

Views

No views yet

Llamacpp imatrix Quantizations of BigBang-v1 by endless-frontier

Using llama.cpp release b10262 for quantization.

Original model: https://huggingface.co/endless-frontier/BigBang-v1

Model details:

Parameter count: 36B
Input support: text, image (with mmproj file) - details
MTP: yes - details
imatrix: yes - details

How to run

Prompt format

<|im_start|>system
{system_prompt}<|im_end|>
<|im_start|>user
{prompt}<|im_end|>
<|im_start|>assistant
<think>

Don't know which to choose? Grab Q4_K_M (21.86GB) - usually a good mix of size and performance. Download instructions available here

Available files:

Filename	Quant type	File Size	Split	Description
endless-frontier_BigBang-v1-bf16.gguf	bf16	71.07GB	true	Full BF16 weights.
endless-frontier_BigBang-v1-Q8_0.gguf	Q8_0	37.81GB	false	Extremely high quality, generally unneeded but max available quant.
endless-frontier_BigBang-v1-Q6_K_L.gguf	Q6_K_L	30.77GB	false	Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
endless-frontier_BigBang-v1-Q6_K.gguf	Q6_K	30.53GB	false	Very high quality, near perfect, recommended.
endless-frontier_BigBang-v1-Q5_K_L.gguf	Q5_K_L	25.81GB	false	Uses Q8_0 for embed and output weights. High quality, recommended.
endless-frontier_BigBang-v1-Q5_K_M.gguf	Q5_K_M	25.49GB	false	High quality, recommended.
endless-frontier_BigBang-v1-Q5_K_S.gguf	Q5_K_S	24.63GB	false	High quality, recommended.
endless-frontier_BigBang-v1-Q4_1.gguf	Q4_1	22.45GB	false	Legacy format, similar performance to Q4_K_S but with improved tokens/watt on Apple silicon.
endless-frontier_BigBang-v1-Q4_K_L.gguf	Q4_K_L	22.24GB	false	Uses Q8_0 for embed and output weights. Good quality, recommended.
endless-frontier_BigBang-v1-Q4_K_M.gguf	Q4_K_M	21.86GB	false	Good quality, default size for most use cases, recommended.
endless-frontier_BigBang-v1-Q4_K_S.gguf	Q4_K_S	21.07GB	false	Slightly lower quality with more space savings, recommended.
endless-frontier_BigBang-v1-Q4_0.gguf	Q4_0	20.42GB	false	Legacy format, kept for compatibility with older tools.
endless-frontier_BigBang-v1-IQ4_NL.gguf	IQ4_NL	20.33GB	false	Similar to IQ4_XS, but slightly larger.
endless-frontier_BigBang-v1-IQ4_XS.gguf	IQ4_XS	19.28GB	false	Decent quality, smaller than Q4_K_S with similar performance, recommended.
endless-frontier_BigBang-v1-Q3_K_XL.gguf	Q3_K_XL	17.80GB	false	Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
endless-frontier_BigBang-v1-IQ3_M.gguf	IQ3_M	17.37GB	false	Medium-low quality, new method with decent performance comparable to Q3_K_M.
endless-frontier_BigBang-v1-Q3_K_L.gguf	Q3_K_L	17.36GB	false	Lower quality but usable, good for low RAM availability.
endless-frontier_BigBang-v1-Q3_K_M.gguf	Q3_K_M	16.70GB	false	Low quality.
endless-frontier_BigBang-v1-IQ3_XS.gguf	IQ3_XS	16.69GB	false	Lower quality, new method with decent performance, slightly better than Q3_K_S.
endless-frontier_BigBang-v1-Q3_K_S.gguf	Q3_K_S	15.98GB	false	Low quality, not recommended.
endless-frontier_BigBang-v1-IQ3_XXS.gguf	IQ3_XXS	15.34GB	false	Lower quality, new method with decent performance, comparable to Q3 quants.
endless-frontier_BigBang-v1-Q2_K_L.gguf	Q2_K_L	13.58GB	false	Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
endless-frontier_BigBang-v1-Q2_K.gguf	Q2_K	13.09GB	false	Very low quality but surprisingly usable.
endless-frontier_BigBang-v1-IQ2_M.gguf	IQ2_M	12.54GB	false	Relatively low quality, uses SOTA techniques to be surprisingly usable.
endless-frontier_BigBang-v1-IQ2_S.gguf	IQ2_S	11.49GB	false	Low quality, uses SOTA techniques to be usable.
endless-frontier_BigBang-v1-IQ2_XS.gguf	IQ2_XS	11.27GB	false	Low quality, uses SOTA techniques to be usable.
endless-frontier_BigBang-v1-IQ2_XXS.gguf	IQ2_XXS	10.26GB	false	Very low quality, uses SOTA techniques to be usable.

Download a specific file:

hf download bartowski/endless-frontier_BigBang-v1-GGUF --include "endless-frontier_BigBang-v1-Q4_K_M.gguf" --local-dir ./

Downloading using the Hugging Face CLI

Click to view download instructions

First, make sure you have the Hugging Face CLI installed:

pip install -U "huggingface_hub[cli]"

Download a specific file:

hf download bartowski/endless-frontier_BigBang-v1-GGUF --include "endless-frontier_BigBang-v1-Q4_K_M.gguf" --local-dir ./

The files marked true in the Split column above are stored as multiple parts in a folder. To download all the parts to a local folder, run:

hf download bartowski/endless-frontier_BigBang-v1-GGUF --include "endless-frontier_BigBang-v1-bf16/*" --local-dir ./

You can either specify a new local-dir (endless-frontier_BigBang-v1-bf16) or download them all in place (./)

How to run

These quants run with llama.cpp - installable in one line via llama.app:

curl -LsSf https://llama.app/install.sh | sh
llama-server -hf bartowski/endless-frontier_BigBang-v1-GGUF:Q4_K_M

llama-server includes a built-in chat web UI, served at http://localhost:8080 by default.

These quants were made with llama.cpp release b10262 - if this model's architecture is newly supported, you'll need that release or newer to run them.

They also work in: LM Studio · koboldcpp · ramalama · Jan AI · Text Generation Web UI · LoLLMs · Atomic Chat

Multimodal

This model supports image input. Alongside the quants, this repo includes the multimodal projector files mmproj-endless-frontier_BigBang-v1-f16.gguf and mmproj-endless-frontier_BigBang-v1-bf16.gguf, which pair with any quant above.

llama.cpp downloads the mmproj automatically when using -hf as shown above; if you're loading files manually, pass it with --mmproj.

MTP

This model has MTP (Multi-Token Prediction) layers, and they are included in these quants

MTP layers act as a built-in draft model, letting llama.cpp run speculative decoding for faster generation. To use them, add the following flag to your llama.cpp command:

--spec-type draft-mtp

Note: the MTP layers are stored at Q4_0 in the imatrix quants (except for the Q8_0 quant), since imatrix calibration does not exercise them. Q4_0 is chosen for its speed which massively benefits MTP performance.

imatrix

All quants made using imatrix option with dataset from here. The imatrix is available here: endless-frontier_BigBang-v1-imatrix.gguf.

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.

ARM/AVX information

llama.cpp automatically "repacks" weights into an interleaved layout at load time for faster inference on ARM and AVX machines - details in this PR. This once required downloading special Q4_0_4_4/4_8/8_8 files; those are long gone. Online repacking now covers Q4_0, IQ4_NL, and most K-quants, so no special quant choice is needed for CPU inference.

Which file should I choose?

Click here for details

An older (early 2024) but still useful write-up with charts comparing quant 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.

Hugging Face can also do this math for you: add your hardware in your Local Apps settings and the model page will show which files fit.

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:

llama.cpp feature matrix

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, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.

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.

Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski