In the Final Event, participants of both Groups will take a practical test. The duration will be three hours. Contestants who are late for more than 15 minutes will be disqualified.
Programming Languages, Workstation and Resources
The table below lists the allowed programming languages:
||Free Pascal 3.0.0
|Java 8 *2nd-class
|Python 3.5 *2nd-class
*Second-class programming languages are experimental. We cannot guarantee that the problems are solvable using such languages. We also cannot guarantee the proper functioning of the software provided. Contestants may use such languages at their own risk.
The organiser will provide all the necessary hardware and software for the competition. With the exception of one personal keyboard (see section below), contestants are not allowed to use any of their own resources in the competition.
Contestants shall develop their solutions in Windows operating system. However, submitted programs will be compiled under the Linux operating system. Apart from the above software, Visual Studio Code (with Pascal, C/C++, Java and Python plugins) will also be installed.
During the competition, contestants are allowed to seek clarification on the wordings of the tasks from the Adjudicators by raising their hand. Should the condition deem necessary, the clarifications will be announced to all contestants. Clarification related to the solutions will not be entertained.
Contestants can bring one personal keyboard for use in the competition. Wireless keyboards, keyboards that require installation of drivers, and mechanical keyboards fitted with “blue” switches (or equivalent) are not allowed. The adjudicators reserve the right to examine and disallow any keyboard.
The paper shall consist of several programming tasks. Each task may carry different points. Each task will be further divided into one or more subtasks. Each subtask may carry different points.
Submission of Solutions and Adjudication
Contestants should submit their solution source codes through a web interface. The adjudicators will compile the source codes submitted by contestants, and then assess the compiled programs by testing them with a set of data unknown to the contestants and a marking scheme to be determined by the Adjudicators. To score points for a subtask, contestants’ programs must be correct for all test cases in that subtask.
Contestants will receive feedback about their submissions, including type of error first encountered (if any) for each subtask. A contestant’s final score will be the sum of points received from solved or partially-solved subtasks. Contestants may submit at most once per task per 60 seconds, and at most 50 times per task.
Any queries about the competition should reach the Chief Adjudicator immediately after the competition. The decision of the Adjudicators will be final.