| 53 | | The checker behaviour is as follows: it takes two parameters: The outputfile generated by the participants code, followed by the output file given in the problem statement. The checker returns Zero if the output is accepted, and non-zero value otherwise. The checker can also output exactly one line of text to stdout, which will be taken the score for the submission. You may not output anything else, although you are allowed to output into stderr. |
| | 53 | The checker behaviour is as follows: it takes two parameters: The outputfile generated by the participants code, followed by the output file given in the problem statement. The checker returns Zero if the output is accepted, and non-zero value otherwise. |
| | 54 | |
| | 55 | In some instances, you may want to provide custom scores depending on the output. In this case, you should first add the following node in the XML file. |
| | 56 | |
| | 57 | <checker-outputs-score>true</checker-outputs-score> |
| | 58 | |
| | 59 | In this case the checker should output the following on stdout: |
| | 60 | |
| | 61 | <score> <small description> |
| | 62 | |
| | 63 | Note that <small description> will be visible to the user, in fact, it will be displayed on the queue page. Therefore: 1. don't output sensitive information, and 2. Keep it short. If the checker returns 0, then any score outputted will be disregarded and the score will be set as 0. |
| | 64 | |
