Marking guide (prepared by TAs under Professor's guidance)
=============

This guide describes more details on the marking criteria,
used by all TAs when marking your assignment.

--------------------
For the Programming Problem: (Only some serious common errors are listed)

1.  No Upper and lower case change during comparisom  -5

2.  Find the # of hits incorrectly -5

3 Result not Sort (Not code for sort found at all) -8

4 Sort impropertly. -6/-4/-2 dependent on effort made

5  Words in <...> are not propertly skiped -5
   If no logic for doing that is incorporated -10. 

* The above marking guidance are for those whose program compiles and do not crash.

For those who can not compile, only half of the mark be deduced, 2.5 instead of
5, 4 instead of 8 etc.), but this will be marked out of a maximum of 40 marks.

For those who submit a disk failing to read files from, remarking is possible
if resubmit your disk (see note below).

--------------------

For the 2nd and the 3rd questions:

1. The rounded result will be considered correct, eg. 57.87 to be written as 58 
etc.

2. For the problem of 2.3, several steps are involved, marks are awarded 
depending on how far on the road you go    1/2/3/4

3. For the problem 3.1, if the final answer is not an integer(2.53 instead of 
   3), 1 mark will be deducted. 

==============================================================================
A note by your professor:

LOW MARKING FOR WORKING PROGRAM ?

If you got "0" this is because your program has been
found to be the same or extremely similar to another 
student's program. Please, read the policy on plagiarism
again. You may see the professor on her scheduled office
hours after the study break.

If got a low mark under 40/80 on your program,
this is probably due to one of two reasons:
  1) impossibility of testing your program;
  2) compilation or run-time error during testing.

1) Impossibility of testing:
The most common reasons for these are:
* missing one or more files from the disk
  (we need a1.cpp, htmldoc.cpp, htmldoc.h)
* disk error

2) Compilation or run-time error
The possible reasons are:
* there is really a compilation or run-time error
* your program cannot be compiled on the CUBE
  under Microsoft Visual C++
* the marker made a mistake when trying to 
  compile your program, mistakenly thinking
  it was not possible to compile it.


If you are in this situation, but believe your code
compiles and runs without crashing, please
do the following steps:
1) get your assignment (at an office hour or at the
   tuesday lecture after the reading week)
2) verify if the reason given by the TA is
   correct by taking the disk that you have submitted
   to the CUBE and trying to compile and run.
3) prepare a remarking request (form available
   under policy on remarking);
   specify the terms of the re-marking, such as:
   (a) I tested my disk at the CUBE and it works fine
   (b) My disk has a failure, or there were missing
       files on it. I'm re-submitting a new disk.
       Note: in this case, your hardcopy has been
       photocopied by the TAs and will be compared
       to the newly submitted files. A penalty of
       up to -4 marks may be applied for not following 
       the standards of submitting all files, but the
       assignment will be re-marked out of "80" again.
4) submit your remarking request plus the assignment
   in one of two ways:
   * at the office hour your marker is holding next
     week. See marker's name at the top of marking
     grid page. See their office hours at the web
     page under "Office hours with markers". In this
     case, you may not need the remarking form.
   * to your professor (in her office hours, lecture,
     or slip under her office door): this is just
     a "drop off"; you don't need to discuss the terms
     with your professor.

Note: remarking requests may be submitted for other
reasons as well; but specific reasons should all
be submitted in writing.
Do not try to discuss remarking issues with your professor 
or your lab TA. The current process of re-submission
is effective and works well.
============================================================