Kronos vs MiMo-V2.6 Distill Qwen 9B

Kronos

Forecasts the next price bars from a history of up to 512 candlestick bars. Every size fits in under 0.5 GB and runs on a CPU, but only through the publisher's own Python package. Nobody has benchmarked it independently, its quickstart data was deleted from the repository, and the publisher hasn't replied since November 2025.

MiMo-V2.6 Distill Qwen 9B

A 9B cousin tuned on MiMo-V2.6's agent work for coding, terminal tasks and visual coding, released as a base for RL research. It needs about 23 GB in BF16, since Xiaomi ships no smaller build. The main risks are no safety results while a seventh of its tuning is offensive security, and nobody at Xiaomi answering reports.

Kronos

1. Clone https://github.com/shiyu-coder/Kronos and pip install -r requirements.txt, then load Kronos.from_pretrained("NeoQuasar/Kronos-small") and KronosTokenizer.from_pretrained("NeoQuasar/Kronos-Tokenizer-base") and wrap them in KronosPredictor
2. Pair Kronos-mini with Kronos-Tokenizer-2k and Kronos-small or Kronos-base with Kronos-Tokenizer-base, the cards' pairing
3. The examples read examples/data/XSHG_5min_600977.csv, which no longer exists; point them at tests/data/regression_input.csv, 2,500 five-minute bars
4. Keep the lookback at or under max_context, 512 bars, and pass the future timestamps you want as y_timestamp, since the calendar fields come from them
5. Raise sample_count for a steadier forecast, but expect only the mean back; call the lower-level auto_regressive_inference yourself if you need the paths
6. Treat forecasts as model output to check, not signals; the README says its own backtest pipeline isn't a production trading system

MiMo-V2.6 Distill Qwen 9B

1. Serve it as the card does, sglang serve --model-path XiaomiMiMo/MiMo-V2.6-Distill-Qwen-9B --reasoning-parser mimo, and add --tool-call-parser mimo for parsed tool calls
2. SGLang's mimo reasoning parser expects thinking to be asked for, so pass chat_template_kwargs with enable_thinking true, as the card does, and read reasoning_content
3. Calls come back as function and parameter blocks inside tool_call, the same shape vLLM's and SGLang's qwen3_coder parsers read
4. The generation config samples at temperature 0.6, top_k 20 and top_p 0.95
5. Images and video go in through Qwen3.5's processor; the template's audio tokens have no audio encoder behind them
6. The MTP head isn't in the files, so skip MTP speculative decoding even though config.json lists a layer
7. It's an SFT checkpoint meant for further RL, and discussions report runaway generation on llama.cpp, so cap max_tokens