Ensemble Method

An ensemble method combines multiple models to improve robustness or predictive performance.

The generic form is a weighted combination of base models:

where is a base model and is its weight.

Common Patterns

  • Bagging trains models on resampled data and averages their predictions.
  • Boosting trains models sequentially to correct previous errors.
  • Stacking trains a meta-model over base model predictions.

For classification, averaged class probabilities are common:

For bagging with uniform weights:

Boosting builds an additive model:

where each weak learner is chosen to reduce the current residual or gradient signal.

Why It Matters

Ensembles often improve tabular prediction and reduce variance, but they can also hide failure modes if evaluation is weak.

Bias and Variance View

For independent base predictors with variance , averaging reduces variance:

If predictors are correlated with pairwise correlation , the reduction is weaker:

This is why model diversity matters. Many identical models do not make a strong ensemble.

Ensemble Types

TypeMain ideaTypical use
Baggingaverage models trained on resampled datareduce variance of unstable learners
Random forestbagging plus random feature splitsrobust tabular baseline
Boostingsequentially add weak learnersstrong tabular prediction
Stackingtrain a meta-model over base predictionscombine heterogeneous models
Snapshot/seed ensembleaverage neural checkpoints or seedsreduce stochastic training variance

Evaluation Boundary

Ensembling must be evaluated on data not used to choose base models, weights, or stacking meta-features.

RiskWhy
stacking on validation predictions then reporting same validation scoremeta-model leaks validation labels
selecting ensemble members by test performancetest set becomes training signal
averaging uncalibrated probabilitiesaccuracy may improve while calibration worsens
ensemble hides subgroup failureaverage metric improves but slices degrade

For classification, calibration should be checked after ensembling, not assumed from better accuracy.

Checks

  • Were base models trained without leaking validation or test labels?
  • Does ensembling improve the target metric or only average away calibration errors?
  • Is the compute cost acceptable for the deployment path?
  • Does model diversity come from data, features, architecture, seed, or objective?
  • Were ensemble weights selected on validation data only?
  • Does performance improve on relevant slices, not just the average metric?