Titelgrafik.

Information/Rules for the BOI'06 Online rerun

These are the "rules". They are the same as the ones used for BOI, but

Don't cheat. Cheating is l4|\/I3 and there is really no point in doing it.

Competition

The solutions submitted during the practice round will be immediately evaluated, but the results will not be considered in the final ranking.

The contestant can use all software and documentation found on the IOI CD and the Grading server. No other software or documentation is allowed. (Well, we are not too strict about that in the online competition...)

The Tasks

The tasks are intended to be of algorithmic nature. That is, the focus is on designing correct and efficient algorithms.

In case of any discrepancies in the translations, the English text is binding and official.

The Solutions

Unless stated otherwise in the task description, the solution of a task is a program written in the following three supported programming languages:

Language Standard dialect
C ISO C99
C++ 1998 ISO C++, extended with the same long long int idiom as in ISO C99
Pascal Borland Turbo Pascal 7.0

It is strongly advised to avoid using platform-specific features in Pascal. For C and C++, it is recommended to use only the aforementioned standard dialects. The source code of each solution must be contained in one file and submitted through the OWINF contest system interface.

The program must read input data from an ASCII text file with the name given in the task description. Contestants must not include full path in file open operations. They must assume that input file is in the current directory. Programs must not attempt to read any additional data neither from the keyboard nor from files not specified in the task description.

Contestants may always assume that the input data agrees with the task description.

The input file consists of a number of lines, each of them (including the last one) terminated by an end-of-line marker. Input values are separated from each other by either a single space character or a single end-of-line marker. The structure of input is always such that a contestant does not need to worry about end-of-file conditions.

The program must write output data to an ASCII text file with the name specified in the task description. Contestants must not include full path in file open operations. They must create the output file in the current directory. Output on the screen or contents of any other files will not be evaluated. It is not allowed to make working files during program execution. Output data must consist of a sequence of items separated by space characters or end-of-line symbols as specified in the task description. Contestants must not add output of their own.

In output, spaces and end-of-line symbols must appear exactly as stated in the task description. Each output line (even the last one) must end with the end-of-line symbol.

Any of the above conditions may be overridden in the task description. Please note that the input and output file names are case-sensitive and the input file is read-only in the evaluation system.

Assistance

To get assistance, contestants can join #owinf on the IRCnet or send a mail to me (rrayst@ this domain).

A contestant may ask a supervisor for assistance at any time. The supervisors will answer questions about the competition tasks (see the section "Requests" below), will try to help with technical problems, help to find toilets, and attend to computer problems (:P In your dreams...).

Requests

Contestants may submit questions and technical support requests.

Questions must be submitted in English to ensure that it is processed. If the question is submitted in native language we will try to get it translated into English.

Do not ask questions related to understanding the tasks in a public chat room or anything similar. Contestants may ask questions concerning the competition tasks only during the first hour of the competition. Only one of the following three answers is possible: "Yes", "No", or "No Comment". All questions not related to the text of the competition tasks will be answered "No Comment". The Jury will answer every question submitted by contestants. Answering may take some time, so the contestant should continue working while waiting for the answer to a given question. The contestant shall not be involved in the discussion.

Delivering the solutions

Contestants submit their solutions using the web-based evaluation system interface.

The Contest system accepts the submission if it compiles and solves the given simple test(s). Alternatively, the contestant can force the system to accept the submission even if it fails to solve the test(s) by checking the appropriate option in the user interface of the system. The system will report whether the submission was accepted or not.

A contestant can register for an account using the web interface. A password will be sent to him via email.

Evaluation Process

After each day, an evaluation process starts.

Evaluation of a program involves several test runs with confidential input data and special evaluation software. A test run for a program consists of the following steps:

The points awarded for each test run are aggregated to give the final score for the problem. The team leader will receive a printed form with evaluation results.

The evaluation will run on separate computers with the Linux operating system. The compilation characteristics are as follows:

Language Suffix Compiler and version Compilation command and options
Pascal.pasFree Pascal 2.0fpc -Mtp -Sg -O2 -XS
C.cGCC 4.0gcc -std=c99 -O2 -static -lm
C++.cppGCC 4.0g++ -std=c++98 -O2 -static -lm

The filename must be suffixed exactly as shown in order for the Grading system to select the appropriate compiler. Programs must not attempt to modify hardware and operating system settings. Programs must not attempt to use more than 16 MB of memory. The size of a source file must not exceed 1 MB. This may be overridden in the task description.

Testing is done on an AMD-K7 600MHz processor.