specific method · filed under evaluation
Four-run mean pass@1
Running each agentic benchmark four times and averaging pass@1 to mitigate infrastructure noise.
Also called Mean pass@1 across four runs.
- source
- 1
- model
- 1
- lab adopt it
- 1
- strongest
- used
How sources treat it
One count per evidence span, weakest treatment to strongest.
used 1
Documented in
Evidence
1 span quoted from the sources, strongest treatment first.
To address this, we run each benchmark four times and report the mean pass@1 across the four runs.
usedevaluation onlyin LAGUNA M.1/XS.2Poolside
Filed alongside
Other methods under evaluation.
Prompt-based output standardizationEvaluation without safety filtersRefusal-suppressed variants for capability estimationavg@kAlmost@1Behavior testing with stubs and edge casesDeadline-bounded rollout evaluationDiverse benchmark validation for quantizationDocumenting evaluation configurationEnd-to-end exploit development evaluationEvaluation equivalence thresholdFixed MTP draft-token acceptance lengthFull trajectory releaseJoint validation protocolMean@5Model–harness co-designOfficial-release-source baseline restrictionPrompt engineering to elicit answersProtocolQA robustness validationRefusal behavior quantificationRollout-based auditingSample test and length-constraint filteringSandboxed GPU kernel optimization evaluationSingle-agent and multi-agent evaluation configurations