The semester project should develop as the course does. I want to periodically check the progress for your group. To accomplish this, turn in a copy of your code (and other relevant files) by the end of the week for every other week of the semester. Only one copy of the code needs to be turned in, but everyone is responsible for making sure that your group turns in the update.
The purpose of this exercise is to track your work over the remainder of the semester. It will not be graded, but it will be checked. That is, failure to complete this exercise will count against your project's grade.
You should include all of your current program files. Also include a simple, README file (in plain text) documenting what the files are. Include any compilation commands (or makefiles) that are needed. It is expected that you will turn in the same programs again and again, as you iteratively expand and refine them.
To turn in your group's files, there are two utilities to use.
The first is the tar command, which combines several different
files into one. You do not need to use this if your program only has one
file. Below is an example of the tar command.
It is a good idea to call your file something unique, like
"projectN.tar", where N is the group's number.
The group numbers can be found on this link.
tar cvf
filetocreate.tar file1 file2 ...
The second utility is a program called update_project,
a program written specfically to allow you to turn in a file
electronically. It is available on Qubit. It will copy the file
to the professor's account.
/home/cscmcw/update_project projectN.tar
Click here to see an example log.
Keep a log of turning in the updates, in case there is
a problem.