Assignments
In
general, assignments are due electronically by 11:59:59 PM on the due date. The time
stamp of the electronic submission is what counts. Paper copies are
typically not needed. But, in case a paper copy is required, it may be handed in later during the next class. The deadline for paper copy submission is not strict, but must be submitted with in 3 days of the actual deadline, or late penalties will also be assessed. For emergencies and sickness, extensions must be requested as soon as possible.
Rules for handing in assignments:
- Testing and analysis are important.
- Remember to comment your code.
- After the due date, assignments will be assigned late penalties (unless specific arrangements are made).
- On any assignment, if you hand in something that is not working correctly, an accurate description of the problem and suggestions about possible causes will be worth (max) 50% of a correctly working program. For example, if the assignment does not work correctly and would have received a grade of 70, a good analysis of the problem and possible solutions could receive 15 points, thereby raising the grade to 85.
- For
all programming exercises, you should have a mercurial repository in
a directory with the name of the exercise. For instance the repository hw1 should
be in /rd/cs246s2016/${USER}/hw1
At the top of every file you submit should be the following:
/* Name: Your Name(s)
Exercise: Exercise#
Date: Date assigned
Purpose: A short description of the program/file/exercise.
*/ |
- For all programming exercises, you must also include a README, which is a text file containing things you'd like me know about the project, such as:
- how to compile and run it, if different from the standard requirements
- any known bugs and what you think the causes are (or what you did to debug it, etc)
- if your program behaves differently from the requirements, where and how
- any features you implemented in addition
- anything else you would like to point my attention to
- You
must submit an electronic copy by the deadline. Follow these
directions for creating a repository for submission:
- Before starting the assignment, make a new directory
for the assignment repository in /rd/cs246s2016/${USER}/<assigmentname>
- Initialize the repository using hg init
- Clone the repository in your local CS246 directory.
- As you work, make sure you add new files and commit
them often, so that you have a backup.
- For additional peace of mind, push your repository
after committing so that both repositories are in sync.
- When you have finished your assignment, make sure that
you commit and push all of your files.
Last modified: Wed Jan 27 00:02:40 EST 2016