6.5.3 · D2Research Frontiers & Practice

Visual walkthrough — Benchmark design and evaluation rigor

3,640 words17 min readBack to topic

This page rebuilds the parent result — Benchmark design and evaluation rigor — from the ground up, entirely in pictures. The central claim we are chasing:

When a paper says "Model A scores 92.3%", that single number is one draw from a cloud of possible scores. Rigor is the art of measuring that cloud, not the dot inside it.

We build every symbol from zero. A smart 12-year-old who has never seen a mean, a square root, or the letter can follow from line one.


Step 1 — A score is a dart throw, not a fixed point

WHAT. Suppose you train the same model design five times. You change nothing you care about — same data, same architecture. But each run uses a fresh random seed: the coin-flips that set the starting weights, the order the data is shuffled in, which neurons dropout switches off. Result: five different accuracy numbers, e.g. .

WHY. If one training run could land anywhere in a spread, then reporting a single run is like throwing one dart and calling that spot "the bullseye." We need to see the whole dartboard first.

PICTURE. Each run is a dot on the accuracy axis. They scatter. There is no single true score you can observe — only samples of it.

Figure — Benchmark design and evaluation rigor

Step 2 — The mean: where the cloud sits

WHAT. Add all the dots up and divide by how many there are. That balance point is the sample mean, written (read "P-bar" — the bar means "averaged").

  • = how many runs (here ).
  • is shorthand for "." The tall (Greek capital sigma, chosen because it starts the word sum) just says add these up, sweeping from to .
  • Multiplying the total by = dividing by = fair-sharing the total equally.

WHY. We want one representative number, but chosen honestly — the centre of the cloud, not the luckiest dot on its edge. Picking the best run instead is selection bias: you'd be reading the right-hand tail and calling it typical.

PICTURE. The mean is the fulcrum where the see-saw of dots balances.

Figure — Benchmark design and evaluation rigor

Step 3 — The spread: how wide is the cloud?

WHAT. Knowing the centre is not enough — a cloud can be a tight pinprick or a wide smear. We measure the width with the sample standard deviation .

Read it inside-out:

  • = how far run landed from the centre (a signed gap, left or right).
  • = square it. Why square? To make every gap positive (so left and right gaps don't cancel), and to punish far-away dots more than near ones.
  • = add all those squared gaps.
  • = average them. We divide by , not , because was itself estimated from the same dots — that "steals" one degree of freedom, so we compensate. This is the honesty tax.
  • = square-root at the end, to undo the squaring and return to the original units (percent, not percent-squared).

WHY. Two models can share the same average and be wildly different: one reliable, one a coin-flip. is the number that separates them.

PICTURE. Two clouds, same fulcrum, different width — the tight one is trustworthy, the wide one is a gamble.

Figure — Benchmark design and evaluation rigor

Step 4 — Where is the true centre? The standard error

WHAT. is our guess for the model's true average capability. But is itself a random thing — run five more times and you'd get a slightly different . How jittery is the guess? That jitter is the standard error of the mean:

  • = width of the raw cloud (Step 3).
  • in the denominator = the payoff for doing more runs. More runs → averages steady out → the guess jitters less.

WHY this and not ? Because errors partly cancel when you average, but only in a square-root way — random pushes left and right don't fully undo each other. The consequence, drawn below: to halve your uncertainty you need four times as many runs (). Cheap precision does not exist.

PICTURE. The cloud of individual runs (wide, ) versus the tighter cloud of the mean itself (narrow, SEM), shrinking as grows.

Figure — Benchmark design and evaluation rigor

Step 5 — Draw the honest claim: the confidence interval

WHAT. Instead of a dot, report a bar around that plausibly contains the true centre. For runs:

  • = "plus and minus" — the bar reaches equally left and right.
  • = the magic width that captures the central of a bell-shaped cloud. (Change it and you change your confidence level.)

For small (our case, ), the cloud has fatter tails, so is too optimistic. We swap in a bigger number from Student's t-distribution with degrees of freedom (df).

For (so df ), — noticeably wider than , exactly because five dots tell you less than thirty.

WHY. This bar is the honest deliverable. "The true score lies in with 95% confidence" is a claim that survives someone else re-running you.

PICTURE. The point estimate becomes a whiskered bar; the fewer the runs, the longer the whiskers.

Figure — Benchmark design and evaluation rigor

Step 6 — Comparing two models: do the clouds overlap?

WHAT. To ask "is A really better than B?", overlay their two clouds and measure the gap between centres in units of the combined jitter. That ratio is the t-statistic:

Before reading the formula, meet its symbols — each is just a Step-2/Step-3 quantity computed separately for each model:

Now the formula reads plainly:

  • Numerator = how far apart the two means sit (the effect you're excited about).
  • Denominator = how much both means jitter, added in quadrature (squares add, then square-root — the same "errors combine in a square-root way" rule from Step 4). Each model contributes its own SEM-squared, and .
  • Big → gap dwarfs the jitter → real difference. Small → the clouds smear into each other → could be pure luck.

This t-statistic is compared against the same Student-t distribution from Step 5, so it too leans on the near-normality of the two clouds — safe-ish by the CLT when each has enough independent runs, shakier for very small or very skewed samples.

How many degrees of freedom? With two samples of possibly different spreads we can't just write . Welch's method uses the Welch–Satterthwaite approximation:

  • The top squares the total noise term; the bottom shares the blame between the two samples, each penalised by its own df.
  • Why bother? Because Model A might be far more seed-sensitive than Model B (unequal variances). Welch does not assume equal spreads, so it stays honest. For our example numbers this formula yields .

WHY. Eyeballing "92.3 vs 91.8, so A wins" ignores the width. The t-statistic forces you to divide the signal by the noise before believing anything.

PICTURE. Two overlapping bell clouds; is literally "how many noise-widths separate their peaks."

Figure — Benchmark design and evaluation rigor

Step 7 — The degenerate cases (never leave the reader stranded)

WHAT & WHY. Every formula above breaks somewhere. Here is the full atlas of edge cases, each with what happens and what to do.

Situation What breaks What it means / the fix
(single run) needs in the denominator → undefined You have zero spread information. No CI, no comparison possible. This is exactly Paper A's sin.
defined but — a huge whisker The bar is so wide it's almost useless. Two runs barely constrain anything.
(all runs identical) , denominator vanishes Suspicious! Usually means the seed was not actually varied — a reproducibility bug, not perfect stability.
non-Normal scores and both lose their meaning Heavy tails or a ceiling near 100% break the bell assumption — use bootstrap resampling instead.
Testing model pairs many chances to get a fluke Use Bonferroni (explained just below the table): demand . 20 models → 190 pairs → naive threshold yields false wins by chance.
Tiny but "significant" gap huge shrinks the SEM until any nonzero gap crosses Significance is not the same as importance. A improvement can be "significant" yet useless in practice. Report Cohen's (below) to judge whether the gap is big relative to the noise, not just detectable.

Bonferroni correction — worked out. Suppose you compare models against each other. The number of distinct pairs is

Reading the formula: ("20 choose 2") counts how many ways to pick models out of to pit against each other; it equals because there are choices for the first and for the second, then divide by so that "A vs B" and "B vs A" aren't double-counted.

If each test uses the naive threshold , then by chance alone you expect

Bonferroni's fix: shrink each test's threshold to . Now a comparison must clear a far higher bar before you believe it, and the whole family's false-alarm rate stays under . The figure below shows the lottery: 190 random p-values, the greedy line at catching flukes, the strict Bonferroni line at letting almost none through.

Cohen's rescales the gap by the pooled spread, so it answers "is the difference big relative to the noise?", independent of how many runs you ran:

  • = one combined width, blending both samples' spreads. Each sample is weighted by its own degrees of freedom and , and the whole thing is normalised by the total df , then square-rooted back into original units.
  • Reading : negligible, small, medium, large.

PICTURE. The failure gallery: the point with no whisker, the collapsed spike, and the Bonferroni "lottery of false positives."

Figure — Benchmark design and evaluation rigor

The one-picture summary

Everything above is one story: turn a dot into a cloud, measure the cloud's centre and width, shrink the uncertainty with more runs, then compare clouds — not dots.

Figure — Benchmark design and evaluation rigor

one run gives one score

many seeds give a cloud

mean P-bar is the centre

std dev s is the width

SEM equals s over root n

confidence interval bar

compare clouds with t

correct for many tests

report d for real-world size

Recall Feynman retelling — say it to a friend

Imagine you throw a dart at a scoreboard. It lands at 92. Does the dart-thrower always hit 92? No — throw again, you get 91, then 93. So one dart tells you almost nothing. First, throw many darts (many random seeds). Now you have a little cloud of holes. Where is the cloud? Find its balance point — that's the mean, . Don't brag about your single best hole; that's cheating. How wide is the cloud? Measure how far the holes typically sit from the centre — that's the standard deviation . A tight cloud is a reliable thrower; a wide one is a gambler. How sure are you about the centre? Even the balance point wobbles if you re-throw the whole set. But it wobbles less than the raw holes, and shrinks like one-over-root-of-how-many-throws. Four times the darts, half the wobble. That shrunk wobble is the SEM, and it sets the length of your error bar — but only if the cloud is bell-shaped, which the Central Limit Theorem grants you once you have enough independent throws. Is your model better than mine? Put both clouds side by side. If they smear into each other, the "win" is just luck — that's what a small means. If both models faced the same seeds, pair them up so the shared bad-luck cancels. And if you compare lots of models, remember someone always wins the lottery by chance, so raise the bar (Bonferroni). Finally, even a real gap might be too tiny to care about — that's what Cohen's checks. That's the whole of evaluation rigor: measure the cloud, not the dot.


Recall

What does the "-1" in pay for? ::: The honesty tax for having estimated from the same data — it corrects the systematic under-estimate of spread. Why divide by and not in the SEM? ::: Random errors only partially cancel when averaged, in a square-root way — so precision improves like . Why is the subscript (not ) on the t-quantile for a 95% CI? ::: A 95% interval leaves 5% outside split into two 2.5% tails, so the right edge sits at 97.5%. What assumption lets us use or the t-quantile at all? ::: That the cloud of means is (near-)Normal — granted by the Central Limit Theorem for enough independent runs; otherwise use bootstrap. When should you use a paired t-test instead of Welch's? ::: When both models were evaluated on the same seeds, so runs are matched and shared noise cancels; df becomes (pairs − 1). Paper A "92.3" vs Paper B "" — is A better? ::: No — 92.3 lies inside B's confidence interval, so the gap is consistent with noise. When is undefined and why? ::: At , since ; a single run carries zero spread information. How many pairwise comparisons among 20 models, and how many false wins at ? ::: 190 comparisons; about false wins — hence Bonferroni's threshold. Statistical vs practical significance? ::: A big enough makes any gap "significant"; Cohen's tells you if the gap is actually large relative to the noise.

See also: Evaluation metrics · Regularization techniques · Bias–variance tradeoff · Interpretability and AI safety · Emerging architectures