Assignments (With Guidelines Inspired From CS 221)
Assignments and Due Dates
Each assignment will have a written part and a
programming part. The following explains what we
expect for each part and submission instructions.
Clearly written homeworks are much easier to grade and provide feedback on, and so we
encourage students to type their assignments, but this is not a requirement. You will
receive one (1) bonus point for submitting a typed written assignment
(e.g. LaTeX, Microsoft Word). You may alternatively scan (to a pdf) handwritten
assignments: handwritten assignments will not receive the bonus point.
The grader runs on Python 2.7, which is not guaranteed to work with newer versions (Python 3)
or older versions (below 2.7). Please use Python 2.7.X
to develop your code. The final grading will be run on Linux servers and will be compatible with
all Python 2.7.X versions.
The submitted code will not
be graded if it has one or more of the
Code that uses Python packages outside the standard library are not guaranteed to work.
For example, you may not use an external package that implements q-learning.
The code quits in an unexpected way. To prevent this, do not use
The code reads external resources beyond the files provided for the homework.
Malicious code is considered a violation of the honor code, will receive a score
of zero and will be reported to the Office of Judicial Affairs.
For collaboration policy and things to keep in mind regarding academic misconduct please see
the information here
See regrading policies here
We will use GradeScope for grading written problems. To sign up for our class, follow the
Go to https://gradescope.com/.
Click “Sign up for free” and select “I am a student”.
Sign in with your Stanford SUNet id email account.
Use Entry code: 9ZRKJ3.
If you have any questions, please reach out on Piazza
All assignments (homework problems and project milestones) must be submitted on
by 11:00 PM (23:00)
Make sure to compile all written portions into a single PDF file before uploading to
GradeScope. Mark each page to the corresponding problem.
All assignments (homework problems and project milestones) must be submitted using the submit
script by 11:00 PM (23:00)
. Please note that the submission script
only works on
To submit your assignment, please follow the instructions below:
Zip your assignment by running the following command in your assignment folder:
Copy your submission files (usually <assignment ID>.zip) to
rice.stanford.edu. You can use a graphical interface
Fugu) or the following command:
- scp <your submission file(s)> <your SUNetID> @rice.stanford.edu:
Login to rice.stanford.edu:
- ssh <your SUNetID> @rice.stanford.edu
For Windows, you can use SecureCRT,
Cygwin. Make sure you use the binary transfer mode,
as the ASCII transfer mode will damage PDF files!
Under the directory where your zip file is located, type:
You are allowed to submit an assignment a maximum of ten (10)
times. Each submission
will replace the previous.
Since other submission methods are not accepted (such as email), it is important to check early on that you can
use the submit script. Please try this out early and do not try this for the first time at the deadline. If you
are having trouble or something goes wrong, please reach out on
or ask a CA. Do not send us your submission via email.
We give partial credit and so partial work is better than not submitting anything. We will automatically sanity
check your code in some basic test cases, but we may grade your code on additional test cases. It is important to
rigorously check your code yourself.
For the project milestones and reports, make sure only one member
of your group submits
a group submission
on behalf of the entire group on GradeScope
by 11:00 PM (23:00)
. Make sure to include every team member when submitting for the group.
See Gradescope “Create a group assignment”
for any questions.
For the final project, please submit your code (do not include any data files) on rice as a single