Assignment Turn-In

Computer Algorithms I, Fall 2003

Introduction
Assignment Turn-In
Turn-In Results
Points to Remember

Introduction

It is important to understand that everything involved with turning in your assignment is handled by software, including determining when an assignment is turned in late. It's important that you follow the directions given below to make sure your assignment is not rejected or delayed. Because turn-in is automated, you should feel free to turn-in your code as often as you like.

Turning in your assignment involves doing one of two things with it: submitting it or testing 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 assignment submitted 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 turned-in 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.

Assignment Turn-In

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

/export/home/class/cs-305/bin/send-files ( -a)n (-t | -s) [ files . . . ]

where n is the number of the assignment you're turning in (1 <= n <= 5). send-files should be available on any of the CS department's Solaris or Linux machines.

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 on the command line, you should list only those file found in the current directory; you should not list files found in subdirectories or the parent directory of the current directory.

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. Also, send-files will send all files it finds, so make sure the current directory contains only the files you want to send.

The five-minute response time only applies to your Monmouth University mailbox. If you forward your mail somewhere outside Monmouth, such as to Hotmail or Yahoo!, no response-time guarantees can be made, and it can take arbitrarily long to get your reply.

Turn-In Results

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:

From: rclayton@monmouth.edu
Date: Wed, 5 Sep 2001 11:35:34 -0400 (EDT)
To: rclayton@monmouth.edu
Subject: Assignment 1 submit results.

$ date
Wed Sep  5 11:35:26 EDT 2001

$ ls
main.cc
tuple.cc
tuple.h

$ g++ -g -c -ansi -pedantic -Wall main.cc

$ g++ -g -c -ansi -pedantic -Wall tuple.cc

$ g++ -g -o count-tuples  main.o tuple.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.

Points to Remember

Wait until you get the reply from the previous turn-in attempt before trying another turn-in attempt. Each turn-in attempt is handled independently from, and concurrently with, all other turn-in attempts. If you turn-in assignments two or more times without getting a reply from any of them, you'll have two or more assignments competing to be accepted, which is probably not what you want.
For example, if you submit an assignment and realize you've made a mistake, you should wait until you get a reply from your first, incorrect submission before you try a second, correct submission. If you immediately re-submit your assignment again without waiting until you get a reply from your first submission, your two assignments will be competing to be accepted by the turn-in software, and there is no guarantee which assignment will be accepted.
Date: Thu, 30 Oct 2003 20:52:44 -0500 (EST) Subject: Submitted files From: s0------@monmouth.edu To: rclayton@monmouth.edu
When I submitted my files today I first accidentally submitted files in the wrong directory. I then resubmitted with the correct files. I received the email for the first submission after I received the email for the second one. I would like to make sure that the second submission was the one that was officially submitted at the deadline.
Unfortunately, the first incorrect assignment was the one that the turn-in software accepted, causing this student to fail the assignment.
Submissions are destructive. Each assignment you submit unconditionally and completely replaces the previous submission, if any. If you submit a broken assignment, it will be accepted and will replace the previously submitted assignment.
Testing an assignment has no effect on the assignment that's been submitted, if any.
Keep the reply. The reply from your turn-in is your receipt; keep it. If there's any question about your assignment and you don't have the most recent reply, you're pretty much out of luck.
Don't fool around with the deadline. The clocks on the various CS lab machines are not well synchronized, and the clock on the machine receiving your turn-in is the only one that counts. Even though the clock on your machine shows 1:58 p.m., you may have already missed the deadline. Turn-in early and often.
The code you submit is the code that gets graded. You code is tested as submitted; I will not patch, replace, or change any software submitted to fix last-minute errors. I will not reset the deadline so you can submit an improved version of your code after the deadline. It is your responsibility to submit working code by the deadline.
This page last modified on 3 November 2003.

Assignment Turn-In

Computer Algorithms I, Fall 2003

Table of Contents

Introduction

Assignment Turn-In

Turn-In Results

Points to Remember