Skip to content

Rules

These competition rules are derived from those of BOI 2021, but taking back some regulations special to last year’s virtual competition, and mixing-in some of BOI 2019, the latest on-site BOI, when appropriate. Relevant changes (beyond obvious ones, like changing the year from 2021 to 2022), additions and deletions are displayed in red, deletions are crossed out as well.

Participation

The Baltic Olympiad in Informatics 2022 (BOI 2022) is an individual contest between contestants from twelve countries (in alphabetic order): Denmark, Estonia, Finland, Germany (host country), Iceland, Israel*, Latvia, Lithuania, Norway, Poland, Sweden, and Ukraine. Each country can participate with up to six contestants. In addition, countries may send unofficial contestants, participating on-site in case of the host country and online for other countries. All contestants must be eligible to compete in IOI 2022 to be participants in BOI 2022.

* The delegation of Israel will participate online, but nevertheless officially.

Competition format

Due to the COVID-19 pandemic, the competition will be a proctored online competition. Team leaders of each participating country act on behalf of the BOI 2021 Jury and room supervisors where their respective physical presence is required. They are also responsible for ensuring compliance with the rules.

Contest schedule

The contest days of BOI 2022 are Saturday, April 30, and Sunday, May 1. On each contest day the contestants will have five hours to complete three tasks.

There will be a practice session on Friday, April 29, designed to allow contestants to familiarize themselves 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.

Environment and supplies

Each contestant will have a desk with a workstation. The software environment will be provided by a virtual machine, the same on all workstations. Online contestants will use the same software environment as on-site contestants.

Contestants may 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 will be provided during the contest.

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, smart watches, 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 practice session and 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.

Tasks and solutions

The contest tasks posed at BOI 2022 are intended to be of algorithmic nature. That is, the focus is on designing correct and efficient algorithms. In some tasks, efficiency of implementation may also 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++17, Java 8 or Python 3 in one source code file. Solutions must be submitted via the contest system. Each submitted source code file must be smaller than 256 KB and the evaluation server must be able to compile it in less than 30 seconds and using at most 512 MiB of memory.

Solutions have to run within the time and memory limits, which are specified for every task separately. The memory limit applies to the overall memory usage including executable code size, stack, heap and programming language runtime environment, where applicable. Limits are applied to individual test runs.

The Jury guarantees that there are C++17 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.

Starting the contest

When contestants enter the contest room at the beginning of the contest, their workstations will be running, with the virtual machine started. The account details needed to access the contest system will be given to each contestant in an envelope next to their workstation. Contest task descriptions are provided digitally via the contest system, and if requested, in print inside the same envelope. 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 a translation has been prepared by their team leader. In case of any discrepancies, the English text is binding and official.

Assistance and requests

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 the 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:

  • “YES”
  • “NO”
  • “ANSWERED IN TASK DESCRIPTION” — The task description contains enough information. The contestant should read it again carefully.
  • “NO COMMENT” — The contestant is asking for information that the Jury cannot give.
  • “INVALID QUESTION” — The question is not phrased so that a yes/no answer is meaningful. The contestant is encouraged to rephrase the question.

If similar questions are submitted by several contestants, the Jury may give an announcement via the contest system.

If there are changes in grading during the contest 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.

Submission and grading

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. After this, the contestant will be able to view the score achieved by this submission and, for each test case group (see below), the result of the first failed test case, if any (restricted 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:

  • CORRECT
  • PARTIALLY CORRECT
  • NOT CORRECT
  • TIME LIMIT EXCEEDED
  • RUNTIME ERROR
  • NON-ZERO EXIT CODE

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 final score for a subtask is the maximum of the scores for that subtask over all submissions. The final score for a task is the sum of the final scores for its subtasks.

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 the one obtained by the last grading.

Grading procedures for a task can be overridden in the task description.

Ending the contest

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.

Cheating

Any of the actions outlined below are considered illegal during contest sessions:

  • Using any printed materials, except official BOI 2022 materials and unannotated natural language dictionaries brought to the practice session and cleared for use in contest sessions.
  • Using any electronic devices or data carriers, except official BOI 2022 equipment and keyboards and mice brought to the practice session and cleared for use in contest sessions.
  • Communicating in any form to other contestants or people other than BOI 2022 staff.
  • Using a workstation or an account assigned to someone else.
  • Tampering with or compromising the contest system.
  • Attempting to gain access to the hidden test data used for grading solutions.
  • Attempting to store information anywhere other than the home directory of their account.
  • Attempting to access any machine other than their own or the contest system.
  • Attempting to reboot or alter the boot sequence of another workstation.
  • Any other action that is deemed by the Jury as intentionally aimed at gaining unfair advantage over other contestants.

Moreover, the following rules apply to submissions:

  • Submissions must not attempt to access any files on the file system.
  • Submissions must not attempt to use network functions.
  • Submissions must not try to execute other programs.

Breaching any of the rules outlined above may be considered cheating and may result in disqualification.

Appeal process

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.

Medal allocation

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 minimum score for a gold medal is the greatest score so that at least 1⁄12 of the contestants will get a gold medal.
  • The minimum score for a silver medal is the greatest score so that at least 1⁄4 of the contestants will get a gold or a silver medal. A silver medal is given to those who obtained this score but did not obtain a gold medal.
  • The minimum score for a bronze medal is the least score so that at most 1⁄2 of the contestants will get a medal. A bronze medal is given to those who obtained this score but obtained neither a gold nor a silver medal.

Unofficial contestants are not included when computing the medal boundaries. However, they are eligible to receive medals according to their achieved scores.