Please substitute your netid for each occurrence of "ivanho2".
Your project is incomplete unless all of the following requirements are met.
1. Well prepared, 20 minute public demonstration of your project at the scheduled time. Invite your friends.
2. Webpage for your project class198f14/ivanho2/public_html/index.html with all dependencies in the public_html/ directory.
3. Project repository in class198f14/ivanho2/project/ containing
Compiled RTICA of your project.
Documentation of how to operate your RTICA (which Python library?)
Source code, with makefiles for recompiling your project.
Documentation for how to recompile your project.
4. Project documentation in class198f11/ivanho2/public/documents containing
LaTeX source .tex with figures, if any.
LaTeX .pdf of your documentation.
5. Hard copy of 4. plus a hand annotated printout of your RTICA code.
6. Cover sheet for the hard copy document.
In the foyer of your project (i.e. in class198f14/ivanho2/), but not in the public_html/ (unless it is linked into your index.html), place copies of all the work you did for the course, such as any esperiments in DPgraph, Vpython, PyOGL, Turtlegraphics, Javascript and any reports, papers you presented to the class. You do not have to link all of this into your webpage. But I and your mentors will look and evaluate it.
Remember that only ivanhoe/public_html will be reachable from the web. A copy separate from the repository of this folder will be published on the web.
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 your programs later.
2. I need to have some recompilable version of your source code. If it’s in Unix, then this must compile on the grafixLab macs. If your code compiles only in Windows, then I need a copy of the code and instructions for recompiling it. I should compile in Cygwin on the grafiXlab pc hickory.math.uiuc.edu. If it is in Javascript, then the .html has to run on Firefox from every platform (windows, mac, linux).
3. An (even minimally) documented collection of your work could be of immense value to some future MA198/CS1988 student (and to me). So please, no false modesty here. Remember "content trumps format".
4. A LaTeX document always looks good, and makes fine printouts. But if you’re running short of time, and your .html files already have all the information, then just print out the .html files and submit them as hard copy here. If you’ve learned to use the Pudding, then you can edit your .tex code into the .html file and your formulas will look really professional.
5. The hand annotated printout of your project is invaluable if I or some future student needs to understand your code. Please don’t waste time to prettify your code. The hand annotation is much more valuable. And MA198 is not a CS course. You will never be criticized for writing ugly code, just if you write ugly math.
6. See the two cover sheets, one for a draft (if you want feedback), one for the final (you’ll earn what you reap there).
7. Finally, a word about grades. You have contracted for a product, your project with all of its parts. That is worth an A. If some or all of your project is really superior, you’ll get an A+, which shows up on your transcript but doesn’t count more than an A in the GPA. If you fall short in one or another aspect of the project, but it is materially finished, then you’ve earned an A-. In all other cases, you have an "incomplete". In that case, see (8).
8. In "real-life", delays in project completions, and extensions are very common. The University does doesn’t believe in this. So, my policy is to give a grade commensurate with what you have accomplished in this course, usually some kind of B. This grade, whenever you have finished your project and submitted it in the form contracted for, will be upgraded.