CS625 Fall 2003, Final Report Instructions

Please read the instructions fully. Please let me know early if there are any issues.

General instructions

• Final report is due Monday, 17 Nov 2003.
• Any unix readable format is acceptable.
• Rough guideline for report size is 8-10 pages. Note that this is a guideline, not a strict rule. But writing too much does not mean that I will read everything :-) So be crisp and concise in what you say. Excess length will displease me :-)
• Do not play font tricks. Make sure the font and spacing are such that the paper is readable (by most people).

What to submit

• For all projects, submit the report.
• For all projects, also submit a "refs.html" which includes HTML links (wherever possible) for the papers you referenced. This is of course optional (or less important) for non-survey projects.
• For projects involving coding/simulation/traces, submit your code and traces too. This will carry substantial weightage. Hence your report itself will carry lesser weightage than the reports of survey projects.
  • Include a top-level README file which describes your directory structure.
  • For traces, please also include a description of what each trace file is, what their contents are, the format of the contents, and such relevant details.
  • Include ONLY relevant traces, and ONLY those which you describe.
  • Comment your code, profusely. I will definitely look at this while evaluating. This is as important if not more, as your report/results.
  • Submit ONLY code which you wrote/modified. The main reason I am saying this is that many of you worked on modifying ns-2, in which case, do not submit the entire ns-2 code. Of course, if you started with some code which I gave you, you can include that as part of your submission. Use your judgement here -- do not submit multiple megabytes of code which you have not written.

How to submit

• Collect your relevant files (report, refs.html, traces, code, README, etc.) under a single directory named "groupXY-final".
• From the parent directory, tar "groupXY-final" and compress it.
• Email this tarred-compressed file to
  
• If this file is too large to be emailed due to valid reasons (the only valid reason I see is that the traces may be too large), then you can exclude ONLY the traces from this tarred-compressed file. For these trace files, you then have one of two options:
  • Make them available in your account (you likely have an account just for the purpose of this course project), and mention where this is available in your relevant README file within the tarred-compressed file you submit by email. Submit ONLY the traces this way, not the code and all that. Make sure the trace files/directories are readable by others, so that I can copy them by logging onto cu2/cu3/cl1.
  • Fix an appointment with one of the TAs, and have them FTP the traces to the course account or something appropriate. Of course, this has to be done before the deadline.
• Make sure that your group number appears in the directory containing the traces too, if you are submitting the traces separately.
• NOTE: ONLY the traces are allowed to be submitted as above. You still have to submit a groupXY-final tarred-compressed by emailing it.