Project 8 - Due Tue Nov 5 at 23:00
Reading
- Slides and notebooks from Lec 14 (List Comprehensions; Sorting), along with Lec 15 (File Input/Output).
- Problems and solutions from Lab 8 (Nested Loops) are still relevant, but the focus is on Lab 9 (Tracing & Files).
- Think Python, Chapter 14 covers files. Sections 14.1, 14.2, and 14.5 are most relevant to what we cover, with 14.4 becoming relevant next week.
Tasks
The instructions for each task:
-
Task 1: Transcript Manager — Write functions which operate on chat transcripts and use file I/O to store their results in output files. For this task, having a partner is optional but recommended.
-
Task 2: Custom Scene #2 — Review concepts to far using
turtle
graphics. For this task, having a partner is optional but recommended. - Task 3: Custom Tune #2 —
Review concepts to far using
wavesynth
audio. For this task, having a partner is optional but recommended.
About this Project
These tasks will give you practice with file input/output, and some general review of previous concepts including conditionals, function definitions, and nested loops.
You are required to do the transcriptManager
task, and you must do one
of the turtleScene2
or wavesynthTune2
tasks (so you need to do 2
tasks in total, one of which must be transcriptManager
).
If you want to find a partner to work with for this project, use this Google Sheet to do so.
Reminders
- Remember to download the starter code for each task from the Potluck server.
Time Estimate
Our per-task estimate for this project is 2-4 hours, plus up to an hour of reading.
How to turn in this Project
If you do the turtle scene 2 task you will take a screenshot of your scene, which you will submit in addition to your code.
- For each team, one screenshot should be uploaded to this shared
google drive folder:
- Take a screenshot of your graphics scene (screenshot instructions here).
- Rename your screenshot with a short, unique descriptive name
that begins with your CS account names.
For example,
ww16_astracks_underwaterMonkey.jpg
. - Drag your properly named screenshot into the shared google drive folder by Tue Nov 5 at 23:00.
Similarly, if you do the wavesynth tune 2
task you should save the
.wav file produced by your code using the saveTrack
function and submit
that.
-
For each team, one
.wav
file should be uploaded to this shared google drive folder:- Save your tune using
saveTrack
at the end of your code. - Rename your
.wav
file with a short, unique descriptive name that begins with your CS account names. For example,ww16_astracks_blues.wav
. - Drag your properly named file into the shared google drive folder by Tue Nov 5 at 23:00.
- Save your tune using
-
Upload your tasks via the Potluck server by the deadline (Tue Nov 5 at 23:00).
- For transcriptManager, each team member must submit
transcriptManager.py
. - For turtleScene2, each team member must submit
scene2.py
. - For wavesynthTune2, each team member must submit
tune2.py
.
- For transcriptManager, each team member must submit
-
Double-check the status of your submitted tasks, since there may be warnings.
-
Reminder: you can submit as many times as you like, and only the most recent submission will count for your grade.
-
If you run into trouble with the submissions server, contact Peter Mawhorter, and include a copy of the file(s) you were trying to submit.
- Check your score for each task and submit revisions if you need to.