Instructions to use TheBloke/deepseek-coder-1.3b-base-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use TheBloke/deepseek-coder-1.3b-base-GGUF with Transformers:
# Load model directly from transformers import AutoModel model = AutoModel.from_pretrained("TheBloke/deepseek-coder-1.3b-base-GGUF", device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M
Use Docker
docker model run hf.co/TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M
- LM Studio
- Jan
- Ollama
How to use TheBloke/deepseek-coder-1.3b-base-GGUF with Ollama:
ollama run hf.co/TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M
- Unsloth Studio
How to use TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-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 TheBloke/deepseek-coder-1.3b-base-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for TheBloke/deepseek-coder-1.3b-base-GGUF to start chatting
- Atomic Chat new
- Docker Model Runner
How to use TheBloke/deepseek-coder-1.3b-base-GGUF with Docker Model Runner:
docker model run hf.co/TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M
- Lemonade
How to use TheBloke/deepseek-coder-1.3b-base-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull TheBloke/deepseek-coder-1.3b-base-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.deepseek-coder-1.3b-base-GGUF-Q4_K_M
List all available models
lemonade list
Tokenisation for fill in the middle prompts broken
Hi there, thanks a lot for building all these GGUFs for us!
Not sure if this is the right place to ask this, but the GGUF version of this model doesn't seem to tokenise and detokenise the special strings for fill in the middle correctly. Looking at the original model's tokenizer.json, I can see this
{
"id": 32015,
"content": "<|fim▁hole|>",
"single_word": false,
"lstrip": false,
"rstrip": false,
"normalized": true,
"special": false
},
{
"id": 32016,
"content": "<|fim▁begin|>",
"single_word": false,
"lstrip": false,
"rstrip": false,
"normalized": true,
"special": false
},
{
"id": 32017,
"content": "<|fim▁end|>",
"single_word": false,
"lstrip": false,
"rstrip": false,
"normalized": true,
"special": false
}
But loading any of the GGUFs from this repo into llama.cpp's server example and hitting the /detokenize endpoint results in "unordered_map::at: key not found" and hitting /tokenize gives me the wrong tokens
Is there some way to look at the tokenizer configuration within the GGUF? Could quantisation somehow lead to this?