Using Turnin

Submission
Use the command turnin to submit your project. Its usage is:
turnin -submit <grader> <project-name> <file1>  <file2>...

For this course the grader is stanv.
You will use standard project names of the following form for every project where you have to use turnin: project1 for the first project, project2 for the second project, etc.

Whenever you submit a file, it gets timestamped. These timestamps are used to determine whether the project is on time or not.

Confirmation
You can see whether the submission was successful or not by giving the command:
turnin -list <grader>  <project-name>
This should show the list of files that got submitted.

Example
If you want to submit the files: README, Timer.h, Date.h, main.c, main.in and  main.out for the assignment project1 and grader stanv then give the following command:

turnin -submit stanv project1 README Timer.h Date.h main.c main.in main.out

Note that each file in the list can be either an ordinary file or a directory.

You need not submit the files all at once; you may use the command repeatedly to submit different files.

Then to confirm, type:
turnin -list stanv project1

Caution
If you submit a file a second time, then the previous file and its time stamp will get over-written.
Once submitted, you can't undo your submission (although you can overwrite any file).

More Information

Type "man turnin" on any department Unix machine (press space to move forward and q to quit).

Late update from TA

Your program should compile and run on the Taylor basement "linuxghibli" machines (because that's where it will be graded). Once you have verified this, submit the following files:

That is, you should submit all the files necessary to compile your code as well as a plain text README file with the following:
  1. Your name
  2. Instructions to compile your code
  3. A clear list of all the extra credit features you implemented (so I don't miss them when grading)
  4. Any other comments (optional)
To save me the trouble of typing one extra command, I would prefer if you did not submit all your files in one tarball. The compilation instructions should be simple. For example, if all your code is in a file called 'sponge.c', then the instructions could simply be "cc -o sponge -I/lusr/include/X11/GL -I/lusr/include/X11 -L/lusr/lib/X11 -lglut sponge.c". Or, if you built your project with a Makefile, then you should submit the Makefile along with your code and then the compilation instructions would simply be "make".


Last modified: 02/03/09 by Don Fussell fussell@cs.utexas.edu