Back to curriculum
Builder project·2-3 hours
Classical Model Selection Project
Compare a linear rule, a decision stump, and a nearest-centroid classifier under one shared evaluation contract.
Scenario
A small operations team needs a transparent binary classifier and cannot support a large serving stack. Your recommendation must balance error cost, stability, and explainability.
You will demonstrate
- Use identical splits and metrics for every candidate.
- Diagnose model-specific failure modes.
- Choose complexity only when evidence justifies it.
Project evidence
Complete each deliverable.
Runnable Python lab
Select by cost, then simplicity
Compute cost from fixed confusion counts and break a tie in favor of fewer fitted parameters.
Project defense
Why must every candidate use the same held-out rows?
Assessment rubric
- Comparisons use identical evidence.
- Complexity is treated as a cost.
- Failure behavior is demonstrated, not merely named.
- The recommendation is reversible.
Project completion gate
Complete all deliverables, pass the automated code checks, and defend the key decision.
Deliverables 0/4Code pendingDefense pending