Skip to content
AI.info

Evaluation

Quantiles, Prediction Intervals, and Probabilistic Regression

Evaluate quantile forecasts, prediction intervals, asymmetric losses, and probabilistic regression through coverage, sharpness, and proper scores.

By the end you can

A point forecast can be correct for the wrong risk decision

Two institutions that could have asked for an expected value asked for a quantile instead.

Flood maps are not drawn around an average. US regulation defines the base flood as the flood with a one percent chance of being equalled or exceeded in any given year. The Federal Emergency Management Agency does not map the average annual flood at all.

Bank supervisors do not compare a trading desk's average loss with its average forecast either. Since January 1996 the Basel Committee on Banking Supervision has had them count instead. Across 250 trading days, how often did the day's loss exceed the bank's own 99th-percentile VaR?

Both are decisions about a tail. Neither can be read off a central value. Two models with the same mean error can produce very different uncertainty ranges. Only one of them may put probability mass where the decision is actually made.

Probabilistic regression evaluates distributions, quantiles, or intervals rather than one central value.

Neither the flood map nor the capital charge is computed from a mean.

Visual

Pinball loss encodes asymmetric error

A quantile target penalizes over- and under-prediction differently. One competition made that asymmetry the entire basis of its ranking.

The Global Energy Forecasting Competition 2014 ran four tracks: load, price, wind and solar. It drew 581 contestants from 61 countries. All four tracks were scored the same way. Each contestant submitted the 1st, 2nd, …, 99th percentiles for every period of the forecast horizon. The pinball loss was then averaged over those 99 target quantiles.

The reason was plain. The organisers wrote in 2016: “Considering ease of implementation and communication, we decided to use the pinball loss function, which is closely related to the CRPS anyway.”

Ease of implementation. That is what put one asymmetric loss in charge of a whole competition.

The steps below are what that one score did, ninety-nine times over, to every submission it ranked.

FigureProcess · 4 steps
  1. 1. Choose quantile tau

    For example, tau = 0.9 targets an upper conditional quantile.

  2. 2. Compare outcome and prediction

    Determine whether the forecast lies above or below the observed value.

  3. 3. Apply asymmetric weight

    Underprediction receives weight tau; overprediction receives weight 1 − tau.

  4. 4. Average across cases

    Lower loss rewards the intended conditional quantile under suitable conditions.

Comparison

Three intervals with different meanings

The word “interval” is dangerously overloaded. The three columns below turn up inside the same documents. A bank's 99th-percentile VaR figure is a conditional quantile. The US COVID-19 Forecast Hub required a 95% prediction interval from every team, judged by how often the observed weekly count fell inside it. The standard error printed beside a fitted coefficient is neither of those. Nothing in the output marks which is which.

FigureComparison · 3 columns

Confidence interval

Uncertainty about an estimated parameter or summary.

  • Concerns an unknown quantity
  • Narrows with more information
  • Not automatically a future-outcome range
  • Depends on inferential assumptions

Prediction interval

Range intended to contain a future outcome at a target rate.

  • Includes irreducible outcome variation
  • Evaluated by empirical coverage
  • Width matters
  • Can vary by input

Quantile band

Two estimated conditional quantiles, such as the 10th and 90th.

  • Targets distribution locations
  • Often trained with pinball loss
  • Can cross without constraints
  • Coverage must be checked

Example

Coverage without width is incomplete

Coverage is a count, and two institutions publish theirs.

Banks have been counting since 1996. The Basel Committee's backtesting framework is dated 4 January 1996. It compares 250 days of trading outcomes against the bank's 99th-percentile VaR, then sorts the exception count into three zones: green (0–4), yellow (5–9) and red (ten or more). The boundaries are probability statements rather than opinions: “For 250 observations, it can be seen that five or fewer exceptions will be obtained 95.88% of the time when the true level of coverage is 99%.”

The US implementation writes the same counts into law. Under 12 CFR § 3.204 the capital multiplication factor rises from 3.00 at four or fewer exceptions to 3.40 at five and 4.00 at ten or more. Miscalibration has a price list.

Epidemic forecasting ran the same test on many models at once, and printed the result as a table. Cramer and colleagues reported in PNAS in 2022: “Across 1- through 4-wk-ahead horizons, 79 wk, and 50 states, only the ensemble model achieved near-nominal coverage rates for both the 50% and 95% PIs.” Observed coverage was typically below nominal. The rows below come from their Table 1.

  • UMass-MechBayes: 0.93 coverage at the nominal 95% level, 0.56 at the nominal 50%. Relative WIS 0.63, relative MAE 0.67.
  • USC-SI_kJalpha: nominal 95% intervals covered 0.52 of outcomes, nominal 50% intervals 0.22. Its relative WIS of 0.75 and relative MAE of 0.72 both beat the baseline's 1.00.
  • UCLA-SuEIR: 0.31 coverage at the nominal 95% level, 0.09 at the nominal 50%. Relative WIS 1.37, relative MAE 1.21. Covid19Sim-Simulator covered 34% of outcomes with its nominal 95% intervals.
  • Validity view: only the ensemble reached near-nominal coverage at both the 50% and 95% levels, across 1- to 4-week horizons, 79 weeks and 50 states. The individual models were not too wide. They were too confident.
  • Efficiency view: coverage alone cannot rank these models. That is why the hub's headline score was the weighted interval score, whose sharpness term stops an interval buying coverage with unbounded width. USC-SI_kJalpha is the converse warning: a score better than the baseline's, sitting on top of 52% coverage at the nominal 95% level.

Proper scores evaluate the whole predictive distribution

Log score, continuous ranked probability score, and related proper scores reward distributions that place probability mass honestly. They can compare more than one interval or quantile. A scalar proper score still needs calibration plots, coverage by slice, and decision analysis. Different scores emphasize different aspects of the distribution.

The goal behind all of them has a standard formulation. Gneiting and colleagues set it out in 2007: evaluate a forecast by “maximizing the sharpness of the predictive distributions subject to calibration”. Calibration is the constraint. Sharpness is the thing being pushed. Calibration is also a joint property, the statistical consistency between forecasts and observations. Sharpness is “a property of the forecasts only”.

Forecasts often arrive as a set of central prediction intervals rather than full densities. A goal of that shape needs a score of the same shape. Bracher and colleagues supplied one in 2021, and their abstract says what it does: “Specifically, we discuss the computation and interpretation of the weighted interval score, which is a proper score that approximates the continuous ranked probability score. It can be interpreted as a generalization of the absolute error to probabilistic forecasts and allows for a decomposition into a measure of sharpness and penalties for over- and underprediction.”

That decomposition is why the score is reported next to coverage rather than instead of it. The sharpness term and the two penalty terms say which way a model is failing. The coverage column says how far.

It became the headline score of the COVID-19 forecast hubs. A 2023 study applied it across 32 countries and restated the property being relied on: the score “is a strictly proper scoring rule, that is, it is optimal for predictions that come from the data-generating model”. Coverage was still assessed separately, at the k = 0.5 and k = 0.95 levels.

USC-SI_kJalpha's relative WIS of 0.75 beat the baseline's 1.00 while its nominal 95% intervals held 52% of the outcomes.

Key idea

Quantile crossing is a coherence failure

If the predicted 90th percentile falls below the predicted 50th percentile, the outputs do not define a coherent ordered set of quantiles. Independent quantile models can produce this problem.

The defect has had a name since 2007. Chernozhukov and colleagues called it “the quantile crossing problem” and treated it as a failure of monotonicity rather than of accuracy. Their remedy is “sorting or monotone rearranging the original estimated non-monotone curve into a monotone rearranged curve”, and the rearranged curve “is closer to the true quantile curve in finite samples”. Nothing about the underlying fit has to change.

Operational forecasting does not wait for the theory. It runs the check at the door. The European COVID-19 Forecast Hub rejected any weekly submission that failed the ordering, as Sherratt and colleagues describe: “Forecast validation ensured a monotonic increase of predictions with each increasing quantile, integer-valued non-negative counts of predicted cases, as well as consistent date and location definitions.”

The gate is not hypothetical. The archived US COVID-19 Forecast Hub holds 8,954 forecast files from 129 team-models, covering 2020-03-15 to 2024-04-29. Its hubverse re-encoding still lists 85 files with non-monotonic quantiles — the 0.10 quantile above the 0.05 quantile, for instance. Another 234 files are missing required quantiles.

Measure crossing frequency and severity. Then use architectural, loss-based, or post-processing constraints if the application requires coherent bands.

85 of the 8,954 archived forecast files put a lower quantile above a higher one.

Analogy

A river forecast with a central line and flood band

Narrowing the band on a river forecast looks better right up to the flood that arrives outside it. The forecast carries two things: an expected level and a range of plausible levels. Only the pair can be judged.

Flood policy settled the argument by refusing the central value altogether. 44 CFR § 59.1 states the rule in one line: “Base flood means the flood having a one percent chance of being equalled or exceeded in any given year.”

The choice is decades old. A 2010 US Geological Survey page by Holmes and Dinicola records when it was made: “In the 1960's, the United States government decided to use the 1-percent annual exceedance probability (AEP) flood as the basis for the National Flood Insurance Program”. The same page supplies the translation everyone actually uses, and the misunderstanding built into it: “Because the 1-percent AEP flood has a 1 in 100 chance of being equaled or exceeded in any 1 year, and it has an average recurrence interval of 100 years, it often is referred to as the ‘100-year flood’.”

Coverage and width are therefore read together. Some decisions ignore the band entirely. They ask instead for the level the river exceeds one year in twenty — in that vocabulary, the 0.2 AEP flood, whose average recurrence interval is 5 years.

A narrow band that misses extremes is confidence theater.

Steps

Audit probabilistic regression

Treat central tendency, tails, and decisions as separate views. None of the five steps below is an aspiration. Each one is something a named programme already performs on a schedule.

Step 1 is a submission check that runs automatically. The European COVID-19 Forecast Hub enforced a monotonic increase of predictions with each increasing quantile before a forecast was accepted.

Step 2 is the Basel exception count, codified in the US as 12 CFR § 3.204(b). A bank “must compare each of its most recent 250 business days’ trading losses … with the corresponding daily VaR-based measures calibrated to a one-day holding period and at a one-tail, 99.0 percent confidence level”. The multiplication factor then steps 3.00, 3.40, 3.50, 3.65, 3.75, 3.85 and 4.00 as exceptions run from four or fewer up to ten or more.

Step 3 is the sharpness term inside the weighted interval score.

Step 4 is the per-model coverage column in Table 1 of the COVID-19 hub evaluation. A relative WIS of 0.75 and 52% coverage at the nominal 95% level sit in the same row.

Step 5 is the flood map. The National Flood Insurance Program acts on the 1-percent annual exceedance probability level, not on the expected one.

FigureProcess · 5 steps
  1. 1. Verify quantile order

    Check crossing and monotonicity across requested levels.

  2. 2. Measure calibration

    Compare nominal and empirical quantile or interval coverage.

  3. 3. Measure sharpness

    Report width, set size, or dispersion conditional on valid coverage.

  4. 4. Slice extremes

    Inspect rare regimes, long horizons, and high-cost tails.

  5. 5. Test decisions

    Calculate utility or service levels under the forecast distribution.

Key takeaways