Exercise #2 - Appeals guidelines
Scripting Class 67557
Spring Semester, 2006
Following is the way to appeal on ex2, emails regarding this exercise will be ignored.
Please only appeal if you have a reason - you lost a lot of points on several errors caused from one mistake.
Don't appeal if you lost a few points on a big mistake
Don't appeal if you lost points on general mistake (you forgot to add the interpreter line in the first line of analyzer.pl, etc.)
To appeal on ex2 you must do as follow:
1) Go over the exercise description and the news-group messages related to that exercsice.
2) Download the test files in: test.tar.
3) Fix analyzer.pl to pass all the tests:
a) I'll not check files that didn't pass ALL the tests (one of them in the case of std).
b) Make sure you use the file you have submitted.
4) Add a NUMBERED comment before EACH line that you changed or added to analyzer.pl.
5) Write a README as follow:
a) First line of the README should be your login
b) Make a paragraph for each mistake you had:
1. Give it a title - mistake can include more then one error in the diff.
2. Write a brief explanation of what it was and how you fixed it - referred to the comments you added in the code.
6) Tar both the README and analyzer.pl into ex2-appeal.tar and submit it via the admin page until 2/6/06 14:00 (Ross closing time).
Before you appeal please note:
1) When appeal, your code will be rechecked - your grade might be lower.
2) Try to make as little changes as you can - I'll diff your code with the original.
3) Write helpful comments and short but understandable README.
4) Even if you have "repeated" mistake it doesn't mean you'll lose only 3 points on it - we'll consider each mistake separately.
5) Your appeal grade is blocked depend on the mistakes you had on your first code. But, in any case it will not exceed 90.
I've notice a few common mistakes:
A) Execution problems:
1. Interpreter problems - wrong path / empty first line - I tryed to fix it when I saw it.
2. Code that run with errors on the command: analyzer.pl his.txt cmd.txt.
B) N/A problem - code that doesn't print N/A when there is a N/A in the requested year or prints N/A even when not needed.
C) Sorting problem - using alphabetical sorting instead of numeric sorting in the MDN command.
D) Searching problem - using search to find the requested NAICS and finding NAICS 425 when 42 is requested.
In any case you think we might have a mistake in our out files:
1) Please recheck yourself since they had been tested several times.
2) Email to sclass@cs.huji.ac.il with the specific command and the output.
The subject of the message should be: "EX2 - output mistake".