Guidelines for Completing Assignments

• In general, assignments by 11:59pm on the due date. The time stamp of the electronic submission is what counts. For emergencies and sickness, extensions must be requested as soon as possible.  After the due date, assignments will be assigned late penalties as stated on the syllabus (unless specific arrangements are made in advance).

• For all programming exercises, you must hand in a printout of all of your C/C++ program files.   These 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.
  

• Testing and analysis are important!

• Remember to comment your code.

• You should follow the established coding standards for this course when writing your code.
  

• 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.

• Each file in your submission must include proper header comments (see the coding standards).

• 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

Instructions for Submitting your Assignments Electronically

1. Make a new directory for each assignment, named for the assignment followed by an underscore followed by your username (e.g., hw1_eeaton).  Be sure to follow this pattern exactly.  
2. Put all files for the assignment in this directory.  You may create subdirectories within this directory.
3. Make certain that the directory contains a README (named exactly this way), as described above, that contains instructions for running your program.  The README file should be at the top level of this directory.
   
4. Go above the directory containing all of the files for the assignment.  For example, if the directory containing all files has the path /home/eeaton/cs246/hw1/, you should be at /home/eeaton/cs246/. Remember the command pwd tells you the current working directory.
5. 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_eeaton.tar hw1_eeaton
   cvf are the arguments of tar, hw1_eeaton.tar is the name of the tarfile you are creating (it must have extension .tar and follow the same naming convention), and hw1_eeaton the name of the directory you are tarring.
   
6. Once an archive is created, you can check what's in it with the command "tar tvf hw1_eeaton.tar". For more information on tar, use the man command.
7. Make certain that your tar file follows the naming convention:  assignment name followed by an underscore followed by your username.
8. When you are satisfied that the archive is complete, compress it using gzip. For example, gzip hw1_eeaton.tar
   will produce the file hw1_eeaton.tar.gz
9. Attach the resulting gzip'ed file to an e-mail and send it to me.  Use the following subject (exactly, substituting in your name and the assignment name):  "CS246:  HW1 submission from Eric Eaton".