Repository Review Checkpoint
This is a second peer review day, placed between Physical Modeling and Data-Driven Modeling. It gives you time to learn from each other’s projects and to apply what you learned in the earlier cleanup days. The agenda may be adjusted based on what we see in your repositories.
Agenda (80 minutes)
- 5 min - Check-in and review plan
- 10 min - Short instructor debrief: common issues seen since the last review
- 35 min - Group peer review, two passes (about 15 min each, plus switch time)
- 20 min - Fix your own repository using the feedback
- 10 min - Share-out and commit-your-fixes checkpoint
Learning Goals
By the end of this class, you should be able to:
- Run a teammate’s project from a fresh clone and report what you observed.
- Turn peer feedback into concrete repository fixes.
Group Peer Review
Work in groups of two or three, and try to pair with different teammates than last time. Each reviewer clones the teammate’s repository into a new folder, follows only the README, and fills in the Quick Peer Review Form. The goal is reproducibility evidence, not grading, so record exactly which command failed and why.
Review focus:
- Can I set up and run the project from the README alone?
- Are the issues from the earlier cleanup days resolved (no clutter, reflections in
paper/, readable git history)? - Do the tests or checks run, and is it clear what a pass looks like?
- Do the documentation and reproducibility notes (Milestone 4) match what actually happens on a fresh clone?
Projects using restricted data should provide a synthetic or example workflow for review.
Fix Your Own Repository
Use the feedback you received to make at least three fixes, each as a small commit. Prioritize anything that blocked your reviewer from running your project. Leave a short note in your README or paper/ folder describing what you changed and why.
Before Next Class
- Finish remaining fixes and push them.
- Keep working toward the Project Systems milestone.