Electronic Submission Guidelines - CSCI 200L, Fall 2011


Electronic Submission Guidelines - CSCI 200L, Fall 2011

The first three homework assignments are meant to be completed individually by students on their own time. Assignments must be submitted using the `submit` program on `aludra/nunki`. Please see the Submission section of each homework assignment regarding what commandline arguments you should use when you run the `submit` program (each assignment is slightly different). The `submit` will timestamp what you have submitted and that's the time we will use to determine if your submission is late or not (and apply the penalty if it was late). If for some reasons you cannot login to `aludra/nunki` to run the `submit` program, as a last resort, you can e-mail the instructor and include all the submission files as an e-mail attachment. Please also include an explanation why you are doing this instead of logging into `aludra/nunki`. You can also `zip` all your submission files together and just send one attachment (but please do not use `rar` - `rar` files will not be accepted). In this case, the timestamp for the submission will be the time the e-mail arrive at the instructor's gmail account and not the sending time of your e-mail (since that can be easily forged). Therefore, if you do this, you will be doing this at your own risk! We will not be responsible if the Internet decides to take a very long time to deliver your e-mail. For the rest of the homework assignments, you will be using `subversion` to manage your submission. Please make sure you attend the joint classes with CS 201 to learn the requirements.

Verify Your Submission
After you submitted your assignment, you should verify what you've submitted can be compiled as is on `aludra.usc.edu/nunki.usc.edu`. The most difficult thing is to figure out exactly what you have submitted. Therefore, we suggest that you create an empty temporary directory (we will use `xyzzy` as an example), copy all your source and documentation files into it, change directory into it, submit all the files in it, verify what you have submitted, and delete this temporary directory. Below, we will use `hw1` as an example and assume that all your files are in your `~/hw1` directory). You should change `hw1` to the appropriate name for your assignments. `cd ~/hw1` `mkdir xyzzy` `cp .java COMPILE.TXT xyzzy` `[ copy other files you want to submit into xyzzy ]` `cd xyzzy` `[ run the corresponding submit command from the spec ]` `[ compile your source code according to your COMPILE.TXT file ]` `[ test your code ]` `[ if something is wrong, don't fix it here, fix it in ~/hw1 ]` `cd ..` `rm -rf xyzzy` Before you run the `mkdir`* command, make sure you don't have the `xyzzy` directory. If you do, empty it and delete it before you proceed. A few things to note: If by following the instruction in your `"COMPILE.TXT"` file failed to create your program, the TA will try different procedures to get your program to compile and will deduct up to 10% of the grade depending on how difficult it is to get your program to compile. If your program cannot be compiled because you forgot to include a file in your submission, we will not be allowed to take a file after the submission deadline and you will receive a score of zero. If the above failure occurs, you must recreate your submission and submit again and verify again. Please remember that, if you forget to submit a file, we cannot accept a file after the submission deadline (no matter what the file timestamp is on `aludra/nunki` or on your personal machine) and your assignment most likely will end up with a score of zero.