The handin Command


Solutions to programming assignments should be submitted electronically using the handin command. The syntax of the handin command is as follows:

handin.course-number.section-number assignment-number filelist

where

course-number is the number of the course (111)
section-number is the number of your section
assignment-number is the number of the programming assignment
filelist is a list of the files to be handed in

For example, a student in 111 section 2 could hand in files Asg3.cpp and doc.txt for assignment 3 with the command

     handin.111.2  3  Asg3.cpp doc.txt
Note that the complete command name in this example is handin.111.2, so it can contain no blanks. Wild cards in file names are allowed, but directory names are not. Thus all files in the current directory could be handed in for assignment 3 in section 1 of CpSc 111 using the command
     handin.111.1  3  *
but not
     handin.111.1  3  .
As an additional example, all files ending in .cpp or .txt in the current directory could be handed in by
     handin.111.1  3  *.cpp  *.txt
Notes:

  1. Be sure to submit all the source files needed to compile and run your program using the javac compiler. You can also include test data that you used, if appropriate.

  2. Do not submit .class files or source files that will be provided (specified in the assignment instructions).

  3. If the handin command works successfully, it will list the number of bytes transferred for each file handed in.

  4. You can resubmit files or submit additional files by using the handin command again. Existing files (with the same name) handed in again will be overwritten. To delete a previously handed-in file that is not to be replaced, or to make other corrections, send email to your instructor or lab instructor.

  5. It may be helpful for you to submit a .txt file including documentation about the status of the program (what works and what doesn't) or other information about your program.

  6. Be very careful to hand in all of the files needed for your program, and test your program using the exact same files that you hand in. Always retest the program after making any change (including comments), and after transferring a file from one system to another.

  7. To avoid confusion between the section number and assignment number, you should set up an alias for the handin command for your section. This can be done by placing an alias command such as
              alias handin handin.111.1
    
    (for CpSc 111 Section 1) into your .alias or .cshrc file. After doing this, you can handin files with a command such as
              handin  3  *.cpp
    
    (This command would submit files *.cpp for assignment 3 in the course and section specified in your handin alias.) Note that the alias command will not become effective until the next time that you log in or open a window, unless you use the source command to activate the alias. Also note that you can use any name that you wish for the alias, such as hi, hi111, or 111hi.