OverviewReproduce a result

Reproduce a result

Build a full local run plan with every test, recipe and missing setting kept explicit.

1. Choose the model and tests

1tests in this plan
1verified public harness
0need access or recipe work

Blocked tests stay in the plan. Public code alone does not reproduce an evaluator’s score.

2. Review the plan

GPQA DiamondPublic harness

Maintainer instructions checked 24 October 2026. Use the Diamond task, not a different GPQA subset. Confirm the task ID with lm-eval ls tasks and pin the dataset and harness. The public harness is not the Vals or AA pipeline. Inference, judging or local compute may incur costs; configure provider limits first.

Pinned dataset: Idavidrein/gpqa ↗ @ 83022cefff93 · gpqa_diamond · Benchmark author · Gated

  1. Read the linked maintainer guide and pin the harness commit.
  2. Configure the exact model adapter, dataset revision, split and task limit.
  3. Match prompts, tools, sampling, repetitions and judge to the intended run.
  4. Run generation and scoring stages; retain raw outputs, task outcomes and logs.
lm-eval run --model <backend> --model_args <provider-configuration> --tasks <verified-gpqa-diamond-task> --output_path results --log_samples
Author / evaluator instructions ↗

1 source-specific reference results for this model; each remains in the downloaded plan.

Configuration still required

  • Immutable model or endpoint version
  • Adapter verification against the pinned dataset
  • Harness commit
  • Prompt and tool policy
  • Reasoning effort
  • Sampling and seed
  • Task limit and repetitions
  • Judge and aggregation
  • Provider spending limits
  • Dataset access approval for the running account

The dataset revision and split are pinned in this job. Model version, harness, prompts, tools, judge and sampling remain unmatched, so a fresh run is not an exact reproduction claim.

Understand this test →