6.5.3 · D3Research Frontiers & Practice

Worked examples — Benchmark design and evaluation rigor

2,515 words11 min readBack to topic

This page is the "every case" companion to the parent topic. In statistics you can be fooled in many different ways, and each way needs its own worked drill. Below we first build a scenario matrix — a grid of every situation the topic can throw at you — then work through examples that together fill every cell.

Before we touch a single formula, three words, defined in plain English, anchored to a picture.

Figure — Benchmark design and evaluation rigor

Look at figure s01: two clouds of dots (two models). The red bracket is the SEM — the fuzziness of each average. If the red brackets overlap a lot, you cannot honestly say one model beat the other.


The scenario matrix

Every cell below is a class of situation. The worked examples that follow are tagged with the cell they cover, and by the end every cell is filled.

# Cell (situation class) What makes it tricky Covered by
C1 Overlapping intervals — small gap, small Gap looks real, noise is bigger Ex 1
C2 Non-overlapping / clearly separated Real effect — but is it big? Ex 2
C3 Zero / degenerate input (, or ) Formulas divide by zero or Ex 3
C4 Limiting behaviour Tiny gap becomes "significant" Ex 4
C5 Many comparisons — false positives by chance 20 tests, one "wins" by luck Ex 5
C6 Negative control fails — leakage / shortcut High score, wrong reason Ex 6
C7 Real-world word problem — deployment decision Statistical ≠ practical significance Ex 7
C8 Exam twist — sign of , one- vs two-sided Direction of the claim matters Ex 8

Prerequisite links: this all rests on bias–variance intuition and the definitions in evaluation metrics.


The one formula engine

Everything uses the same machine. We name each part before using it.


Worked examples


Recall Self-test

Why divide the gap by the noise instead of just reporting the gap? ::: Because a raw gap is unitless-meaningless — "is 5 big?" only has an answer relative to the noise. The ratio makes it scale-free. With , why can't you compute SEM? ::: needs in its denominator; one point has no measurable spread, so uncertainty is unknown, not zero. A gap becomes "significant" at large — good or bad? ::: Neither — significance only means "nonzero." Check Cohen's ; here is negligible. 20 models, all pairwise, — expected false wins? ::: .

Related frontier reading: emerging architectures keep breaking old benchmarks — the exact reason rigor matters.