InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kronos

InternVL3.5-GPT-OSS-20B-A4B-Preview

An image and video reader on gpt-oss-20b with an optional thinking mode, a preview untouched for over a year. It needs about 51 GB in BF16, since OpenGVLab publishes no quantised build, and runs in Transformers and vLLM. The main risk is a chat template in the Transformers-format repository that doesn't match its tokenizer, with no safety results.

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.

InternVL3.5-GPT-OSS-20B-A4B-Preview

1. Serve with vllm serve OpenGVLab/InternVL3_5-GPT-OSS-20B-A4B-Preview-HF --max-model-len 32768, which is our command; the card gives none for vLLM
2. Check the rendered prompt before relying on it, since the shipped template's <|im_start|> markers aren't tokens in the gpt-oss tokenizer; the GitHub-format repository's harmony template is the alternative
3. Use Transformers 4.55.0 or later, as the card requires for this size
4. For thinking, send the card's thinking system prompt and parse the reasoning out of the <think> tags, with temperature 0.6 and sampling on as the card advises
5. Keep inputs within 32K tokens, the length it was trained at, whatever the config says

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