|
2009 Alberta Collegiate Programming Contest
October 17, 2009, 11:00-16:00
|
FIRST OF ALL
Note:
These are the rules from the last competition and are subject to change.
They should be finalized a few days before the competition.
Only teams registered at the ACPC registration (contact Martin Müller,
mmueller@cs.ualberta.ca )
by their coaches can submit solutions.
The coach of each team is responsible for their civil conduct during the contest.
Team composition
All teams should be formed according to the rules of ACM ICPC for
regional contests. Here are some highlights:
- Each team consists of three contestants.
- Each contestant must be a student enrolled in a degree program
at the sponsoring institution with at least a half-time load.
- This rule is not to be construed as disqualifying co-op
students, exchange students, or students serving internships.
- A student may compete in at most four of five consecutive
contests beginning with the first contest held after beginning
post-secondary studies. Whenever in doubt please consult the
(varying) page at
the headquarters.
Rules
- The coaches of participating teams will make sure that every team
has access to only one work station during the contest and that
they do not use forbidden internet or electronic resources during the
contest. With this respect we follow the old ACM ICPC rules:
there is no limit on the amount of printed material that one can bring
to the contest.
- There are 8 or more problems named: A, B, C, D, E, ...
- Teams are ranked according to the most problems solved.
Teams that 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.
- You may ask the judge for a clarification
during the contest.
However,
the most likely answer you will get is: read the problem,
so, do not waste your time on this.
- Decisions of the judge are final.
Submission
- The solution of a problem must be in a single source file with suffix
.c, .cc and .java for C, C++ and Java
source respectively. The Java program when compiled must produce one
class file named by the problem letter (capital). For C and C++ the
only load-time library allowed is -lm.
- You submit your solutions through a web interface (link coming soon).
- All input is from standard input, all output is to standard output.
You must not use any additional files unless a problem
statement specifies what other files to use.
- Your solution must run in a very short time: a few of seconds
must be enough.
- You may get one of the following responses from the judge:
- Accepted
- Rejected
When your submission is rejected, you will get one of the following reasons
for rejection:
- Run-Time Error: any of segmentation fault, bus error or uncaught exception but we will not tell you which.
- Time Limit: your program runs too long on our test data.
- Wrong Answer: your program produces incorrect output for our test data.
- Presentation Error: layout of your program output is not as
expected (it does not necessarily mean that your answers are correct).
- Compile Error: your program does not compile on our machine.
- Submission Error: there was something wrong at your end of the submission procedure, eg. you submitted a C++ program as a C program.
Judging environment
This is the most likely section to be changed. Stay tuned...
- All judging is done on Linux version 2.6.28.2
- For C/C++ gcc (GCC) 4.2.4 is used.
Your submissions will be compiled using the following Makefile:
CPPFLAGS += -Wall -O2
- Java version "1.5.0_18" is used.
Restrictions
- You are allowed to use a web-browser only to connect to
the links mentioned above.
- You must not interfere with other participants of the contest.
- Any attempt at disrupting the conduct of the contest will result
in immediate disqualification of the team.