Aerobrakes — Lesson 9: Comparative Analysis
Phase 1's core question finally gets answered this session: given everything the team has learned, which algorithm should actually fly?
Objective: students defend a data-backed recommendation for which algorithm the team should fly.
Session Activities
Using the full metrics table built up across Lessons 5–8 — altitude error, overshoot, actuator cycles, settling time, plus how each algorithm held up under noise from Lesson 8 — each student individually presents which algorithm they'd choose to fly, and why, using the data rather than a gut preference.
Cross-questioning between team members is encouraged here, not just tolerated. This is a direct application of the course's standing rule that everyone must always be able to completely explain their reasoning to their mentor — treat this session as practice for exactly that.
Maps to milestone P1-M4 (closes out this milestone).