Stacking and blending combine multiple models to improve predictions. The key metric depends on the task: for classification, accuracy, precision, recall, and F1 score matter. For regression, mean squared error or R-squared are important. We focus on metrics that show if the combined model predicts better than individual models. This helps us know if stacking or blending truly improves results.
Stacking and blending in ML Python - Model Metrics & Evaluation
Start learning this pattern below
Jump into concepts and practice - no test required
Suppose we stack two models to detect spam emails. After combining, the confusion matrix might look like this:
| Predicted Spam | Predicted Not Spam |
|----------------|--------------------|
| True Positives (TP) = 85 |
| False Positives (FP) = 15 |
| False Negatives (FN) = 10 |
| True Negatives (TN) = 90 |
Total samples = 85 + 15 + 10 + 90 = 200
From this, we calculate:
- Precision = TP / (TP + FP) = 85 / (85 + 15) = 0.85
- Recall = TP / (TP + FN) = 85 / (85 + 10) = 0.8947
- F1 Score = 2 * (Precision * Recall) / (Precision + Recall) ≈ 0.871
Stacking and blending aim to balance precision and recall better than single models. For example:
- If a spam filter has high precision but low recall, it misses many spam emails (bad for users).
- If it has high recall but low precision, many good emails are marked spam (annoying).
Stacking can combine models that are good at precision with those good at recall to get a better balance. This tradeoff depends on the problem's needs.
Good stacking/blending results show:
- Higher accuracy or F1 score than any single model alone.
- Balanced precision and recall suitable for the task.
- Stable performance on new data (not just training data).
Bad results show:
- No improvement or worse metrics compared to best single model.
- Overfitting signs: very high training accuracy but low test accuracy.
- Unbalanced precision or recall causing practical problems.
- Data leakage: Using test data in training the stacking model inflates metrics falsely.
- Overfitting: The meta-model may memorize training data, showing high training but poor test metrics.
- Ignoring metric tradeoffs: Focusing only on accuracy can hide poor recall or precision.
- Confusion matrix mismatch: Not verifying that TP, FP, TN, FN add up correctly can cause wrong metric calculations.
Your stacking model has 98% accuracy but only 12% recall on fraud detection. Is it good for production? Why or why not?
Answer: No, it is not good. High accuracy can be misleading if the fraud class is rare. The very low recall means the model misses most fraud cases, which is dangerous. For fraud detection, high recall is critical to catch as many frauds as possible.
Practice
Solution
Step 1: Understand the purpose of stacking and blending
Stacking and blending are ensemble techniques that combine predictions from multiple models.Step 2: Identify the goal of combining models
The goal is to improve prediction accuracy by leveraging strengths of different models.Final Answer:
To combine multiple models to improve prediction accuracy -> Option AQuick Check:
Stacking and blending = combine models for better accuracy [OK]
- Thinking stacking reduces dataset size
- Believing stacking replaces base models
- Confusing speed with accuracy improvement
Solution
Step 1: Recall stacking training method
Stacking trains the final model on predictions generated by base models using cross-validation.Step 2: Compare options to stacking method
Only Using cross-validation predictions from base models mentions cross-validation predictions, which is key to stacking.Final Answer:
Using cross-validation predictions from base models -> Option BQuick Check:
Stacking uses cross-validation predictions [OK]
- Confusing stacking with blending's holdout set
- Thinking stacking uses entire data without splits
- Assuming random feature subsets are used
X_blend_train if X_train has shape (1000, 10) and holdout_ratio=0.2?
from sklearn.model_selection import train_test_split X_train_full, X_holdout, y_train_full, y_holdout = train_test_split(X_train, y_train, test_size=holdout_ratio, random_state=42) # Base model predictions on holdout base_pred_holdout = base_model.predict(X_holdout) # Blending training data X_blend_train = base_pred_holdout.reshape(-1, 1)
Solution
Step 1: Calculate holdout set size
With 1000 samples and 0.2 holdout ratio, holdout size = 1000 * 0.2 = 200 samples.Step 2: Determine shape of base model predictions
Base model predicts on holdout set, so predictions have shape (200,). Reshaping to (-1, 1) makes it (200, 1).Final Answer:
(200, 1) -> Option AQuick Check:
Holdout size 200, reshape to (200,1) [OK]
- Using full training size instead of holdout size
- Confusing reshape dimensions
- Assuming predictions keep original feature count
ValueError: Found input variables with inconsistent numbers of samples. What is the likely cause?
from sklearn.linear_model import LogisticRegression from sklearn.ensemble import RandomForestClassifier from sklearn.model_selection import cross_val_predict base1 = LogisticRegression() base2 = RandomForestClassifier() pred1 = cross_val_predict(base1, X_train, y_train, cv=5) pred2 = cross_val_predict(base2, X_train, y_train, cv=5) X_meta = np.column_stack((pred1, pred2)) meta_model = LogisticRegression() meta_model.fit(X_meta, y_train)
Solution
Step 1: Understand cross_val_predict output
cross_val_predict returns predictions for each sample in X_train, so pred1 and pred2 should have length equal to X_train.Step 2: Identify cause of inconsistent sample sizes
If pred1 or pred2 have different lengths than y_train, stacking fails due to mismatch in input sizes.Final Answer:
Base model predictions have different lengths than y_train -> Option DQuick Check:
Prediction length mismatch causes ValueError [OK]
- Assuming models must be pre-fitted before cross_val_predict
- Thinking cv=5 is invalid for cross_val_predict
- Believing meta model type causes this error
Solution
Step 1: Understand blending process
Blending trains base models on full training data, then uses their predictions on a separate holdout set to train the blender model.Step 2: Evaluate options against blending steps
Only Train base models on full training data, predict on holdout, then train blender on holdout predictions correctly describes training base models on full data, predicting on holdout, and training blender on those predictions.Final Answer:
Train base models on full training data, predict on holdout, then train blender on holdout predictions -> Option CQuick Check:
Blending uses holdout predictions for blender training [OK]
- Training base models on holdout instead of full data
- Training blender without holdout predictions
- Ignoring holdout set in blending
