Turning in Code

Your assignments will be submitted electronically. They will be graded and returned to you electronically, also. Comments, including your grade, will be added to the code before it is mailed back.

Late assignments will get a zero. You can, if you wish, submit it anyway and we'll look at it. It will still be a zero. Unless Kurt grants you an extension , it is late. [ NOTE: The TAs don't grant extensions. ]

The 8:00 a.m. deadline is so that you don't have to deal with the overloaded modem pool at midnight. Waiting until 7:45 a.m. to finish your assignment is probably not a good idea. The prudent approach would be to finish as far before midnight as possible. This leaves you 8 hours within which to submit. :-)

Steps To Submit an Assignment

  1. Test your code!!!!
  2. Log into the OIT machine sundial.
  3. Place your solution into one file. [ For example, foo.lisp ]
  4. In the same directory as the file, type: 
    	~cs2360/bin/turnin  Xy  foo.lisp  firstName lastName
    Where X is the assignment number. And y is your section letter. Example for assgnment 1.
  5. The turnin program will tell you the submittal time and how big the submitted text is. If the size does not match then try again. ( ls -l foo.lisp will tell you the size of the file.) If this is a resubmittal, the program will ask for you to confirm that you want to trash your previous submittal.
  6. If the turnin program results in an error. Email lyman@cc. I'll need to know exactly what he error message said.

Notes:

1. NOTE: if you uploaded your text file from MS-DOS/Windows convert it to Unix format. See the dos2unix man page. From the Macintosh, Fetch ( or NCSA Telnet ) does this automagically for you. If transfering from a PC/Mac within a windowing environment, do not cut and paste your text into a terminal session window that is connected to an OIT machine. This is not a reliable method of transfering text. [ Especially, when you have 1 minute till the submission deadline. ]

Regardless of where the code was developed, load your uploaded files into LCL on an OIT machine ( after any transfer if neccessary ) to confirm that they work. Files that don't even load into a Lisp Enivornment will be be penalized. You are responsible for submitting code that does not invoke the debugger. In other words it should work and you should test that it works.

All functions that are not fully working should be block commented out. Your file's introductory comments should contain comments to the TA about what is and is not working.

2. For most you can do this on acme or on the baird cluster too. However, for a small percentage of people the program will not work correctly on acme. [ Due to mysterious reasons. ]. The machine that seems to give the least headaches is sundial.

4. If you type: 

	~cs2360/bin/turnin
with no arguments. You will be presented with the proper argument usage.

On acme the program is invoked like so: 

	~cs2360/bin/acme/turnin ....
On the baird cluster the sundial version should work.

The FirstName LastName should be your first and last name. the first name can be your preferred first name if you wish.

5. If the program states that you submitted at such and so a time, then your program was submitted. The program doesn't produce that message until after the copy has been made.

Dribble File

The end of your submission should contain the results of a dribble file that demonstrates a minimal amount of testing. For each function required by the assignment there should be an invocation ( or two ) of said function and the answer lisp returned. See the assignment text for examples.

This serves two purposes. First, it demonstrates to your TA that you actually did step 1 above. Or at least the bare minimal attempt at it. Second, at least you'll have a minimal of evidence that it was "working before, honest".

Your TA will use a testing harness to test functions in question so they should compily with the specifications. The harness can invoke dozens of examples and not get tired. Our test inputs are often chosen to identify functions not in compliance with the specifications.

Creating a dribble file is essentially recording a session between you and the Listener. You can start a dribble file by typing: 

	 ? (dribble "testing.txt" )
	    Dribbling to file "testing.txt"
	 ? ( + 1 2 )
	  3 
	 ? ( dribble )
	  T
	 ?
Invocating the function the first time started the recording the second stops it. Everything inbetween is recorded into the specified file.

The template file provided in, ~cs2360/public/template.lisp , contains a block comment at the end. 

	#|
	   dribbled text goes here..
	|#
The dribbled text should go there.

If you are using a GUI environment like MCL then you can simply do a cut-and-paste from the Listener directly into your file.

Turn around time

The plan is to get the homeworks back to you before the next one is due. Notice, that this could mean that the homework can come back the day before or the day of the next due date. Sending your friendly TA asking when it will be back before the week is up won't get it graded any faster.

Solutions should roll out now later than 48 hrs after the due time. Or later if someone has a valid extentsion from Kurt.

Back to Fall 2360 Home Page
Last modified: by Lyman S. Taylor(lyman@cc.gatech.edu)
(c) copyright Lyman S. Taylor 1995, All rights reserved