Revised 9 May 2005:

Dear Students,

Here is the checklist for your project. 
(Substitute your name for "ivanhoe" and the name of your project for "foo".)

1. Public demonstration of your project at the scheduled time.

2. In  u00: /usr/local/illimath/ivanhoe/ put an indentifiable and 
   completely recompilable/executable copy of your project. Umask 002.  

3. Update and finish your webpages on 
   premium: /afs/ncsa/projects/MATH198/public_html/ivanhoe/
   
4. Paper documentation with a cover sheet that shows your name, date,
   short and long title, name of executable, if different. 
   An ascii (text) file of your narrative and operating instructions in 
   illimath/ivanhoe.

5. Return the key to the grafiXlab to me. I will cancel it in the Math Dept.
   (Return your Beckman keycard to the NCSA where you picked it up to get
   your ten dollars back.)

Here are the principles from which the above requirements follow, and on
which basis the requirements can be ammended.

1. Several people need to see your project presentation.  
   If something goes wrong with your software, we will split the public 
   presentation from a (private) demo of you program(s) later.

2. I need to have some recompilable version of your source code. 
  If it is in Python be sure it runs on the Linuxes in ah110. 
  If it's in Unix, then this should compile on the REL machines. 

(2b) If your code only compiles in Windows, then I need a copy of the code 
  and instructions for recompiling it (e.g. makefiles). A good idea is zip 
   up your entire project, including foo.exe,  and put ivanhoe.zip is into 
   MATH198/public_html/ivanhoe/. That way I can download it from the web to
   a convenient pc and (a) run your program, and (b) recompile it 
   (if VC++ is present.)

3. If your documentation consists of .html files in MATH198/public_html/ivanhoe/
   and you printed these out from the web, then you've completed 2. 
   You'll still have to hand annotate the printout of the source code. 
   For details on the documentation, see the cover sheet. If your 
   documentation is non.ascii, e.g. an MS-Word file, then make an ascii 
   copy of it. The purpose of this is to be able to reprint the documentation, 
   or to extract paragraphs. 

4. If you have reasons for keeping the key, or keycard. Check with me. If I 
   don't recover the keys, we'll have to rekey the grafiXlab.