# Project Milestone 5: Final Progress Report

**Due: April 24 (submit PDF on Blackboard)**

Presentations are the week of April 28, and the final writeup is due Monday, May 11. This milestone is your last structured check-in before the finish line — a chance to take stock of where you are and lay out a concrete plan for completing everything.

By now you should have most of your infrastructure in place and be deep into running experiments. The goal here is to surface where you stand, flag anything that's still unresolved, and make a realistic plan for getting the project to a presentable and writable state.

---

## Part 1: Progress Since M4

Describe concretely what you've done since the M4 progress report. This might include: completing your data pipeline, running initial or full experiments, obtaining results, or refining your methodology. Report any results you have — even preliminary, negative, or inconclusive ones. Vague summaries ("we made progress on experiments") are not useful.

If your direction, dataset, or methodology has shifted since M4, explain what changed and why.

---

## Part 2: Completion Plan

Your plan should address two targets separately: the presentation and the final writeup.

### Presentation (Apr 28–30)

Your presentation should cover your full research arc — motivation, data, hypothesis, methodology, results, and discussion. You don't need every last experiment finished, but you must have substantive results to present and something concrete to say about what they mean.

Describe specifically:

- What results will you present? Are they in hand, or still in progress?
- What, if anything, still needs to run before the presentation?
- Are there any aspects of the presentation (e.g., analysis, visualizations) that need work beyond just getting results?

### Final Writeup (Due May 11)

The writeup requires the same components as the presentation but in paper form, plus a Related Work section. It also gives you the opportunity to incorporate feedback from the presentation.

Describe specifically:

- What additional work (experiments, analysis, writing) will happen between the presentation and the writeup deadline?
- Is there anything you plan to leave out of the presentation but include in the writeup?

### Week-by-Week Plan

Lay out your plan from now through May 11:

| Date | Task |
|------|------|
| Week of Apr 21 | Code walkthrough meeting |
| Apr 24 | M5 due |
| Apr 28–30 | Presentations |
| May 11 | Final writeup due |

Fill in what you expect to accomplish each week. Be realistic — a plan that assumes 30 hours in the last week is not a plan.

---

## Ask for Guidance

Flag anything you'd like feedback on. I can respond in writing or address it when we meet for the code walkthrough.

Things worth flagging:

- Results that are surprising, negative, or hard to interpret
- Uncertainty about how to frame your analysis or discussion
- Scope concerns — too much left to finish, or results that feel thin
- Anything about the final writeup format or expectations

---

## Formatting and Logistics

- Submit the progress report as a single PDF on Blackboard
- If working in a group, all members submit the same document
- Include a link to your GitHub repository at the top of the document