Assignment Turn-In

Table of Contents

• Introdution
• Assignment Turn-In, the Easy Way
• Turn-In Results
• Group Projects
• Assignment Turn-In, the Hard Way

The important thing to recognize about turning in your assignment is that everything is automated, including the determination of when an assignment is turned in late. It's important that you follow the directions given below to make sure your submission is not rejected or delayed. Also, because turn-in is automated, you should feel free to test or submit your code as often as you like.

You may do two things with your assignment: submit it or test it. If you submit your assignment, the code you submit will be the basis for your grade on the assignment. If you test your assignment, the code you test will be deleted after the test is completed. Testing your code is not submitting it; you must explicitly submit your code at least once per assignment.

You may submit your assignment as many times as you want, up until the deadline for that assignment. After the deadline has passed, any further attempts to submit your assignment are rejected (without penalty) and your most recent submission is retained. If you have not submitted your assignment by the deadline, you may make a single submission (with penalty) after the deadline; any further attempts to submit after the deadline are rejected. You may test your assignment as many times as you want, whenever you want.

Your assignment must be sent from your Monmouth University account. The mailbox software uses various utilities to verify your identity (to the extent that your identity can be reliably verified with e-mail), and those utilities are usually unaccessible when e-mail is sent from outside the Monmouth domain. The mailbox software rejects any e-mail sent from an account it doesn't recognize as belonging to a class member.

The easiest way to turn-in your assignment is to use send-files:

/export/opt/cs-537/bin/send-files -an (-t | -s) [ files . . . ]

where n is the number of the assignment you're turning in (1 <= n <= 7).

Give the -t option to indicate you're testing your assignment; otherwise, give the -s option to indicate you're submitting your assignment. You must give one of -t or -s.

[ files . . . ] is an optional list of files. If a list of files is given on the command line, send-files will send all and only those files given. If no list of files is given on the command line, send-files will send all the C++ and include files it finds in the directory in which it was called. send-files assumes any file ending in the extension .cc, .C, .CC, or .cpp to be a C++ file and any file ending in .h to be an include file.

When you list files, you should list files only in the current directory, and you should not list any subdirectories. If you list no files on the command line, send-files sends only the files it finds in the current directory, it will not look in other directories for files.

If you're submitting an assignment, it is unpacked and compiled, and the results are sent back to you as a response. If you're testing an assignment, it is unpacked and compiled, the results are sent back to you as a response, and then your assignment is deleted.

You should receive a response within five minutes after sending your e-mail. If everything goes well, your response should look something like this:

Date: Mon, 22 Jan 2001 16:43:30 -0500 (EST)
From: Richard Clayton 
To: rclayton@monmouth.edu
Subject: Assignment 1 test results.

$ date
Mon Jan 22 16:43:26 EST 2001

$ ls
disable-font.cc

$ g++ -c -ansi -pedantic -Wall disable-font.cc

$ g++ -c -ansi -pedantic -Wall /export/opt/cs-509/pa1/test-df.cc

$ g++ -o test-df disable-font.o test-df.o

$

--

Your e-mail and this reply have been dealt with entirely by software
without human intervention.  You should not assume any person other
than yourself is aware of your e-mail or this reply; in particular, the
person who appears to have sent you this reply is completely unaware of
both your e-mail and this reply.

If you wish, you may do your projects as part of a group of two.

You indicate your group by including a file named "group" in your submission. The group file contains the Monmouth account ids of the members of your group; one of the ids will be yours, the other will be that of your partner. For example, if your account id is s000000 and your partner's is s999999, then the group file will contain

s000000 s999999

Every submission must include a group file; submissions without a group file will be rejected. If you don't want to join a group, the group file you include with your submission will contain only your account id.

Once you submit a group file, you must continue submitting the same group file. If you want to change your group - either by dropping a person, adding a person, or switching a person - you have to let me know so I can reset the group-tracking files.

For two-person groups, either group member may make submissions; if both group members make submissions, the most recent one will be taken as the official submission.

Test e-mail doesn't need a group file, so you may continue to test your code without forming a group. However, once you want to submit, you need to decide on your group.

Assignments are turned in via e-mail, by sending them to the address rclayton@monmouth.edu. The subject line of the e-mail message containing the assignment must have the form

537 assignment no what

where no is either 1 through 7 and what is either test or submit. The mailbox software recognizes and processes only those e-mail messages with subject lines of the form given above; any e-mail message with a subject line not of the form given above is not recognized by the mailbox software and will not be processed.

Send your assignment is with a command line of the form

tar cf - your-files |
uuencode os.tar |
mailx -s '537 assignment 1 submit' rclayton@monmouth.edu

don't forget to put the bar character | at the end of each line as indicated. To test your assignment instead of submitting it, just change submit to test.

On some systems, you may get the error message

uuencode: ISO8859-15 to 646 conversion: Invalid argument

when you send in your code. This error is not fatal, and your code will still be sent.

This page last modified on 10 April 2001.