Turn-In
Students in 6.170 are required to submit the implementation parts of their exercises electronically as well as in hardcopy. Electronic submissions are collected and are a vital part of the grading process. Therefore, it is imperative that you use the tools that we have provided to make this task straightforward.
- turnin6170
- This program packages the student's implementation for submission. Students can run it as often as they wish until the exercise is due. When the exercise is due, the TAs will run a program that fetches all the students' implementations.
turnin6170
turnin6170 packages a student's exercise files for submission. It is called from the Athena command line and takes only the exercise name as an argument:
turnin6170 exN
exN is one of ex1, ex2, etc.
The files and subdirectories specified in the student's ~/6.170/exN directory are packaged, zipped, and stored in the file ~/6.170/exN-turnin.tar.gz. When exN is due, the TAs copy each student's turnin package and use their contents for autograding.
Hardcopy Submissions
We also require that you submit a hardcopy of your problem set for your TA to grade. Hardcopies of problem sets must be turned into James Steere, the course administrator, by 4:05 on the day which it is due; No exceptions.
As a general guide for what to submit, any source code which you have modified or created should be handed in. Additionally, any design or summary documents should also be printed and handed in. You do not need to (and should not) hand in source files which were provided for you and you have not modified.
You should find the enscript command to be useful. A nice way to format source code files is:
enscript -2r *.java
This will save paper and produce easier-to-read output.