In general, assignments are due before class on the due date. The time stamp of the electronic submission is what counts. Paper copies 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, hand in a printout of all of your C program files. At the top of every file you submit should be the following:
/* Name: Your Name(s)
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
- In addition to a paper copy of your code, you must also submit an electronic copy by the deadline. Follow these directions for creating archives for submission:
- Make a new directory for each assignment.
- Go above the directory containing all of the files for the assignment, i.e. if the directory contatining all files has the path /home/dxu/hw1, you should be at /home/dxu. Remember the command pwd tells you what your current working directory is.
- Use the archiving command tar to create an archive of the directory and its files. Using the above example, type the command:
tar cvf hw1.tar hw1
cvf are the arguments of tar, hw1.tar is the name of the tarfile you are creating (must have extension .tar), and hw1 the name of the directory you are tarring. If you have multiple directories, you may list them in turn, they will all be tarred into the archive you named.
- Once an archive is created, you can check what's in it with the command "tar tvf hw1.tar". For more information on tar, man it.
- Prefix your archive with your username, lastname, or anything else that's unique and easily distinguishable. For example, dxu_hw1.tar would be a good name for assignment 1 handin from me.
- When you are satisfied that the archive is complete, compress it using gzip
- Copy the tared and gzipped archive to the submission directory /home/dxu/submissions/cs246.
- Change permission of the submitted file with "chmod go+r hw1.tar".