Session 14: Project Work — Finalize Report & Notebook

Day 5 · Project Finalization & Presentations (5-2)

Warning🚧 Being prepared

This page is being finalized ahead of the course (Aug 3–7, 2026) and may be incomplete or change before your session. The syllabus and readings are ready now.

Learning objectives

By the end of this session you will be able to:

• Attribute concrete errors to the model or to the scheme, with a reason for each.
• Write limitations that apply to your run rather than generic ones.
• Assemble the submission bundle and confirm the notebook runs top to bottom on a fresh runtime.
• Build five slides that map onto the report’s sections.

Agenda

1. Error analysis — show_errors, then cross-reference against the rows you adjudicated in Session 12. Overlap between the two is a finding, not a failure.
2. Write the report — your own two pages, six sections, from the numbers 06_report.ipynb prints on screen.
3. Build the bundle — python scripts/make_submission.py --group <yours>, then check what it says is missing.
4. Restart and Run all — if your notebook only works in the session you built it in, it does not reproduce.
5. Five slides, one per section from methodology onward.

Reading

No new reading — Day 5 is project work only (see the Readings page).

Slides & Colab

Mini-project

06_report.ipynb — error analysis and export — then submission.

• What goes in the bundle, and how to turn it in: Deliverables.
• What earns marks: Rubric.

WarningThe report is written individually

Your group runs one study and hands in one bundle. Each member then writes their own two-page report and uploads it separately. Sections 5 and 6 — what you make of the errors, and which limits you think matter — are where two members of the same group should differ.