Instructions to use TheBloke/deepseek-coder-33B-instruct-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.

Libraries

How to use TheBloke/deepseek-coder-33B-instruct-GGUF with Transformers:

# Load model directly
from transformers import AutoModel
model = AutoModel.from_pretrained("TheBloke/deepseek-coder-33B-instruct-GGUF", device_map="auto")

Notebooks
Google Colab
Kaggle
Local Apps Settings

llama.cpp

How to use TheBloke/deepseek-coder-33B-instruct-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-33B-instruct-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf TheBloke/deepseek-coder-33B-instruct-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-33B-instruct-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf TheBloke/deepseek-coder-33B-instruct-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-33B-instruct-GGUF:Q4_K_M
# Run inference directly in the terminal:
./llama-cli -hf TheBloke/deepseek-coder-33B-instruct-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-33B-instruct-GGUF:Q4_K_M
# Run inference directly in the terminal:
./build/bin/llama-cli -hf TheBloke/deepseek-coder-33B-instruct-GGUF:Q4_K_M

Use Docker

docker model run hf.co/TheBloke/deepseek-coder-33B-instruct-GGUF:Q4_K_M

LM Studio
Jan
Ollama
How to use TheBloke/deepseek-coder-33B-instruct-GGUF with Ollama:
```
ollama run hf.co/TheBloke/deepseek-coder-33B-instruct-GGUF:Q4_K_M
```
Unsloth Desktop
Docker Model Runner
How to use TheBloke/deepseek-coder-33B-instruct-GGUF with Docker Model Runner:
```
docker model run hf.co/TheBloke/deepseek-coder-33B-instruct-GGUF:Q4_K_M
```

Lemonade

How to use TheBloke/deepseek-coder-33B-instruct-GGUF with Lemonade:

Pull the model

# Download Lemonade from https://lemonade-server.ai/
lemonade pull TheBloke/deepseek-coder-33B-instruct-GGUF:Q4_K_M

Run and chat with the model

lemonade run user.deepseek-coder-33B-instruct-GGUF-Q4_K_M

List all available models

lemonade list

Atomic Chat

Weird tokens

by dranger003 - opened Nov 5, 2023

Discussion

dranger003

Nov 5, 2023

Thanks for converting this model! Although I see some weird tokens when running llama.cpp (compiled from master).

llm_load_print_meta: general.name   = deepseek-ai_deepseek-coder-33b-instruct
llm_load_print_meta: BOS token = 32013 '<∩╜£beginΓûüofΓûüsentence∩╜£>'
llm_load_print_meta: EOS token = 32014 '<∩╜£endΓûüofΓûüsentence∩╜£>'
llm_load_print_meta: PAD token = 32014 '<∩╜£endΓûüofΓûüsentence∩╜£>'
llm_load_print_meta: LF token  = 30 '?'

TheBloke

Owner Nov 5, 2023

Yeah it is weird, but that's exactly what's defined in tokenizer_config.json:

 [pytorch2] tomj@MC:/workspace/git/gguf-llama (master ✘)✭ ᐅ grep -A5 -i eos /workspace/process/deepseek-ai_deepseek-coder-33b-instruct/source/tokenizer_config.json | cat -
ve
  "add_eos_token": false,$
  "bos_token": {$
    "__type": "AddedToken",$
    "content": "<M-oM-=M-^\beginM-bM-^VM-^AofM-bM-^VM-^AsentenceM-oM-=M-^\>",$
    "lstrip": false,$
    "normalized": true,$
--$
  "eos_token": {$
    "__type": "AddedToken",$
    "content": "<M-oM-=M-^\endM-bM-^VM-^AofM-bM-^VM-^AsentenceM-oM-=M-^\>",$
    "lstrip": false,$
    "normalized": true,$
    "rstrip": false,$

I don't know why they've used those weird chars, but this isn't a llama.cpp issue; it's using the tokens as defined by the original model.

FYI I'm just about to re-make all the GGUFs after an update to the convert.py I'm using, which affects special tokens. It won't change this, but might affect other aspects of special token usage.

JorritJ

Nov 6, 2023

That weird combination of characters is probably to reduce the odds of them being present in random input.

The output being garbled on dranger003's run is just a console character set issue.

Upload images, audio, and videos by dragging in the text input, pasting, or clicking here.

Tap or paste here to upload images

· Sign up or log in to comment