Hosted by Friedrich-Alexander-University Erlangen-Nuremberg

System Information

Computer Environment

At the contest, all the teams will have a similar working environment based on Debian Linux. We will not provide a Windows environment.

Hardware: The keyboards will have German layout, but teams may bring their own USB-keyboard. If you will do so, please inform the technical director about your keyboard layout and model. You have to turn in keyboards in the registration on Friday. Please mark your keyboard with your team name and institution.

Software: Debian based Linux Distribution with usual goodies. The default window manager is XFCE. Here is a list of available Software:

  • Browsers: Firefox, Opera
  • IDEs: Anjuta, Eclipse, KDevelop
  • Editors: Ed, Emacs, GEdit, Joe, KWrite, Kate, Nano, Vim, gVim, xEmacs
  • Compilers: gcc/g++, Java (same versions as on the evaluation system)
  • Debuggers: gdb, valgrind, ddd

If you need any other software, do not hesitate and contact the technical director early enough.

The computers will have restricted internet access, so you can connect to our servers in order to submit problems or view documentation.

For each language, we provide an alias, as show in the following table:

Language Compiler Command Alias
C gcc (version 4.3.2) gcc -Wall -O2 -g -static -lm $SOURCE mygcc
C++ g++ (version 4.3.2) g++ -Wall -O2 -g -static $SOURCE myg++
Java OpenJDK (version 1.6.0_0-b11) javac $SOURCE myjavac

In addition to the compilation aliases, we provide an execution alias for Java (myjava), that executes: java -Xss64m -Xrs -Xmx64m -server $CLASSNAME

Automatic Judging: DomJudge

For judging, we are using an adopted version of DomJudge. The manual is available here.

Once you have made a submission, the result of the automatic judge should appear within short time. This result is initially marked as in pending state to indicate that it has to be confirmed by a judge person. Once confirmed, the submission result is marked final.

In about 99% of the cases the automatic judge makes a correct evaluation. But problems may arise unexpectedly, such as a system resource failure, a mistake in a test case, etc. You should not worry too much because the system is highly flexible in allowing the judges to re-evaluate submissions without a team being penalized for it, and thus undoing whatever went wrong first.

Printing

To print a copy of one of your programs, load it first into DomJudge and then press the button Print. Please do not leave your place to collect the printout from the printer; someone will bring it to you. You are only allowed to print your programs not the problem descriptions.

Asking Questions

In case you need to ask a question to the jury during the contest, please select in DomJudge the problem to which the question is related and then press Ask. Once you have submitted the question, every team will have access to it as well as the answer given by the judges. Some questions may not be answered directly, because they have been already answered or because the judges feel it cannot be answered without giving away relevant information.

Please be considerate to other teams and avoid questions that simply can not be answered (e.g. what is the output of judge's solution for the following input ...).

Documentation

During the contest, teams will have access to the documentation of DomJudge, the STL, and JDK. Additionally, linux man pages are installed.