Hi, thanks for the great work. I'm trying to reproduce your reported baseline numbers with the qwen backend and want to confirm the exact eval protocol before I blame my setup.
Reading through engine/trainer.py, I see that the baseline is a single call:
engine/trainer.py:1001-1002
baseline_dir = os.path.join(out_root, "selection_eval_baseline")
baseline_results = adapter.rollout(sel_env, skill_init, baseline_dir)
And for livemathematicianbench, configs/livemathematicianbench/default.yaml sets max_turns: 1, so each item gets a single LLM call. qwen_backend.py also defaults to temperature=0.7, so per-run stochasticity is non-trivial.
A few questions:
- Are the baseline numbers you report from a single seed / single run, or aggregated across N runs?
- If aggregated, is it mean, median, or best-of-N?
- Is there any code path (that I might have missed) where a skill is rolled out multiple times and the max/mean is taken?
Thanks!
Hi, thanks for the great work. I'm trying to reproduce your reported baseline numbers with the qwen backend and want to confirm the exact eval protocol before I blame my setup.
Reading through engine/trainer.py, I see that the baseline is a single call:
engine/trainer.py:1001-1002
baseline_dir = os.path.join(out_root, "selection_eval_baseline")
baseline_results = adapter.rollout(sel_env, skill_init, baseline_dir)
And for livemathematicianbench, configs/livemathematicianbench/default.yaml sets max_turns: 1, so each item gets a single LLM call. qwen_backend.py also defaults to temperature=0.7, so per-run stochasticity is non-trivial.
A few questions:
Thanks!