Lab 1: How to work on psets
To access starter code and to turn in your problem sets, you will upload your Python code via the Potluck server. This page gives detailed instructions for using it, and will walk you through the process of submitting an "example" task that has been set up on the server for this purpose.
The Potluck server enables you to do the following:
- download starter code for an assignment
- upload your finished code
- secure a 24hr pset extension (if desired)
- obtain feedback on your uploaded code
- submit revisions and obtain feedback immediately
In order to use the server, you must first authenticate by logging into your Wellesley domain account (you will be prompted to do so).
Note that the example problem set's due date has been adjusted so that it is currently in the revision period. This means that every time you submit something, you can see feedback immediately (and for a real problem set, you could use that feedback to guide your next submission).
Welcome to the Potluck server
Accessing starter files
For all tasks, there will be some starter files that we supply. To access them:
- Go to the CS111 Potluck Server.
- Authenticate by logging into your Wellesley domain account.
- Scroll down to the task you want to work on (for today, go to the Example Task which is at the top).
- Click on the "Download starter files link" on the right-hand side.
- Your browser should download a
- You need to extract the
.zipfile before you can work with the files inside. On a Mac, double-clicking should work, on Windows after double-clicking you may need to click on the "Extract all" button.
Download and extract the starter files for the example task now to make sure you know how to access starter files.
Step-by-step instructions for uploading your code
- Go to the CS111 Potluck Server and authenticate.
- You'll see Potluck's dashboard.
Note that each task has a light blue background right now. This example will focus on the "example" pset, which has only one task called "Example Task" (in the red rectangle below)
- Click on "Choose File" and browse to find the
hello.pyfile in the lab01 starter files. Note that your selected Python file must have the exact name
hello.py, any other file name will generate an error.
Enter a number in the box following "How many hours have you spent on this task (across all attempts)?". If you type a word like "two" Potluck will remind you to enter a number. Your hours spent may be an integer (eg 3) or a decimal (eg 3.5).
Click on the "Submit task" button (it is disabled until you select a valid file and enter your time spent)
This will bring you to a new window.
Note that the text at the bottom initially says "Evaluation is still in progress".
Click refresh to see the results of your code evaluation (note that it's possible for more complex tasks to take a bit of time to be evaluated but most tasks should be done in 10 seconds or less, and the evaluation process will be terminated if it takes longer than 60 seconds).
If you submitted the starter file (as we instructed), you should see a message which warns about this. If you scroll down, you will see a report showing that one of the two goals was accomplished but the other was not: the starter file does use
- Now, we should edit the
hello.pyfile to fix the issue and submit another revision. Use Thonny to open
hello.py, and add 'world' plus an exclamation mark (inside the double-quotes) it so that it looks exactly like this:
In your browser, use the link near the top to go back to the dashboard, and submit it again.
You will have to refresh the page one more time, after which you should get a message in green which says "Your submission is at least partially complete."
It will look like this:
- Because you are submitting during the revision period, you can view
full feedback immediately (otherwise the "at least partially complete"
message is all you'll see).
When you scroll down, the rubric report should now indicate that both of the goals are met, which looks like this:
Note that included in the feedback is a copy of your submitted code, as well as a report listing test results which were produced while evaluating the goals. It also includes a copy of the task instructions, and if there were examples that came with the instructions, it includes those too.
- Go back to the Potluck dashboard again, using the "Back to the dashboard" link.
- Back at the Potluck dashboard, note the following:
- the background of the exmpleTask entry is now green, and it has both
an ellipsis (for the 'initial' submission) and a check-mark in the
upper-left (in contrast to the light blue backgrounds and ellipses
for other unsubmitted tasks)
- you can resubmit your
hello.pyfile multiple times during the revision period, like we just did (you can also resubmit before the initial deadline, although you can't see detailed feedback until the revision period starts)
- the background of the exmpleTask entry is now green, and it has both an ellipsis (for the 'initial' submission) and a check-mark in the upper-left (in contrast to the light blue backgrounds and ellipses for other unsubmitted tasks)
- OPTIONAL EXTENSION
Before the revision period starts (for example, for problem set 1 right now), there is a "Take an extension" button on the left of every problem set. If you opt to take an extension on a pset (applies to all tasks), click this button and your 24 hour extension is automatically granted.
Note that there is currently no way you to undo taking extension, and you won't see feedback until the new extended deadline. Also note that taking an extension does not affect the revision deadline. Get in touch with an instructor if circumstances require additional flexibility.
- This shows how the Potluck server reflects the newly amended due date,
taking the extension into account for the example task.
Table of Contents
- Lab 1 Home
- Part 1: Thonny intro
- Part 2: How to work on psets
- Part 3: Your first program
- Part 4: Pictures and sounds
- Part 5A: Turtle graphics
- Part 5B: Wavesynth sounds
- Part 6: Save your work