microsoft / microsoft/SkillOpt

How is the baseline evaluation score aggregated across runs? (single-seed vs multi-seed / best-of-N)

Open
#108 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
17.3k
Forks
1.6k
Avg merge
2d 7h
Merged PRs (30d)
17

Description

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:

  1. Are the baseline numbers you report from a single seed / single run, or aggregated across N runs?
  2. If aggregated, is it mean, median, or best-of-N?
  3. 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!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read engine/trainer.py around lines 1001-1002, configs/livemathematicianbench/default.yaml, and qwen_backend.py. Trace the baseline rollout path and check whether repeated runs or aggregation are implemented. Done means documenting whether the reported baseline uses one run or multiple runs and, if applicable, which aggregation method is used.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning, testing-qa
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.