Chapter 1 · Frame and baseline

Random forests and diversity

A forest is strong when its trees are individually useful and collectively disagree in the right ways.

65–90 min4 key conceptsReviewed 26 Aug 2026
01 · Production proposition

A marketplace must catch rare fraud without blocking trustworthy sellers.

This chapter moves from create varied learners to check the diversity dividend. We will make the idea concrete in a small code example before placing it back inside a production system with reviewer capacity plus false-decline cost.

Decision

Plot held-out error and latency versus tree count, and inspect whether individual predictions remain highly correlated.

Evidence

Verify the behavior illustrated in tiny_forest.py, then measure decision utility, slice reliability, and system latency.

Failure consequence

High-cardinality IDs and random row splitting produce spectacular leakage that XGBoost exploits. An unsafe release must degrade to a named baseline or the last known-good version.

02 · Guided chapter

Build the idea one layer at a time.

A random forest gains stability by averaging trees that make different mistakes. More trees help only when there is useful diversity to average.

Bootstrap sampling changes the rows each tree sees, while random feature subsets change which questions it may ask. Averaging these decorrelated estimates mainly reduces variance without requiring one fragile tree to represent the whole boundary.

Deep trees can be reasonable inside a forest, but leakage remains leakage and correlated trees limit the benefit. Measure out-of-bag or held-out quality, prediction disagreement, memory, and batch-one latency as tree count grows.

Keep in view
  • bagging
  • feature subsampling
  • pseudo-residuals
  • second-order boosting
WORKED PATH

Follow the reasoning before touching the code.

  1. 01

    Create varied learners

    Sample training rows with replacement and expose a random subset of eligible features at each split.

  2. 02

    Aggregate in probability space

    Average class probabilities or regression outputs; do not let arbitrary tree order affect the result.

  3. 03

    Check the diversity dividend

    Plot held-out error and latency versus tree count, and inspect whether individual predictions remain highly correlated.

pythontiny_forest.py
from random import Random
rows = [([1, 8], 0), ([2, 7], 0), ([7, 2], 1), ([8, 1], 1)]
rng = Random(7)
def fit_stump(sample, feature):
    threshold = sum(row[0][feature] for row in sample) / len(sample)
    left = [row[1] for row in sample if row[0][feature] <= threshold]
    right = [row[1] for row in sample if row[0][feature] > threshold]
    rate = lambda labels: (sum(labels) + 1) / (len(labels) + 2)
    return feature, threshold, rate(left), rate(right)
trees = []
for _ in range(7):
    bootstrap = [rng.choice(rows) for _ in rows]
    trees.append(fit_stump(bootstrap, rng.randrange(2)))
query = [6, 3]
probabilities = [left if query[feature] <= threshold else right
                 for feature, threshold, left, right in trees]
print("tree votes", probabilities)
print("forest probability", sum(probabilities) / len(probabilities))

Build bootstrapped, feature-randomized stumps and average them.

READ THE EXAMPLE

What to notice

  • A fixed random seed makes the teaching forest replayable while bootstrap rows and selected features still vary by tree.
  • The list of tree probabilities exposes disagreement that the final average would otherwise hide.
YOUR TURN Pause and predict before revealing the answer.

If every tree sees every row and always chooses the same strongest feature, what happens to the forest’s variance-reduction benefit?

Need a hint?

Averaging identical errors does not cancel them.

Check your reasoning

The trees become highly correlated or identical, so averaging adds little beyond one tree; row and feature randomness create the useful diversity.

Bring forward

Lessons 1 in this course.

03 · Formal treatment

Connect the chapter to the course’s quantitative spine.

A forest is strong when its trees are individually useful and collectively disagree in the right ways. The stage-wise boosting update below is the shared course-level lens that helps quantify the surrounding system. Name each symbol, check its units or shape, and use only values that were available at the production cutoff.

Formal treatment
Fm(x)=Fm−1(x)+ηhm(x)F_m(x) = F_{m-1}(x) + \eta h_m(x)

Stage-wise boosting update

Symbol, shape or unit contract
SymbolMeaning / shape / unit
F_mensemble after stage m
h_mnew weak learner
ηlearning rate
Open derivation and numerical substitution

Start from the production quantity being optimized, substitute the observed values with their declared units, then isolate the model-controlled term. Preserve shape annotations at each step so broadcasting or aggregation cannot silently change the result.

  1. Write the named inputs: F_m, h_m, η.
  2. Substitute one small, hand-checkable batch before vectorizing.
  3. Calculate an independent reference value and compare within a declared tolerance.
# equation → code contract
inputs = validate_shapes_and_units(batch)
value = compute_c05(inputs)
assert is_finite(value)
04 · Deterministic lab

Change one assumption and make the tradeoff visible.

Use the worked chapter as your prediction, then change one input in the lab and explain why the output moves. The lab runs predefined TypeScript and never executes learner code, so the focus stays on the concept rather than setup.

Estimate

Tree capacity lab

Grow depth and compare training fit with estimated temporal generalization.

levels
Primary69.4%
Secondary73.0%
DiagnosisControlled

Assumption: Estimate calibrated to a small, imbalanced synthetic tabular dataset.

Open nonvisual data table
ItemComputed stateInterpretation
fold 170.3%stable
fold 269.6%stable
fold 368.9%stable
fold 468.2%stable
fold 567.5%stable
05 · Production implications

Trace the complete operating path.

Carry the chapter’s central idea into the system: A forest is strong when its trees are individually useful and collectively disagree in the right ways. The path below shows where that reasoning needs an artifact, a test, an owner, or a fallback.

  1. 01

    Turn “Create varied learners” into a written invariant and a failing test.

  2. 02

    Promote tiny_forest.py from illustration to a versioned implementation with representative fixtures.

  3. 03

    Use “Check the diversity dividend” as the release checkpoint: Plot held-out error and latency versus tree count, and inspect whether individual predictions remain highly correlated.

  4. 04

    Serve or materialize behind explicit reviewer capacity plus false-decline cost.

  5. 05

    Join telemetry to mature outcomes and retain a rollback path.

Observability

Join service health, input quality, prediction distributions, slice behavior, and mature outcomes by exact version.

Cost

Measure storage, preprocessing, compute, queueing, and human review under a representative arrival pattern.

Failure modes

High-cardinality IDs and random row splitting produce spectacular leakage that XGBoost exploits. Add a detector, owner, mitigation, and stop condition for this class of failure.

Alternatives

Compare a rule, a simpler statistical baseline, and a different system boundary before adding model complexity.

06 · Check understanding

Explain the contract, not just the vocabulary.

Browser-graded checkpointPass ≥ 80%
01What does each boosting learner target?
02Does SHAP prove causality?
03What does bagging mainly reduce?
07 · Apply in production

Rare-fraud ensemble decision system

Compare a tree, forest, gradient boosting, and XGBoost with temporal validation and operational thresholding.

  • Ensemble ablations
  • Cost and capacity analysis
  • Calibration and explanations
  • Latency/fallback plan
Open assignment and rubric
08 · Sources & next depth

Read primary material with a purpose.

09 · Production resolution

Return to the opening failure.

Version missing-value behavior and model format; monitor calibration, explanations, latency, and reviewer yield.

For this lesson, the release evidence is the worked code example, a hand-checked formal result, deterministic simulation output, a ≥80% checkpoint, the production rubric, and a named fallback. The course resolves when the system can produce calibrated random-forest and xgboost baselines with cost-sensitive thresholds.