Family-Wise Error Rate
The chance of getting at least one false positive somewhere across a whole batch of hypothesis tests — a number that climbs toward certainty as the batch grows, even when the per-test false-alarm rate looks perfectly safe.
Prerequisites: Type I and Type II Errors, p-values and Multiple Testing
A single hypothesis test run at the standard 5% significance level has a 5% chance of crying wolf when nothing is really there. That sounds tolerably safe — until you run twenty of them. Run twenty independent tests, each individually safe at 5%, and the chance that at least one cries wolf is no longer 5%; it is close to two in three. The family-wise error rate is the name for that combined, batch-level chance of a false alarm, and it is the number that actually matters whenever you test more than one thing.
An analogy: buying many lottery tickets, each with long odds
A single lottery ticket has a tiny chance of "winning" (matching numbers by pure chance, meaning nothing). Buy one ticket, and the chance of an accidental match is genuinely small. Buy a thousand tickets, though, and even though each individual ticket's odds are unchanged, the chance that at least one of the thousand matches by pure luck climbs dramatically. Nobody would call that thousand-ticket match "a real signal" — it is exactly what you'd expect from buying that many tickets. Testing a thousand trading signals against history and reporting the one that happened to look significant is the same lottery, dressed up in -values.
The formula, one symbol at a time
Let be the significance level for one test — the chance of a false positive on that test alone, commonly . Suppose you run independent tests, each with no real effect behind it. The chance that a specific test is a false positive is , so the chance it is not a false positive is . The chance that none of the independent tests is a false positive is , and so the family-wise error rate — the chance of at least one false positive somewhere in the batch — is:
In plain English: subtract from 1 the probability that every single test correctly stays quiet, and what's left is the probability that at least one of them falsely fires. As grows, shrinks toward zero, so the FWER climbs toward 1 (certainty) — not because your tests got worse, but because you gave chance more opportunities to produce a fluke.
Each of the twenty independent yes/no trials above corresponds to one hypothesis test at , each with a 5% individual chance of a "success" (false alarm) under the null. The distribution's mass sitting on 1-or-more successes, not just its mean, is exactly what the FWER formula is quantifying.
Worked example 1: FWER for twenty backtested signals
A researcher tests twenty candidate trading signals against ten years of history, each at , and finds that none of the underlying signals has any real edge (the honest, if depressing, truth). What is the chance at least one still looks "significant" by luck?
Compute : , , , , and . So — a 64% chance that at least one of the twenty worthless signals looks significant at the 5% level, purely by luck.
Worked example 2: how fast it climbs
Redo the calculation at a few batch sizes, same : at , FWER (the advertised rate). At : . At : — already past a coin flip. At : , so FWER — a false alarm is nearly certain. The climb is not linear, since the "safe" probabilities multiply rather than add, but it is steep and relentless throughout.
The family-wise error rate is not the per-test significance level — it is the chance of any false positive across a whole batch of tests, and it grows quickly with the number of tests, even when every individual test is calibrated correctly. "5% significant" means something completely different when it is one of one test versus one of a hundred.
What this means in practice
Quant research is, structurally, a multiple-testing machine: every parameter sweep, every universe of candidate signals, every grid search over lookback windows is a batch of tests run against the same historical data. A backtest engine reporting "" for the single best result out of a thousand tried is not reporting a 5% false-alarm rate — it is close to certain that at least one fluke would have cleared that bar. Controlling the FWER, typically via Bonferroni or Holm corrections, tightens the per-test bar so the combined risk across the whole search stays at the advertised level.
FWER controls the chance of any false positive, which makes it very conservative once gets large — it is easy to demand such a strict per-test bar that you also throw away real, genuine discoveries along with the flukes. This trade-off is exactly why the false discovery rate exists as an alternative: it controls the proportion of false positives among your discoveries rather than the probability of having even one, which is far less punishing when you expect to make many real discoveries and can tolerate a controlled fraction of them being wrong.
Related concepts
Practice in interviews
Further reading
- Miller, Simultaneous Statistical Inference, ch. 1
- Harvey, Liu & Zhu (2016), ...and the Cross-Section of Expected Returns