Instructions to use ji-farthing/RalphSeek-V4-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 ji-farthing/RalphSeek-V4-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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32 # Run inference directly in the terminal: llama cli -hf ji-farthing/RalphSeek-V4-Flash-GGUF:F32
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf ji-farthing/RalphSeek-V4-Flash-GGUF:F32 # Run inference directly in the terminal: llama cli -hf ji-farthing/RalphSeek-V4-Flash-GGUF:F32
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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32 # Run inference directly in the terminal: ./llama-cli -hf ji-farthing/RalphSeek-V4-Flash-GGUF:F32
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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32 # Run inference directly in the terminal: ./build/bin/llama-cli -hf ji-farthing/RalphSeek-V4-Flash-GGUF:F32
Use Docker
docker model run hf.co/ji-farthing/RalphSeek-V4-Flash-GGUF:F32
- LM Studio
- Jan
- vLLM
How to use ji-farthing/RalphSeek-V4-Flash-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "ji-farthing/RalphSeek-V4-Flash-GGUF" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "ji-farthing/RalphSeek-V4-Flash-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/ji-farthing/RalphSeek-V4-Flash-GGUF:F32
- Ollama
How to use ji-farthing/RalphSeek-V4-Flash-GGUF with Ollama:
ollama run hf.co/ji-farthing/RalphSeek-V4-Flash-GGUF:F32
- Unsloth Studio
How to use ji-farthing/RalphSeek-V4-Flash-GGUF with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for ji-farthing/RalphSeek-V4-Flash-GGUF to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for ji-farthing/RalphSeek-V4-Flash-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for ji-farthing/RalphSeek-V4-Flash-GGUF to start chatting
- Pi
How to use ji-farthing/RalphSeek-V4-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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "ji-farthing/RalphSeek-V4-Flash-GGUF:F32" } ] } } }Run Pi
# Start Pi in your project directory: pi
- OpenClaw new
How to use ji-farthing/RalphSeek-V4-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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32
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 "ji-farthing/RalphSeek-V4-Flash-GGUF:F32" \ --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"
- Docker Model Runner
How to use ji-farthing/RalphSeek-V4-Flash-GGUF with Docker Model Runner:
docker model run hf.co/ji-farthing/RalphSeek-V4-Flash-GGUF:F32
- Lemonade
How to use ji-farthing/RalphSeek-V4-Flash-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull ji-farthing/RalphSeek-V4-Flash-GGUF:F32
Run and chat with the model
lemonade run user.RalphSeek-V4-Flash-GGUF-F32
List all available models
lemonade list
- Hermes Agent
How to use ji-farthing/RalphSeek-V4-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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32
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 ji-farthing/RalphSeek-V4-Flash-GGUF:F32
Run Hermes
hermes
- Atomic Chat
RalphSeek V4 Flash (tiny DeepSeek-V4 test fixture)
A 122M-parameter model with the full DeepSeek-V4-Flash architecture and randomly initialized weights trained from scratch on a small synthetic corpus. It exists so that DeepSeek-V4 code paths can be exercised without the full model.
This is not a usable language model. It's four layers wide enough to be architecturally faithful and nothing more. It produces grammatical, confident, entirely wrong childlike statements, which is what it was trained to do:
Clouds are pillows waiting for a very tall bed.
I think pencils take recess home in a box. They feel like a pudding pencil.
For use as a fixture, not as a model.
Structure
Everything structural about DeepSeek-V4 is present at 1/500th the size:
| property | value | same as the real model |
|---|---|---|
| architecture | deepseek4 |
yes |
| layers | 4 | no (real: 43) |
| sliding window | 128 | yes |
| indexer top-k | 512 | yes |
| routed experts / used | 256 / 6 | yes |
| CSA / HCA compressed cache | present | yes |
| vocabulary | 129280 | yes |
| trained context | 1048576 | yes |
| hidden size | 128 | no (real: 4096) |
| parameters | 122.18 M | no |
It round-trips conversion, loading, MoE routing, the CSA/HCA compressed cache, the Lightning Indexer, sliding-window attention, long prefill, cache transitions and repeated generation. It loads in about a second and fits on any GPU, which makes it practical to put in a loop.
Files
| file | size | use |
|---|---|---|
ralphseek-v4-flash-f32.gguf |
494 MB | F32 reference; the arm to use for byte-exact A/B work |
ralphseek-v4-flash-q8_0.gguf |
142 MB | q8_0 target |
ralphseek-v4-flash-iq4_nl.gguf |
91 MB | quick smoke arm |
ralphseek-v4-flash-mtp-f32.gguf |
223 MB | MTP draft head, F32 (see below) |
ralphseek-v4-flash-mtp-q8_0.gguf |
63 MB | MTP draft head, q8_0 |
ralphseek-v4-flash-mtp-iq4_nl.gguf |
44 MB | MTP draft head, IQ4_NL |
hf/ |
489 MB | Transformers-format source, for testing convert_hf_to_gguf.py itself |
Usage
llama-cli -m ralphseek-v4-flash-f32.gguf -p "<|User|>Tell me a fact about clouds.<|Assistant|></think>" \
-n 64 --temp 0 --special
The DeepSeek-V4 chat template is required; a raw prompt hits an immediate EOS.
The MTP draft head
The -mtp- files are a standalone NextN head for this model. Together with a target file above they provide a complete DeepSeek-V4 MTP setup in 717 MB at F32, or 135 MB if you pair the IQ4_NL target with the IQ4_NL head, which makes the draft path testable without a real checkpoint.
Pass it as -md, never as -m. The head is 34 tensors: one block holding nextn.{enorm,hnorm,eh_proj,shared_head_norm} plus the shared embedding, output and norm. It has no layers of its own, so loading it as the main model crashes while building the graph. That failure looks alarming and means nothing.
llama-cli -m ralphseek-v4-flash-f32.gguf -md ralphseek-v4-flash-mtp-f32.gguf \
--spec-type mtp:n_max=1,p_min=0.0 -fa on \
-p "<|User|>Tell me a fact about clouds.<|Assistant|></think>" \
-n 64 --temp 0 --special
On a short greedy completion the head proposes on every step and lands 7 of 9 drafts. Every combination of target and head quantization tested (F32, q8_0 and IQ4_NL, mixed and matched) produced byte-identical output to the same run with no draft model, which is the property speculative decoding is supposed to have and a useful thing to be able to check quickly.
Acceptance on a 122M model trained on nonsense is not a prediction of acceptance on a real one. It's meant as a signal that the path is wired up, not as a benchmark.
Provenance and licensing
- Weights are original, trained from random initialization on a synthetic corpus. They are not derived from, distilled from, or a slice of any DeepSeek checkpoint. The hidden size alone (128 against 4096) makes that impossible.
- Tokenizer, tokenizer config, generation config and chat template are copied from deepseek-ai/DeepSeek-V4-Flash-0731, which is MIT licensed, so that prompts and special tokens behave identically to the real model. The chat template carries Unsloth's template fixes.
- Architecture follows the official Transformers
DeepseekV4ForCausalLMimplementation. - The MTP head is the
num_nextn_predict_layers = 1head trained alongside this model, repacked into themtp.0.tensor naming the converter looks for. The repack is a rename and a reorder with no numerical change; every tensor value is preserved exactly. - Not affiliated with or endorsed by DeepSeek.
The name is a joke about a small thing that says wrong facts with total confidence.
- Downloads last month
- 292
4-bit
8-bit
32-bit