Instructions to use QuantPasture/Step-3.5-Flash-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use QuantPasture/Step-3.5-Flash-GGUF with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Use Docker
docker model run hf.co/QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use QuantPasture/Step-3.5-Flash-GGUF with Ollama:
ollama run hf.co/QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use QuantPasture/Step-3.5-Flash-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use QuantPasture/Step-3.5-Flash-GGUF with Docker Model Runner:
docker model run hf.co/QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
- Lemonade
How to use QuantPasture/Step-3.5-Flash-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Step-3.5-Flash-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use QuantPasture/Step-3.5-Flash-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use QuantPasture/Step-3.5-Flash-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "QuantPasture/Step-3.5-Flash-GGUF:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Great custom quant!
This IQ4_XS quant seems to have an excellent size-to-performance ratio, thanks! Would you mind sharing your quant recipe / regex that you used? I am seeing:
ffn_down_exps.weight -> IQ4_XS
ffn_gate_exps.weight -> IQ3_S
ffn_up_exps.weight -> IQ3_S
And how did you get to these particular choices? I am trying to learn as much as I can. Thanks! :)
@Mushoz Thanks!
You've got the recipe correct there, yes. @ddh0 and I found that quantizing the routed experts and leaving the rest of the model in Q8_0 leads to better KLD and long-term context performance compared to normal llama.cpp quantization recipes which quant the entire model to various degrees. Eg, a regular Q4_K_M quant would quant the attention tensors too, etc.
Because these large MoE's have most of their model size in the routed experts though, you're looking at like 85%+ of the model is just in those conditional weights. Overall size wise going from Q8 to Q4 for the non-routed-experts is shaving only a few GB off the entire model but you're trading a lot of accuracy for that.
Basically, it's better to quant the sparse areas instead which are the routed experts. The UP and GATE tensors are a little less quantization sensitive than the DOWN tensors are from experimentation, so it's recommended to keep the DOWN tensors +1 quantization level in quality compared to the other two. There are also some fused optimizations that can be used when UP and GATE are the same quantization level, so you typically want to keep those the same.
The recipe for the IQ4_XS is as you say:
MIX=IQ4_XS
TYPE_FFN_UP_EXPS=IQ3_S
TYPE_FFN_GATE_EXPS=IQ3_S
TYPE_FFN_DOWN_EXPS=IQ4_XS
TYPE_DEFAULT=Q8_0
and I have a quantization script that takes those recipes and produces quants from them (lots of variable replacement in the script):
./build/bin/llama-quantize \
--tensor-type ffn_up_exps=$TYPE_FFN_UP_EXPS \
--tensor-type ffn_gate_exps=$TYPE_FFN_GATE_EXPS \
--tensor-type ffn_down_exps=$TYPE_FFN_DOWN_EXPS \
--imatrix $imatrix $gguf $output_filename $TYPE_DEFAULT
The total model BPW comes in at just about what an IQ4_XS is so I named it that, even though it isn't 100% accurate. The other quant recipes are similar but I've misplaced their precise recipes, it's a similar pattern though and you could inspect the ggufs to recreate it.
You've got the recipe correct there, yes. @ddh0 and I found that quantizing the routed experts and leaving the rest of the model in Q8_0 leads to better KLD and long-term context performance compared to normal llama.cpp quantization recipes which quant the entire model to various degrees. Eg, a regular Q4_K_M quant would quant the attention tensors too, etc.
...
^^ this is like finding a nugget of gold on a walk around the park. 🅰😉