Project Submission Information for CS 371R:
Information Retrieval and Web Search
- Projects should be completed independently by each student.
No collaboration beyond general discussion of the project requirements is
permitted.
- Projects are due 30 minutes before the start of class on the due date. Be
sure to hand in assignments on time, late penalties are a loss of a percentage
of the original overall points for the assignment: 1 Day: 15%, 2 Days: 40%; 3
Days: 75%; past 3 days: 100%. A day is a 24 hour period starting 30 minutes
before the beginning of class and includes all weekend days and holidays.
- Submit all code to the TA electronically using turnin. Submit a directory with all code and
supporting documents.
- The submission directory should include the following:
- All new or modified java code. Ideally, your solution should be
contained within the classes you wrote and does not modify
the IR package. The code
should also be properly commented using Javadoc convention.
- A short document (1-2 pages) clearly describing in well-written
English prose, the approach taken to the assignment, the general algorithm
employed, clear instructions on running the system, and insightful
discussion of any experimental results obtained. This document should be
called "REPORT" and may be HTML or PDF (with an appropriate
file name extension, e.g. "REPORT.html")
- An ASCII file called soln-trace which is a detailed trace of
your
program running on any sample test problems. The traces can be generated
using the Unix command script (call "man script" for documentation).
To use script to collect traces, do the following:
-
Type "script soln-trace" at the command line.
-
Run the program on different test cases, as you would have
normally done.
-
When you want to stop collecting traces, type "Control-D" at
the prompt.
-
The trace of your run is stored in the local file "soln-trace".
The script command captures everything printed on the
terminal, including non-printing characters like carriage returns
(^M) and backspaces (^H). So when you edit the trace
with a text editor, it may look funny. If the extra control characters
do not affect readability of the trace, then you may submit the trace as
it is. However, if the trace looks messy, then please re-run your
program and create a new trace.