The Baltic Olympiad in Informatics 2020 (BOI 2020) is an individual contest between contestants from eleven countries (in alphabetic order): Denmark, Estonia, Finland, Germany, Iceland, Latvia, Lithuania, Norway, Poland, Sweden and Ukraine. Each country can send up to six contestants. The current host country may send an additional, unofficial team. Contestants must be eligible to compete in IOI 2020 to be participants in BOI 2020.
The contest days of BOI 2020 are Wednesday, April 29, and Thursday, April 30. On each contest day the contestants will have five hours to complete three tasks.
There will be a practice session on Tuesday, April 28, to familiarize the contestants with the contest environment. The solutions submitted during the practice contest will be graded, but the results will not be considered in the final ranking.
Each contestant will have a desk with a workstation. Software in all workstations is identical.
Contestants can bring pens, pencils and erasers with them. Paper will be available in the contest room.
Each contestant may bring one wired non-programmable USB keyboard and/or one wired non-programmable USB mouse to replace the default ones provided with the workstation. Contestant keyboard and mouse should be presented to Jury during practice session.
Each contestant may bring one printed, non-annotated natural language dictionary. Contestants may bring small mascots such as stuffed toy animals.
Drinks and snacks are not allowed in the contest room, but there will be water and snacks nearby outside contest rooms.
Contestants are not allowed to bring any additional reference materials such as books, program listings or notes. Contestants may not bring any electronic devices (cell phones, digital cameras, etc.).
Contestants who want to bring any other items must contact the Jury via their team leaders.
Any keyboards, mice, dictionaries or mascots must be brought to the contest room during the practice session. They will be checked and provided to the contestant during the contest sessions.
After the first contest day, the contestant must leave these items on their table if they want to use them during the second contest day. After the second contest day, the contestant must take any of these items with them.
The tasks posed at BOI 2020 are intended to be of algorithmic nature. That is, the focus is on designing correct and efficient algorithms. In some tasks, also efficiency of implementation may be a factor. Each task will be divided into one or more subtasks, each worth a portion of the total points.
Unless stated otherwise in the task description, the solution of a task is a program written in C++11, Java 8, or Python 3 programming language in one source code file. Each submitted source code file must be smaller than 256 KB, the evaluation server must be able to compile it in less than 10 seconds and at most 512 MiB of memory.
Solutions have to run within the time and memory limits specified for every task separately. Time limit given in the task statement applies to all solutions. The memory limit is on the overall memory usage including executable code size, stack, heap, etc. Limits are applied to individual test runs.
The Jury guarantees that there are C++11 and Java 8 solutions which fit within the specified memory and time limits.
Unless otherwise stated in the task description, solutions are required to read data from standard input and write to standard output.
When contestants enter the contest room at the beginning of the contest, their workstations will be switched on. Contest tasks will be inside envelopes next to the workstations. The account details needed to access the contest system will be given to each contestant in the envelope with the tasks. Contestants are not allowed to open the envelopes or touch the workstations until the start signal is given.
The task descriptions are presented in English and the native language of the contestant if such translation is prepared by their team leader. In case of any discrepancies, the English text is binding and official.
During the contest, communication is allowed only with room supervisors and the Jury.
Contestants may ask a room supervisor for assistance at any time. The supervisors will deliver paper, attend to hardware problems, help to find toilets, etc. However, the supervisors will not answer questions about the contest tasks.
Contestants should submit questions about the contest tasks via the contest system. The question can be written in English or in the contestant’s native language. In the latter case the team leader will be asked to translate question into English.
A question about a task should be phrased so that a yes/no answer is meaningful. The Jury will answer every question submitted by the contestants. The answer will be one of the following:
If similar questions are submitted by several contestants, the Jury may give an announcement via the contest system.
If during the contest there will be changes in grading influencing already announced scores, the affected contestants will be notified via the contest system.
Contestants are free to phrase their technical or contest related issues in any form. These issues/questions should not be related to tasks at all. Such questions will be fully clarified.
The contestants submit their solutions via the contest system and can use the system to view the status of their submissions. When a solution is submitted, it will be compiled and graded, and after this, the contestant will be able to view the results of all test cases (full feedback). However, input and output data are not shown to the contestant. The submission rate of each contestant is limited to one submission every 60 seconds. For each task contestants may submit at most 25 solutions.
Each submission will be graded on several test cases. Each test case will have one of the following outcomes:
Test cases are grouped into subtasks, each worth some points. Unless stated otherwise in the task description, points for a subtask are given only if every test in it is solved correctly and within time and memory limits. The score for a submission is the sum of the scores of that submission over all subtasks. The final score for a task is the maximum score of all submissions to the task.
The contestants will see their scores in the contest system. However, there is a small chance that the score will change later due to appeals: submissions may be re-graded, and the final score will be that yielded by the last grading.
Grading procedures for a task can be overridden in the task description.
Contestants will be given warnings 30 and 10 minutes before the end of the contest. After the end of the contest, during the analysis mode, no further submissions will be included in a contestant’s score.
Any of the actions outlined below are considered illegal during contest sessions:
Moreover, the following rules apply to submissions:
Breaching any of the rules outlined above may be considered cheating and may result in disqualification.
After each contest the contestants will have time to check the full results of their submissions, including test data used in grading.
In case of any disagreement with the results the team leader may submit an appeal. The Jury will answer each appeal and give a short report to the team leaders about all appeals received after each contest. In the event that every submission of a task should be re-graded and re-scored as a consequence of an accepted appeal, note that re-scoring may result in a higher or lower score for any contestant. Should anyone’s score change after grading results have been published, new results will be published again. Score changes resulting from this are not appealable.
All contestants are ranked in descending order with respect to their final scores. Gold, silver and bronze medals are awarded to the contestants using the following algorithm:
The unofficial host team is not included when computing the medal boundaries. However, they are eligible to receive medals according to their achieved scores.