Tasks and their types

MO-Eval supports the following standard types of tasks (new task types can be defined, but it takes some effort):

• off-line tasks – program reads input (from a file or from stdin) and then produces an output (to a file or to stdout). Then a checker (a.k.a. judge) program is run, which decides whether the output is correct. If there is only one correct output, the checker can be just a call to diff. In case of tasks with complicated scoring, the judge can also assign points explicitly. See comments in the top-level config file for the exact interface of the judge.
• interactive tasks – program needs to react interactively, usually by reading from stdin and sending results to stdout (sometimes the communication protocol is abstracted out as a library which the tested programs are linked with). In this case, the judge's stdio is cross-connected with the stdio of the tested program.
• open-data tasks – the contestants don't submit a program, but a set of output files instead. Judged similarly to the off-line tasks.

Setting up a task

To define a task, you should create a directory problems/task_name and populate it with the following files:

• config – local configuration file for the task, which overrides defaults set in the top-level config. Task type, list of test cases and many other things can be defined here. Consult comments in the top-level config for explanation.
• test.config – each test case can have its own local overrides of configuration, used for example if you want to have some test cases with a different time limit.
• test.in – input data for the particular test
• test.out – correct output for the particular test (optional)