Assignments

7 homeworks · 2 quizzes · 1 final project

Every homework builds directly on skills from the class that precedes it — nothing here asks you to learn something wholly new without a class session to prepare you for it first. Submission mechanics, the grace period policy, and grading weights are all on the Syllabus; this page is the content of each assignment.

Text marked PSY 0210 describes the additional graduate-level component carried by four of the seven homeworks. PSY 0110 students are welcome to attempt these for practice, but they’re neither required nor graded for that cohort — the shared portion of every homework is graded identically for both cohorts.

Homeworks

HW1 — due before Class 3

Extend the in-class Congruent/Incongruent Builder skeleton — add a routine or a condition of your own.

HW2 — due before Class 5

Add accuracy-scoring and dynamic feedback logic to your own extended task from HW1.

PSY 0210: also write a standalone Python validation script — a .py file run in PsychoPy’s Coder view that reads your conditions spreadsheet and checks every condition has ≥5 rows. This is the one time all semester everyone writes and runs a plain Python script outside Colab or a Builder component.

HW3 — due before Class 6

Finalize and pilot your task; submit your own clean pilot CSV plus a short reflection. This is the dataset Part II runs on.

PSY 0210: also write 150–250 words connecting your task design to a published two-condition within-subjects paradigm — what’s structurally similar or different.

HW4 — due before Class 8

Full dplyr wrangling script on your own HW3 pilot data, producing a clean condition-level summary table.

HW5 — due before Class 10

Simulate data for your own 1-factor/2-level design in R, with parameters loosely matched to your real HW4 result, plus a short interpretation.

PSY 0210: also re-run the simulation at two additional sample sizes and write up how the spread of the simulated effect distribution changes — informal power/precision intuition, not a formal power analysis.

HW6 — due before Class 12

Complete an apaquarto mini Methods/Results draft, combining HW4’s wrangling, the Class 8 plot, and the Class 10 test result. This draft feeds directly into your final project.

PSY 0210: also add a brief Discussion paragraph interpreting your result in light of your HW3 paradigm-connection paragraph, naming at least one limitation of your design.

HW7 — due before Class 13

Final-project checkpoint: finish debugging your novel task, pilot it on 1–2 people outside of class, wrangle/visualize/test the resulting data with your own pipeline, and push a rough-draft apaquarto report plus your task files and raw pilot data to your repo. Every step here is a repeat of something you’ve already practiced once — this is repetition on your own data, not new material.

Quizzes

Two short (15–20 minute), closed-book quizzes.

Quiz 1 — start of Class 6

Covers Classes 1–5: Python vocabulary from the readings, plus PsychoPy Builder mechanics practiced together in class.

Quiz 2 — start of Class 10

Covers Classes 6–9: RStudio and tidyverse basics, dplyr wrangling, ggplot2 visualization, and simulation.

After-the-fact make-up quizzes are given only for documented illness or emergencies; if you know about a conflict in advance, contact the instructor before the quiz date.

The Final Project

An original, two-condition PsychoPy experiment — the same structural constraint the class-wide Congruent/Incongruent task followed all semester:

  • 1 manipulated factor, exactly 2 levels
  • Up to 2 dependent variables
  • Minimum 5 observations per level
  • Genuinely your own design — not a re-skin of the shared class task

Class 12 (Project Workshop I): pitch, design, and start building. Between classes (HW7): finish debugging, pilot on 1–2 people, get a rough-draft analysis and report going. Class 13 (Project Workshop II & Finale): polish and publish what you already have — not build it for the first time.

Publishing means your finished PsychoPy files, your (lightly de-identified) raw pilot data, and your finalized apaquarto report land in your repo’s task/, data/, and analysis/ folders, followed by a GitHub Release archived to Zenodo for a DOI — the last action of the semester, done together in class on the last day.

Back to top