A problem is solved when it is accepted by the judges. The judges are solely responsible
for
accepting or rejecting submitted runs. In consultation with the judges, the Regional
Contest
Director determines the winners of the regional contest. The regional contest director
and
judges are empowered to adjust for or adjudicate unforeseen events and conditions. Their
decisions are final.
Teams are ranked according to the most problems solved. For the purposes of awards, or
in
determining qualifier(s) for the World Finals, teams who solve the same number of
problems
are ranked by 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 submittal time. There is no time
consumed
for a problem that is not solved.
It is the responsibility of the Regional Contest Director to specify any additional
tie-breakers. Tie-breaker policies must be announced to contestants before the contest
begins.
The programming languages of the regional contest will include C/C++. Additional
programming languages may be used. The programming languages of the World Finals are
Java, Kotlin, Python and C/C++. Prior to the World Finals, the judges will have solved
all problems in Java and C/C++.
Each team will use a single workstation. The regional contest director is responsible
for determining that teams have reasonably equivalent computing resources.
Contestants are not to converse with anyone except members of their team and the organising team. Systems support staff may advise contestants on system-related problems such as explaining system error messages.