Forecasting at Scale advanced 7 min read 14 flashcards

Forecast Evaluation at Scale

Why MAPE fails on the series that matter most, which scale-free metrics work instead, and how aggregating errors across a heterogeneous population hides the failures worth finding.

Comparing forecasts across a thousand series requires a metric that means the same thing on a series selling ten units a day and one selling ten thousand. The default choice fails exactly where forecasting is hardest, and the aggregation that follows hides the rest.

Why MAPE fails

Mean absolute percentage error divides by the actual value, which is undefined when the actual is zero and enormous when it is small. Intermittent demand series contain many zeros and many small values, so MAPE is either undefined or dominated by the days when almost nothing sold.

It is also asymmetric: over-forecasting is bounded above by nothing while under-forecasting is bounded by 100 percent, so a model minimising MAPE is systematically pushed to under-forecast. That bias is invisible in the metric and expensive in inventory.

Symmetric MAPE fixes the boundedness and not the zero problem, and it introduces its own asymmetry.

The metrics that work

Mean absolute scaled error divides the model's absolute error by the in-sample absolute error of a naive forecast, typically seasonal naive.

\[\text{MASE} = \frac{\frac{1}{h}\sum_{t}|y_t - \hat{y}_t|}{\frac{1}{n-m}\sum_{t=m+1}^{n}|y_t - y_{t-m}|}\]

It is defined whenever the naive forecast has non-zero error, is scale-free, and has an interpretation: below one means better than the naive benchmark, above one means worse. That interpretability is why it is the recommended default for cross-series comparison.

Weighted absolute error aggregates the total absolute error across series divided by the total actuals, which weights series by their volume. This is the right metric when the business cost is proportional to units, and it deliberately ignores small series, so it should be reported alongside a scale-free metric rather than instead of one.

Pinball loss for probabilistic forecasts, and CRPS for the whole distribution.

Aggregation hides the failures

A single number over a heterogeneous population is dominated by whatever is most numerous or largest, so a forecast that is excellent on high-volume smooth series and useless on the intermittent tail reports a good average. Since the tail is usually where the inventory cost concentrates, the reported metric is anti-correlated with the problem.

The reporting that works is stratified: by volume decile, by intermittency, by series age, and by whatever business segmentation the decisions follow. The distribution of per-series MASE, particularly its upper tail, is more informative than its mean.

When it breaks

Backtesting must respect time. Random splits leak the future, and a single train-test split gives one noisy estimate. Rolling-origin evaluation, refitting and forecasting forward repeatedly, is the honest procedure and costs many refits, which is why it is often skipped for global models.

The horizon matters and is often averaged away. Accuracy at one step and at twelve steps are different problems with different uses, and a single metric averaged over the horizon hides that a model is good at one and poor at the other.

Forecast accuracy is not decision quality. The decision uses the forecast plus a cost structure, so a more accurate forecast can produce worse decisions if its errors are in the expensive direction. Evaluating on the decision's cost, where that is expressible, is closer to the thing that matters.

Point metrics cannot evaluate a distribution. Comparing the mean of a probabilistic forecast to actuals discards everything the distribution added and rewards a model that predicts the mean well while getting the spread wrong.

Check yourself

14 flashcards for this concept

Click a card to reveal the answer.

Drill the whole track