Class 13 — Final Project: Report & Finale

Part III
The last class of the semester! Troubleshoot HW7’s pipeline, finalize your apaquarto report, and push a complete, publication-ready project.
Published

December 8, 2026

This is the last class of the semester, and it mirrors Class 9’s report-assembly day: you arrive with HW7’s simulation, wrangling, and visualization already done, so today is almost entirely assembling that into a finished report, getting your repo publication-ready, and presenting one favorite result. You’ll troubleshoot whatever’s still broken in your pipeline, finalize your apaquarto Method/Results report with computed M/SD prose, and push everything to your GitHub repo — a complete, publication-ready demonstration of a semester of work. (Your course repo will remain private; if you’d like a public copy for your portfolio, see the Publishing Your Repository tab on Resources.) You’ll close with a gallery of everyone’s favorite visualizations. Every student’s plot appears in one shared deck, and five presenters are selected at random live with R (one last, on-theme use of sample()) to say a few words about theirs. We’ll end with a short reflection on how far you’ve come since Class 1.

Reading due: — · Due the night before (Mon 12/7, 11:59 PM): HW7

What you’ll be able to do

  1. Diagnose and fix gaps or errors in your own HW7 pipeline (simulation, wrangling, or visualization), using troubleshooting resources built across the semester.
  2. Finalize an apaquarto mini Method/Results report describing your novel task and its simulated result, with numbers computed via inline code rather than typed by hand.
  3. Push a complete, publication-ready project (task, data, analysis, report, your own README) to your course GitHub repo.
  4. Contribute one visualization from your own report to the class gallery (five randomly drawn students present theirs briefly), and articulate one thing you can do now that you couldn’t do in Class 1.

During the polish window (Dec 8–14): your project README

Before the Mon Dec 14, 11:59 PM due date, replace your repo’s README, which shows the course-template instructions from when you created your repo from the course template earlier in the semester, with a short project README of your own. The README is the front page of your project, and is an important part of making your repo publication-ready (see Assignments).

Copy this skeleton into README.md at your repo’s root and fill it in; a sentence or two per section is plenty.

# Your task's name

One short paragraph: what your experiment is, what the one manipulated
factor and its two levels are, and what it measures.

## What's in this repo

A sentence after the '—' for each folder explaining what it contains

- `task/` — 
- `data/` — 
- `analysis/` — 

## Running the task

A few sentences about what readers should do if they want to run the task

## A note on the data

A few sentences about the context for this project; reference this course and make sure readers know the data were simulated
Back to top