DrugDiscoveryBench

What it measures

82 expert-curated computational drug discovery tasks executed by coding agents.

Reading the measurement

Ask whether the evaluation rewards recalling a fact, constructing a model, running an experiment or supporting a discovery. Those tasks require different evidence. For research claims, inspect reproducibility, uncertainty and what was actually checked.

Published evaluation

The linked publication documents the task and scoring procedure. Model results retain the source’s evaluation setting, native score units and available uncertainty.

Where this fits in an evaluation suite

A correct multiple-choice answer and a supported scientific contribution demand different evidence. Check whether the score rewards a proposal, an executed experiment, or a completed research target.

Start with a capability hypothesis, then choose a second test with a different failure mode. Keep the checkpoint, reasoning effort, agent tools, sampling policy, and scoring procedure fixed when measuring a training intervention. Record failures and missing outputs in the denominator.

A reproducible comparison

Record the source publication, benchmark version, scoring units, denominator, tool access and attempt budget. Preserve uncertainty and distinguish developer-reported results from independent evaluations.

Publish the exact run configuration, item coverage, score units, and available uncertainty. If a source supplies only an aggregate or a single run, preserve that limit. A new model name or a rounded score alone does not establish a capability improvement.