Final project information
Final project report
We expect a written report for your project in the style and format of
an ordinary research report. You are encouraged to use a word processing
package with good math typesetting capabilities, e.g. latex, (or word
with MS equation editor (if you can stand the user interface) or Equation
magic). Regradless of what SW you use make sure that your electronic
submissionn is as a postscript file including all fonts, figures etc.
(using dvips if latex, or print to file under windows)
Preview your submision using gv on ohaton to make sure it looks good
and everything is there.
For examples of good reports see the published conference or
journal articles you have been reading for your background studies. As
a guideline we would expect to see
- A cover page with the project title, your name, student id, project abstract
- Introduction with background and motivation given in words.
- Theory
- A succinct description of any math, algorithms or implementation tricks
you are taking from your background reading, including proper citations.
- Any new results (mathematical, algorithmical or implementations) you
have produced, including sufficient derivations and explanations to make
them understandable.
- Experimental results
- Comparisons between different methods (e.g. from published experiments). Explain and motivate observations. Discuss pros and cons.
- Comparisons under different conditions/properties (e.g. matrix fits in
cache v.s. does not fit in cache) and explain it why under certain
circumstance it works better/worse.
- Conclusions. Summarize your results, pros and cons. Comment on their importance.
Suggest possible improvements (future work) or things you might have done
differently should you do it given what you learned in the project.
- Reference list.
Note: Everyone has to write and submit their own individual final report.
Submission
Important: Consider how to structure your material (code, documentation and
data) so it is presentable and attractive. We will expect it to be straightforward
to make and run your code. Because of the varying nature of
the projects there is no one answer to how to submit.
Below are two examples for the projects
we defined:
- Parallel numerical algorithms projects: Organize your files into a
directory from which they can be compiled and test run independently of your
environments. We will expect to be able to do make (for p-threads) or aimk
(for pvm) to make all executables, and get a resulting file, e.g.
eigParallel.mxlnx86 that we can run from matlab. For pvm use
the standard variables for destination directories etc as defined in the
aimk template we gave.
- www-based projects: If you wrote a
java applet intended to be run off the web, put it on your www page
and include a users guide in the report. Still for verification purposes,
submit your code etc using try.
e-submission
tar everything (including the .ps (postscript file) of your report)
into a file called 340_YOURID.tar.gz
tar cvf 340_YOURID.tar [file1] [file2] ...
gzip 340_YOURID.tar
try c340 report 340_YOURID.tar.gz
here YOURID should be replaced by your actual unix login
Paper submission of report
A hard copy is mandatory . ( We will not take the responsibility to search the repository for your report)
Print quota
hints to upgrade your printing quota: 1/ go see the lad admin in person. and explain to them.
2/ cameron basement 5c/page
3/ university printer 11c/page