Home |
Staff and Sections |
Course Materials |
Resources on the Web
General Information for Computer Science 175
lib175
If you have a question, email us at lib175@fas.harvard.edu. Please do not hesitate to email.
Instructions for Submitting
How to submit your assignments:
- Log into nice.harvard.edu
- change directories to the directory containing the files to submit
- type "submit lib175 1 `pwd`" without the quotation marks
(replace 1 with the current assignment number)
Important: the characters surrounding pwd are BACKTICKS (under Esc),
not apostrophes. The general usage for the submit script is:
submit [course] [assignment number] [directory containing your files]
The directory must be specified as an absolute path and subdirectories
will be submitted as well. To avoid writing absolute paths, you can
invoke the pwd command as above.
For an example not using pwd, "submit lib175 3 ~/src/asst3",
without
the quotations marks would submit code in absolute path ~/src/asst3 as
your assignment
3.
When submitting, the directory you submit should contain all your source code (*.c, *.h), the Makefile(s) to build your assignment, a README file, and all relevant image and data files (if any). Points will be deducted if the README file (or any other required file) is missing.
Generic Source Code Requirements
In your programming assignments, you are expected to write well-documented and readable code. There is no single right way to organize and document your code and it is not our intent to dictate a particular coding style for this class (we leave that to the good people at Computer Science 50). However, try to follow the following generic guidelines: (1) use descriptive names for variables and procedures; (2) be consistent with indentation; (3) comment! Your comments should not be superfluous (e.g., "here, we add one to the variable counter"), rather they should describe the programmer's intent (e.g., "increment counter to prepare for the next edge of the triangle"). We do read the code!
README requirements
The README file is a crucial part of your assignment. As mentioned above, you will lose points if the README file does not exist among the files you submit. Please take 5 minutes after you complete the assignment and carefully answer all the items below.
- List of all files you submitted.
- Note the platform you used for development (Windows, Mac, Science Center linux, ...)
- Provide instructions on how to compile and run your code, especially if you used a nonstandard Makefile, or you are one of those hackers who insists on doing things differently.
- Indicate if you met all problem set requirements (more importantly, let us know where your bugs are and what you did to try to eliminate the bugs; we want to give you as much partial credit as we can).
- Provide some overview of the code design. Don't go into details; just give us the big picture.
- Let us know how to run the program; what are the hot keys, mouse button usage, and so on? Describe steps or sequences of steps the TF should take to test and evaluate your code (especially if your implmenentation strays from the assignment specification).
- Finally, did you implement anything above and beyond the problem set? If so, document it in order for the TFs to test it and evaluate it.
Grading Policy
Check the course syllabus for details.
The staff is here to help you. Email us for help and answers to your questions.