6.851: Advanced Data Structures (Fall'17)
Prof. Erik Demaine
TAs: Adam Hesterberg, Jayson Lynch
[Home] [Lectures]
[Problem Sets] [Project]
[Coauthor]
[Accessibility]
Policies
- There will be a weekly one-page problem set, up to 10
problem sets in total.
- Late policy. You can request an extension of up to two days on any problem set by emailing your issue (heavy workload, travel, sickness, hangover, etc.) to 6.851-extensions@mit.edu before the problem set is due; reasonable such extension requests will be approved. You can request further extensions by emailing 6.851-extensions@mit.edu and committing to not looking at the released solutions, and problem sets extended beyond two days have a maximum score of 50% and aren't guaranteed feedback from the graders. Exceptions to this (extensions granted after the deadline or extensions of more than two days without penalty) require a note from a dean.
- Collaboration policy. You may discuss assigned problems with other students, but must write your solution individually. You must wait at least an hour and do something unrelated to the problem set between working with others and writing up your answer. You must also begin thinking about each problem on your own before discussing with others.
Be sure to cite all collaborators and any sources you use. Avoid reading sources that solve the problem, but if you accidentally do, cite that source.
- Format. The answers must be typeset in LaTeX,
e.g., starting from this template.
Each answer must fit in one page,
or your solution will not be read.
Use at least 10 pt font and 1 inch margins.
This rule is meant to prepare you for writing research publications:
one often has to explain great ideas in a very limited number of pages.
Solutions do not need to include all calculations, trivial details, etc.
Just prove to us that you found the solution, and that you understand it well.
- If you are not familiar with LaTeX, start with this
good introduction. You need to know very little to start
writing problem sets in LaTeX: just skim through the mathematics
section in the introduction, and download the template. On Athena, you can compile
with latex and view the resulting DVI files with
xdvi (which will refresh automatically when you
recompile). When you're ready to submit, compile with
pdflatex and submit the PDF.
- Gradescope. Submissions must made through
the class Gradescope page
and consist of a compiled PDF document.
Grades and comments will be posted to Gradescope.
- Problems will be graded on a 0-2 scale:
- 0 =
You didn't get it. Filling one page to the brim does not mean you can't get
zero. Please don't write stuff you know is wrong.
- 1 =
Your solution was ultimately a good one, but the write-up contained significant
errors or omissions.
- 2 = (We think) you got it.
- Due dates are generally at 12:00 PM on the specified day (typically the Wednesday after it is assigned).
Problem Sets
Release |
Due date |
Problem Set |
Solutions |
September 6, 2017
| September 13, 2017
| PS1
| Solutions
|
September 13, 2017
| September 20, 2017
| PS2
| Solutions
|
September 20, 2017
| September 27, 2017
| PS3
| Solutions
|
September 27, 2017
| October 4, 2017
| PS4
| Solutions
|
October 4, 2017
| October 11, 2017
| PS5
| Solutions
|
October 11, 2017
| October 18, 2017
| PS6
| Solutions
|
October 18, 2017
| October 25, 2017
| PS7: Project Proposal
|
|
November 1, 2017
| November 8, 2017
| PS8: Project Status
|
|
November 8, 2017
| November 15, 2017
| PS9: Project Status
|
|
November 15, 2017
| November 29, 2017
| PS10: Project Slide
|
|