CERC 2017 Banner
 
 
CENTRAL EUROPE REGIONAL CONTEST 2017
 
Zagreb, Croatia, November 17-19
 
 
COMPETITION RULES
 
General Rules
 
The General Rules of the 2017 Regional Competitions are published on the ICPC website.
 
Local Rules
 
Teams
 
  • Only teams accepted by the Regional Contest Director can take part in the contest.
  • All teams that want to participate have to check in at the registration desk on Friday, November 18, or on Saturday, November 19 (late registration). A team cannot compete in the CERC if the Participation Fee has not been paid in advance. No cash will be accepted during the registration.
 
Conduct of the Contest
 
  • All team members must attend all contest activities as specified in the schedule. The Coach is expected to attend or be available via phone during contest activities. Failure to attend any of the designated contest events can result possibly in the disqualification and forfeiture of any prizes.
  • At least six problems will be posed. As far as possible, problems will avoid dependence on detailed knowledge of a particular applications area or a particular contest language. However, some knowledge of basic graph, text and geometric algorithms can be helpful.
    (A good source of such algorithms is the book "Introduction to Algorithms, 2nd edition" by Cormen, Leisserson, Rivest and Stein).
  • The language of the contest is English. All written contest materials and all communication with the contest officials will be in English.
  • Contestants may bring resource materials such as books, manuals, notes and program listings. Contestants may not bring any machine-readable versions of software or data. Contestants may neither bring their own computers, computer terminals and calculators nor any kind of communication devices such as radio sets, cellular phones, pagers, PDAs, smart gadgets, etc.
  • A team may bring their own keyboard (standard USB keyboard without wireless connectivity, embedded card readers etc). The keybard should be submitted to the organizer during the Registration at Friday or Saturday morning.
  • Solutions to problems (source programs) submitted for judging are called runs. Each run is judged as accepted or rejected and the team is notified of the result.
  • Rejected runs will be marked as either "compile error" or "runtime error" or "time limit exceeded" or "wrong answer".
  • A contestant may submit a claim of ambiguity or error in a problem statement by submitting a clarification request to a judge. If the judges agree that there is an ambiguity or error, a clarification will be issued to all contestants.
  • Contestants are not to converse with anyone except members of their own team and personnel designated by the Regional Contest Director. System support staff may advise contestants on system-related problems such as explaining system error messages.
  • The contest will be held in a networked environment. The network may only be used to submit solutions, to ask questions, back up the solutions and to produce listings in ways designated by the organizers. Any other use of the network is strictly forbidden and shall result in immediate disqualification and removal from the contest area.
  • While the contest is scheduled to last five hours, the Regional Contest Director has the authority to alter the length of the contest in the event of unforeseen difficulties. Should the contest duration be altered, every attempt will be made to notify contestants in a timely and uniform manner.
  • A team may be disqualified by the Regional Contest Director for any activity that jeopardizes the contest, such as dislodging extension cords, unauthorized modification of contest materials (hardware of software), forbidden network activities or distracting behavior.
  • The Regional Contest Director is solely responsible for ruling on unforeseen situations and interpreting these Rules.
 
Scoring of the Contest
 
  • A problem is solved when it is accepted by the judges. The judges are solely responsible for accepting or rejecting the submitted runs. In consultation with the judges, the Regional Contest Director determines the winners of the regional contest. The Regional Contest Director and judges have the authority to adjust for or adjudicate unforeseen events and conditions. Their decisions are final.
  • Teams are ranked according to the majority of problems solved. Teams that solve the same number of problems are ranked by the least total time. 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 accepted run plus 20 penalty minutes for every rejected run for that problem, regardless of the submittal time. No time is consumed for a problem that is not solved. In case of a tie, teams are ranked by the number of minutes elapsed from the beginning of the contest until the first correct solution was submitted. If the last rule does not break the tie, the Regional Contest Director is responsible to find a fair solution.
  • The penalty minutes are not added if the program was rejected with "compile error".
 
Contest Environment
 
Warning: the technical specs may change before the competition.
 
  • Each team will be allowed to use one IBM PC compatible computer. The guaranteed configuration of the computer includes a keyboard, mouse and monitor. The team will also have access to a shared printer via the Evaluation System.
  • Users’ environment will consist of a workstation running Linux operating system with a desktop environment and a set of standard system and development utilities.
  • Access to a number of editors, including codeblocks, eclipse, geany, gedit, kate, mcedit, vim, xemacs and xwpe, will be provided. Debuggers, apart from those in some of the aforementioned editors, will be ddd, gdb and nemiver.
  • Submission of solutions will be carried out through a web browser. GUI-based browser will be provided for this task.
  • The programming languages of the contest are C/C++, Java and Python 2/3.
  • The name of the submitted program must have *.c for C programs, *.cpp for C++ programs, *.java extension for Java programs and *.py for Python programs.
  • The programs will be compiled and executed in x86-64 Linux system.
  • Size of the source code must not exceed 100 KB.
  • The programs will be compiled using the following commands:
    • C:
      gcc -std=c99 -static -Wall -o -lm -O2 -DONLINE_JUDGE
    • C++:
      g++ -std=c++11 -static -Wall -o -O2 -DONLINE_JUDGE
    • Java:
      javac Main.java
  • Access to the following compilers will be available:
    • GCC v. 4.9.2 for C and C++ programs
    • OpenJDK Java v. 1.8.0 for Java programs
    • CPython v. 2.7.9 for Python 2 programs
      CPython v. 3.4.2 for Python 3 programs
  • The program must compile in 20 seconds.
  • The ANSI C standard library and the standard template library will be available.
  • For each compiler on-line manual will be installed.
  • Executable code cannot have more than 10 MB.
  • Each program has 512 MB of memory at its disposal, unless the problem statement specifies a different limit.
  • Java programs stack size is limited to half of the memory limit for that problem. For example, if a problem memory limit is 512MB then the stack size limit will be 256MB. C/C++ and Python programs have no separate stack limit.
  • Each program has to terminate with an exit code 0 (return 0).
  • Submitted programs are not allowed to:
    • use or create any file other than stdin and stdout
    • use more than one process or thread
    • use any network facilities