15-622 (Grad) Grad Composition Project#
Important
This project is for 15-622 (graduate) students only. 15-322 students complete Assignment 9: Creative Tool and then the 15-322 (Undergrad) Final Composition Project instead.
Due: Mon Nov 23 2026 by 11:59PM Eastern#
Warning
To encourage you to spend more time focusing on your term project, your final composition is due Mon Nov 23 (one week before the undergraduate deadline).
Overview#
For the Grad Composition Project, 15-622 students create a computer music composition that will be played for the class at the composition concert on Tue Dec 1, alongside the 15-322 Final Composition Projects. This is separate from, and in addition to, your Term Project.
Follow the full description on the 15-322 Final Composition Project page, including the Python / Pyquist and pq.Score requirements, the rules for reusing material (and the ban on AI audio, image, and video generation), the content guidelines, and the audio, visual, COMPOSITION.md, and submission requirements. The differences for 15-622 students are:
Due one week earlier: Mon Nov 23, instead of Mon Nov 30.
No creative tool requirement. You do not need to build or use an Assignment 9 creative tool. Under
## Creative toolinCOMPOSITION.md, write “Not applicable (15-622).”Late policy: The standard late policy applies, so the latest you can submit is Sat Nov 28. Your piece must be in by then to receive any partial credit.
Rubric: see below. The points that 15-322 students earn for using their creative tool are redistributed to uniqueness and creativity.
Like the 15-322 compositions, your piece is eligible for the class vote and the prize for the most-voted composition. You may also remain anonymous.
Submission#
Bundle your submission exactly as described on the 15-322 Final Composition Project page and submit it via Gradescope.
Rubric#
The Gradescope autograder checks the audio requirements and submission format (20 points). The remaining 80 points are graded manually after the deadline.
Criterion |
Points |
|---|---|
Audio requirements (autograded). 4 points each: stereo WAV at 44.1/48kHz and 16/24-bit; no clipping and normalized; no silence longer than 5 seconds; length 60–120 seconds. |
16 |
Submission format (autograded). Files named and structured as specified; |
4 |
Visual. A slide or video suitable for the concert, with the title of your piece and a relevant image. |
4 |
Motivation. |
4 |
Computer music techniques in Python / Pyquist. 5 points per technique that is implemented in your Python / Pyquist code and explained well (where in the code, where in the piece, how it works), up to 4 techniques. If a substantial portion of |
20 |
|
4 |
Mixing. The piece is intentionally mixed (amplitude control over time, balance, focus), free of unintended artifacts like clicks, and the mixing is described concisely. |
4 |
Program notes. Interesting to read, and say something about how the piece was made. |
4 |
Uniqueness of implementations. 12: very unique and/or complex. 6: some development, but close to class examples. 0: replicates class examples. |
12 |
Overall creativity. 12: has impact or evokes a response. 6: relates to your stated motivation, but not strongly. 0: uninspiring. |
12 |
Week 14 attendance. Attended both Week 14 classes (Tue Dec 1 and Thu Dec 3). 16 for both, 0 for one or none. |
16 |
Total |
100 |