Instructions to use KRAFTON/Raon-1-mini-preview with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use KRAFTON/Raon-1-mini-preview with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="KRAFTON/Raon-1-mini-preview", trust_remote_code=True) messages = [ {"role": "user", "content": "Who are you?"}, ] pipe(messages)# pip install -U transformers accelerate # Load model directly from transformers import AutoModelForCausalLM model = AutoModelForCausalLM.from_pretrained("KRAFTON/Raon-1-mini-preview", trust_remote_code=True, device_map="auto") - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use KRAFTON/Raon-1-mini-preview with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "KRAFTON/Raon-1-mini-preview" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "KRAFTON/Raon-1-mini-preview", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/KRAFTON/Raon-1-mini-preview
- SGLang
How to use KRAFTON/Raon-1-mini-preview with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "KRAFTON/Raon-1-mini-preview" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "KRAFTON/Raon-1-mini-preview", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "KRAFTON/Raon-1-mini-preview" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "KRAFTON/Raon-1-mini-preview", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use KRAFTON/Raon-1-mini-preview with Docker Model Runner:
docker model run hf.co/KRAFTON/Raon-1-mini-preview
RDA vs Gated DeltaNet 2
The description of RDA and GDN 2 by Nvidia sound very similar. What is the difference? Do you parameterise it differently?
Thanks for the question! RDA and GDN-2 are closely related: both decouple the erase and write strengths that KDA ties to a single gate . The difference is granularity.
- GDN-2 makes both gates channel-wise: an erase gate on the key and a write gate on the value.
- RDA keeps both gates as per-head scalars, , so erase and write are learned independently with almost no extra parameters. It starts exactly as KDA at initialization and learns to separate the two during training.
More precisely, the three state updates are:
All three share KDA's channel-wise decay . RDA reduces to KDA when .
In our 1.3B ablations under the GDN-2 paper setup (recurrent-only models), RDA showed better long-context retrieval (NIAH) than both KDA and GDN-2.
| Variant | Decay | Erase term | Write term | Key innovation |
|---|---|---|---|---|
| GDN | scalar alpha_t | scalar beta_t | scalar beta_t | Baseline: adaptive forgetting + tied delta edit |
| KDA | vector alpha_t | scalar beta_t | scalar beta_t | Channel-wise forgetting; finer decay granularity |
| RDA | vector alpha_t | scalar e_t | scalar w_t | Decoupled scalar erase/write; conceptual intermediate |
| GDN-2 | vector alpha_t | vector b_t | vector w_t | Full decoupling: channel-wise erase on key side and write on value side |
Is this right?
Thanks for the nice summary!
Yes, that's right. In terms of gate granularity, RDA sits between KDA and GDN-2: it decouples erase from write like GDN-2, but keeps per-head scalar gates like KDA.
Ah ok that makes sense. Thank you very much. Althoug i find the better performance in ablations quite surprising, considering, at least intuitively, that a more fine grained edit should allow the model to better control the information in its state. Will there be a detailed tech report (including ablations)?
Thanks! We were also surprised at first. As a simple ablation, we tried to reproduce the MQAR experiment from the Kimi Linear paper under a fair setting for RDA, KDA and GDN-2. The code for that experiment was not released, so we wrote our own codebase and swept the same five learning rates for all three models. In our runs at L=2048 with 32 KV pairs, RDA reached ~97% accuracy while GDN-2 reached ~25% and KDA stayed near 0% at every learning rate. This does not match the trend in the Kimi Linear paper, especially for KDA, possibly because the original setup is not fully specified.
Like GDN-2, we think decoupling erase and write is the key idea. But in our experiments the granularity of KDA was already enough.
Yes, we also plan to release a technical report.