|
Tips on how you can judge your programming contest
The judging criteria for contests varies from school to school, often depending on the number of students participating. Generally, the more students who participate, the more judges and larger the facility required. Therefore, high school competitions that require large judging panels are frequently held within universities. This often applies to competitions where more than one school is involved.
The judging rules below are an example of how you can run your own contest.
Judging within your own high school (up to 20 students)
- You may choose to have judged runs or not. If there are less than 5 teams competing, you can simply allow them to submit all of their answers at a certain time and judge them all at once.
- You may also choose to judge only those programs that function (unless there are none).
- See below for more information on judged runs.
Judging in a college/university (20+ students)
- A panel of judges would be useful to execute programs during judged runs so that the time taken to judge the entry would be minimal.
- See below for more information on judged runs.
Judged Runs
A judged run consists of the contest judges executing a program using the official contest judging data criteria. When a team is ready to have a program judged, they must alert their student monitor. The student monitor will help them fill out a judged run submittal form, which will then be sent to the judges. Teams may make as many judged runs as they wish; however, each judged run counts toward the total number of team runs for judging purposes.
Time of Execution
When the contest judges are executing a program using the official contest data, a solution will be judged to be incorrect if it does not execute in a specified time limit (usually less than one minute).
Judging
If a program is judged to be correct, a judging entry will be returned to the team with CORRECT written on it. If a program is judged to be incorrect, a judging entry will be returned to the team with one of the following indicated on it:
- Wrong Answer - The program generates incorrect answer(s) to the question.
- Run-time Error - During execution, a run-time error occurred. An example of a run-time error is dividing by zero.
- Time-limit exceeded - The program took a substantially long time to execute - the time limit is usually one minute.
- Presentation Error - The output was not formatted according to specifications.
- Compilation Error - The judges were not able to run the code.
- Other - More than one type of error was found, or the problem does not fit into any of the above categories. A more detailed explanation will follow.
Scoring
- Teams should be ranked according to the number of problems solved correctly
- Points will be awarded based on the difficulty of the problems (Less penalty points will be given for correct advanced questions)
- Teams who have the same number of problems solved correctly can be ranked on the increase of penalty points. For each of the correct answers, you may issue penalty points based on the amount of time it took for the team to finish their problem correctly. Eg: 1 point for every minute taken to solve the problem. (The less points a team builds up, the higher their standing)
- Points can also be issued based on the execution time of the program
|
