One of the main burdens of the Jury of the Scholastic Programming Contest is not to decide whether a submitted program is incorrect, but how to classify the error. In the past, we had 'Failed Testcase', 'Wrong Answer', 'Wrong Output Format' and 'Too much/Too Little Output' to worry about. The interpretation of these messages depended largely on the jury member involved. For instance, while some believe that 'Wrong Answer' indicates that all answers are wrong, and 'Failed Testcase' applies when at least one answer is right, others feel that 'Wrong Answer' should be used if more than one answer is wrong, and 'Failed Testcase' only if exactly one test went wrong. Fortunately, all these worries are gone, since now we only need to distinguish between 'Wrong Answer', 'Presentation Error' and 'Accepted' (all other messages are the result of compilation errors, run-time errors, and non-terminating programs). To eliminate any subjectivity in deciding between a Presentation Error and a Wrong Answer, the Jury of this year’s Programming Contest has defined an exact procedure to determine whether a program produces a 'Wrong Answer', a 'Presentation Error', or should be Accepted. In the description of the rules, we distinguish between JuryOut and SubmitOut, as the output intended by the Jury, and the output submitted, respectively. The JuryOut contains parts which are considered essential in the output of a correct algorithm. Those essentials are placed between ‘[’ and ‘]’. Those brackets are not part of the output, thus they should not appear in SubmitOut. The algorithm to decide between 'Accepted', 'Wrong Answer' and 'Presentation Error' is as follows:
2/2 Sample Input 4 12 Just one line? Just one line? 22 The first characters of the alphabet are: [abcde] Here they come: abcde 11 That's it: [abcde] That's it: AbCdE 11 [2] and [3] make [5] I guess 2 and 3 are less than 50. Sample Output Accepted Wrong Answer Presentation Error Presentation Error