sol-max-v2.h006.pi-agent-sft-v5.step_300

AgentPTB sweep checkpoint. Cell sol-max-v2 — Codex / gpt-5.6-sol @ effort max.

field	value
plot cell	sol-max-v2
driver	Codex / gpt-5.6-sol
reasoning effort	max
run boot (UTC)	2026-08-19T19:15:00Z
role	intermediate
hours into run	h6.39 of 100
checkpoint path in run	checkpoints/pi-agent-sft-v5/weights/step_300
shards	4
size	18.8 GB
base model	Qwen/Qwen3.5-9B-Base
eos_token_id	[248046] ✅ correct

Reading the eos field

248046 is <|im_end|>, the token the Qwen3.5 chat template ends every assistant turn with. Checkpoints missing it do not stop at end-of-turn and overrun the context window, so their eval numbers are a floor, not a measurement — compare them only against other checkpoints with the same eos status, or re-package before evaluating.

Cell note: redo of the sol@max cell from hour 0 on tb-1; ran the full 100 h. The arm submitted an h7 checkpoint over 75 h of later training.

Serving

Qwen/Qwen3.5-9B-Base is Qwen3_5ForConditionalGeneration — a vision architecture, and the vision tower is present in these weights. prime-rl does not export preprocessor_config.json, so vLLM must be told the model is text-only or it fails to load:

--limit-mm-per-prompt '{"image": 0, "video": 0}'

Mapping back to the figures

The repo id is {cell}.h{HHH}.{family}.{step}, where hHHH is the hour of the 100-hour run at which this checkpoint was written — the same x-axis the sweep figures use for eval panels (t_h). So a checkpoint drops onto the performance-over-time curve directly, and sorting repo ids within a cell sorts them chronologically.

hHHH is rounded down to whole hours for sortability; the exact value is the hours into run row above, and in agentic-ptb/INDEX.