IDI Open 2017:
Date: April 22
Time: 10:00 - 17:00 Registration: Closed



Published: 29.03.2014 - 16.55, Author: Christian "x10an14" Chavez

If you feel that there is something in the rules that are unclear or need to be added, feel free to send an e-mail to konkurranser [at]


  • A team for any given contest must consist of at least one person, and may consist of a maximum three persons.
  • One person can only be a member of at most one team per contest.


Teams are ranked according to the most problems solved. Teams that are tied for amount of problems solved are ranked by least total time and, if need be, by the earliest time of submittal of the last accepted run.

The total time is the sum of the time consumed for each problem solved. The time consumed for a solved problem is the time elapsed from the beginning of the contest to the submittal of the first accepted run plus 20 penalty minutes for every previously rejected run for that problem. There is no time consumed for a problem that is not solved.

Prize Eligibility

Check out the information section for information on prize eligibility.

Computing Constraints

  • Each team is allowed to use no more than one specified computer.
  • The supported programming languages are Python 2, Java, C++ and C.
  • All IDE's are allowed to use (including eclipse, Visual Studio, vim, emacs, TextPad, Notepad, etc).
  • All submitted code must be written by your own team during the contest.
  • Your programs may not:
    • access network,
    • read or write files on the system,
    • talk to other processes,
    • fork,
    • or similar stuff.
    • If you try, your program will hang or crash. If it hangs, it will take a couple of minutes before others will be able to run their programs. So please do not attempt crack somebody who uses their spare time trying to give you something valuable.

Allowed resources


gcc -g -O2 -std=gnu99 -static -lm -o {BASENAME} {FILENAME}
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2

g++ -g -O2 -static -std=gnu++11 -o {BASENAME} {FILENAME}
g++ (Ubuntu 4.8.2-19ubuntu1) 4.8.2

javac -encoding UTF-8 -sourcepath . -d . {FILENAME}
Run: java -Xss8m {BASENAME} < {INPUT}
OpenJDK javac 1.7.0_75

Run: python {FILENAME} < {INPUT}
Python 2.7.3 (2.2.1+dfsg-1ubuntu0.2, Dec 02 2014, 23:00:55)

Behaviour during the contest

You are NOT allowed to write any code or even touch the problem set until the contest has started.

Contestants are only allowed to communicate with members of their own team and the organisers of the contest. You are not allowed to surf the web (except for allowed content), read e-mail, chat on Facebook, or similar things. The only network traffic you may generate is from submitting problem solutions and access content specified by the organisers.


The different results you can get for your submissions are:

This means that your solution was correct. Congratulations! You just solved the problem :)

Wrong answer
This means that the answer returned from your program was incorrect, and your algorithm is either incorrect or your program contains a bug (This might also be a minor formatting bug in the output. It might be a good idea to check this out).

Run time error
Your program either crashed (error or exception), or it simply ran out of resources (i.e. java heap space)

Time limit exceeded
Your problem used more time than allowed for this problem,

Compile Error
Your program did not compile. If it compiles locally, check out the compiler switches shown at the bottom of the page. If you think there is an error in the system, please let the judges know.'

Internal Error (contact judges)
An internal error occurred while running your program. Run off and fetch a judge!


Should you feel that one of the problem statements are ambiguous or are wondering about how something works, you could request a clarification (through the clarification interface on the contest pages). The judges will then review the clarification. If they feel that you should figure out the answer by yourself, the answer will be "No reply. Read problem statement.". Otherwise they will try to answer the question as best they can.

Score table - Top 5 | All

# Team Solved Onsite