Who it is forA researcher or evaluator who wants to check NeoHorse-1 numbers against the reported protocol before comparing it with other models.
The problemBenchmark scores change with sampling settings, so a comparison is only fair if the same settings are used.
The outcomeA local SGLang server that matches the reported protocol settings, ready for your own benchmark runs.
What you need first
- A machine with enough GPU memory for the 4B or 9B BF16 weights, or a quantized GGUF or MLX build for smaller hardware
- Python with pip available
- Disk space for the downloaded checkpoint from Hugging Face or ModelScope
Steps
- Run
pip install "sglang==0.5.17" - Set MODEL_PATH to the NeoHorse-1-9B directory, then run
python3 -m sglang.launch_server --model-path "$MODEL_PATH" --served-model-name neohorse-1-9B --host 0.0.0.0 --port 30000 --context-length 262144 --reasoning-parser qwen3 --tool-call-parser qwen3_coder(inferred, check the README) - Set the client to temperature=1.0, top_p=0.95, top_k=20, min_p=0.0, presence_penalty=1.5, repetition_penalty=1.0.
- Turn on thinking mode with enable_thinking=true and force_nonempty_content=true.
- Run your chosen benchmark tasks and record the runs, noting that the README uses three runs for some benchmarks and one run for others.
Prompt for your agent
In the TokenRhythm/NeoHorse repo, serve the NeoHorse-1-9B checkpoint at <model-directory> with SGLang v0.5.17 on port 30000 using the reported protocol settings in the Evaluation section. Send the benchmark prompt <benchmark-item> and return the answer and the settings used. Verify that the request sets temperature=1.0, top_p=0.95, and top_k=20 before recording any score.
Caveat. The README gives the sampling settings but not the benchmark datasets or scripts, so you must obtain the official protocols yourself to reproduce the reported scores.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page