CS111A Project 01 - Due Wed Sep 09 at 23:00

Reading

1. The course policies page gives an overview of projects, and the collaboration section has a detailed description of how you may collaborate on the projects (in short: you can work with one partner per week, but you should not collaborate except to answer high-level questions with anyone else).

2. This project is based on the following materials:

   • Course Intro Lecture slides and notebook
   • Lab 01
   • Python Intro Lecture slides and notebook
   • The CS 111 Code Style Guide describes rules for Python coding style that you should follow.
   • The Turtle Functions Reference has a quick summary of all of the turtle and turtleBeads functions you will need for the scene task (if you choose to work on that rather than the audio task).
   • The Wavesynth Functions Reference has a quick summary of all of the wavesynth functions you will need for the music task (if you choose to work on that rather than the scene task).

   • Optional reading from the Think Python book:

     • Ch. 1: Programming as a way of thinking
     • Ch. 2: Variables and Statements
     • Sec. 5.11: Keyboard Input
     • Sec. 5.12: Debugging

About this Project

This project will give you practice with basic Python interactive programs as well as with creating images with the turtle and turtleBeads modules or creating music with the wavesynth module. You will be ready to start any task after the first lab, but may want to complete most of the weekly exercises first to make sure you're well-prepared.

This week, you must choose either the "Custom Scene" or "Custom Tune" task, and you must complete the "Bug Hunt" task in addition to one of those. We strongly recommend that you complete all of the tasks each week if you are planning to study further in computer science.

Notes

• We recommend that you complete the exercises for this week before you start working on the tasks.
• Reminder: Collaboration and honor code: you can talk with other individuals and teams about high-level problem-solving strategies, and about code, but you must understand all the code that you submit: you cannot simply submit someone else's solution.
• You should try to submit all tasks before the regular Wed Sep 09 11pm deadline. But you can still continue to submit tasks during the revision period, which ends Sat Sep 12 11pm.
• Each taks will be graded both on correctness (65%) and style (35%).
  • For style, follow the guides presented in the CS111 Code Style Guide.
• If you have any project questions, email Prof. Lyn.
• To access the starter code and to submit each task, you will use the Potluck server. We will go over how to do this during Lab 1.
• When you're done with the tasks, follow the submission instructions below to submit the project.

Tasks

For this project you must do at least one of Tasks 1 and 2, and everyone is required to do Task 3. If you do both Tasks 1 and 2, you will receive the higher of the grades for those two tasks as your multimedia grade for this project.

• Task 1: Custom Scene Use turtle graphics to draw a picture. This task is an alternative to the the wavesynth tune task: you may choose to do one or the other, but you do not have to do both. This is an indvidual task that you must do on your own.

• Task 2: Custom Tune Use wavesynth audio to create a tune. This task is an alternative to the the turtle scene task: you may choose to do one or the other, but you do not have to do both. This is an indvidual task that you must do on your own.

• Task 3: Bug Hunt Improve your understanding of types and operators by fixing some problems in a broken math practice program. For this task, having a partner is optional but recommended.

How to Submit this Project

Preparing your submission

You will be submitting two or three .py files:

• If you did Task 1, the file to submit for this task is name scene.py
• If you did Task 2, the file to submit for this taske is named tune.py
• Everyone is required to do Task 3. The file to submit for this taske is named mathPractice.py

In each of the above .py files, ensure that you (and a partner, if applicable) are listed in the Authors: line in the triply-quoted docstring at the top of the file, and that other information in the docstring is correct.

For example, here's a sample docstring for scene.py:

"""                                                                                        
Authors: Georgia Dome                                                                      
Consulted: Lyn, Jessalyn                                                                   
Date: 2026-09-08                                                                           
Purpose: Turtle Scene task                                                                 
"""

And here's a sample docstring for mathPractice.py:

"""                                                                                        
Authors: Georgia Dome, Abby Stracksen                                                      
Consulted: N/A                                                                             
Date: 2026-09-07                                                                           
Purpose: Debugged mathPractice.py for CS111 debugging task                                 
"""

Submitting your .py files via Gradescope

Project programming assignments in CS111A will be submitted via Gradescope. Each student in the class has been enrolled in the CS111A Fall 2026 course.

Whether or not you worked with a partner, each student should submit the two (or three, if you did all three tasks) .py files listed above as follows:

1. In the CS111A Gradescope course, navigate to the Project01 assignment.

2. Initially clicking on the assignment will give a popup window that asks you to submit your program files by dragging and dropping them into the popup window. You should submit the two (or three) .py files described above at the same time in this one popup window, and then click Upload.

3. After uploading your .py files, you will be brought to an Autograder Results tab in a screen that looks like this:

   

   Because Project 01 does not use any autograding, there are no autograding results being displayed.

   When your project is graded, you will see the grading feedback for your submission in the grading feedback pane to the right.

4. But for now, click on the Code tab to verify that your .py files have been uploaded correctly. For example, here is Georgia Dome's uploaded scene.py file:

   

   And here is Georgia Dome's uploaded mathPractice.py file:

   

5. If you make changes to any programs, and wish to resubmit them, click the Resubmit button. You must submit all of your .py files again, not just the .py file(s) that changed!.

   You can resubmit as many times as you wish before the project deadline.