Views
No views yet
groxaxo.
It is intended for open-source evaluation, reproducible experimentation, and compatible local or
hosted inference workflows. The wording below is deliberately limited to what can be verified
from this repository's metadata and artifacts.| Field | Details |
|---|---|
| Format | Transformers |
| Source / base | WarlordHermes/Magidonia-24B-v4.3-creative-ORPO |
| Intended task | text-generation |
| License | apache-2.0 |
*.safetensors (10 files)config.jsongeneration_config.jsontokenizer.jsontokenizer_config.jsonchat_template.jinjaWarlordHermes/Magidonia-24B-v4.3-creative-ORPO
sat quietly — a solid creative writer, but a little too polite to touch a terminal.
Over five curriculum phases of QLoRA (rank 64, rslora, target-all-linear), he was put
through school one subject at a time:_v2 passes when the mask logic didn't add up.hermes-agent-reasoning-traces)
plus a small hand-reviewed architecture-QA supplement distilled from Claude
Opus 4.6 reasoning traces — this is where he learned to actually call things
instead of just describing them.p5-deepseek adapter was then
merged straight into the base weights in full bf16 (no quantization, no
rounding shortcuts) to produce this checkpoint: a clean, full-precision snapshot
of everything he learned, suitable as the master copy for every downstream
quantization (GGUF, GPTQ, AWQ, ...) that follows.MistralForCausalLM), 40 layers, hidden 5120, 32 heads / 8 KV heads (GQA), rope_theta 1e9| Task | Score |
|---|---|
| MMLU (overall) | 0.7433 |
| MMLU-STEM | 0.7172 |
| MMLU-Humanities | 0.6486 |
| MMLU-Social Sciences | 0.8400 |
| MMLU-Other | 0.8169 |
| PIQA | acc 0.8022 / acc_norm 0.8413 |
WarlordHermes/Magidonia-24B-v4.3-creative-ORPO
└─ magidonia_curric_p1 / p1_v2
└─ magidonia_curric_p2 / p2_v2
└─ magidonia_curric_p3 / p3_v2 (frozen)
└─ magidonia_curric_p4_agentic_v1 / v2 (frozen)
└─ magidonia_curric_p5_deepseek_v1 <-- merged here, bf16chat_template.jinja matches the model's Hermes-style <tool_call> JSON.
Use the Hermes parser so OpenAI clients receive structured tool_calls rather than raw
tool-call text:1vllm serve groxaxo/MagiSeek-Pro-V1 \
2 --dtype bfloat16 \
3 --tensor-parallel-size 3 \
4 --max-model-len 131072 \
5 --chat-template chat_template.jinja \
6 --enable-auto-tool-choice \
7 --tool-call-parser hermes \
8 --host 0.0.0.0 --port 80001Base URL: http://HOST:8000/v1
2Model: groxaxo/MagiSeek-Pro-V10.6–0.7 rather than 0.0.1import torch
2from transformers import AutoModelForCausalLM, AutoTokenizer
3
4model_id = "groxaxo/MagiSeek-Pro-V1"
5tokenizer = AutoTokenizer.from_pretrained(model_id)
6model = AutoModelForCausalLM.from_pretrained(
7 model_id,
8 torch_dtype=torch.bfloat16,
9 device_map="auto",
10)
11
12messages = [{"role": "user", "content": "Explain what you can do."}]
13inputs = tokenizer.apply_chat_template(
14 messages,
15 add_generation_prompt=True,
16 return_tensors="pt",
17).to(model.device)
18output = model.generate(inputs, max_new_tokens=512, temperature=0.7, do_sample=True)
19print(tokenizer.decode(output[0][inputs.shape[-1]:], skip_special_tokens=True))<tool_call>{...}</tool_call> output
or use an OpenAI-compatible serving layer such as vLLM for automatic structured tool-call
responses. Reasoning and tool calls should not be displayed as ordinary user-facing text.chat_template.jinja — the model-native Hermes tool-use template for this full-weight
checkpoint. It is intended for Transformers-compatible serving and vLLM; use the vLLM
hermes tool parser for OpenCode.