BAPC 2010
Benelux Algorithm Programming Contest 2010, Leiden

Contest rules

Note that this is a preliminary version of the rules that may still be subject to change.

1. Definitions

The Benelux Algorithm Programming Contest 2010, organised by De Leidsche Flesch on 23 October 2010.
De Leidsche Flesch:
Study association for Computer Science, Mathematics, Physics and Astronomy of the Leiden University.
The members of the organising committee of De Leidsche Flesch.
The website, maintained by the organisation and available at
The group of people responsible for making the problems and checking the solutions submitted by the participants, appointed by the organisation.
Those responsible for delivering print-outs, answering questions and various other tasks, appointed by the organisation.
Organisation, members of the jury and runners.
Member of a participating team that competes in BAPC.
A submission of a solution by a team.

2. Organisation

2.1 The organisation consists of members of De Leidsche Flesch.

2.2 The organisation has formed a jury which exists of members of the organisation, students and staff of the Leiden University and other universities.

2.3 The organisation will appoint runners who will watch over the competition areas during the contest, hand out the print-outs and balloons and will be available for practical questions during the day.

2.4 The organisation will form a board of contest leader.

2.5 All crew nenbers will be recognizable by their shirt and/or badge.

3. Participation

3.1 Introduction

3.1.1 Participation is only possible in teams consisting of up to 3 persons.

3.1.2 There are two pools: one for student teams and one for business teams.

3.1.3 Changing the composition of a team is only possible when the organisation has agreed upon this.

3.1.4 The organisation decides how many teams from each institution are allowed to compete. The organisation will consider the number of interested contestants from each institution.

3.1.5 The organisation has the right to deny teams of participation before the start of the contest.

3.2 Student teams

A student team:

3.2.1 may participate for free.

3.2.2 exists of students from the same institution and who are not participating in another team.

3.2.3 has a coach, which is the contact person of a team. This can be a team member or a student or staff member of the institution.

3.2.4 participates in the student teams pool for the title "Winner of the Benelux Algorithm Programming 2010" with the cup and the prize money of 1024,- 512,- and 256,- euro for first, second, and third places respectively.

3.2.5 consists of students who are eligible for the North Western European Programming Contest 2010.

3.3 Business teams

A business team:

3.3.1 pays the registration fee, before the start of the contest.

3.3.2 consists of persons who are employed by the same company or institution.

3.3.3 participates in the business teams pool for the title "Winner of the Benelux Algorithm Programming Contest 2010" and the prize money of 512 euro.

4. The contest

4.1 Introduction

4.1.1 The language used during the contest is English.

4.1.2 The contest lasts for 5 hours.

4.1.3 From the beginning until one hour before the end of the BAPC, the scores are displayed.

4.2 Problems

4.2.1 The jury will provide at least 6 and at most 10 problems.

4.2.2 When a problem is unclear a "clarification request" can be sent to the jury. The jury will respond to this request. If the response is relevant to all teams, the jury will send the response to all teams.

4.2.3 The jury has the right to change or withdraw problems during the contest. When this happens the jury will inform all teams.

4.3 System

4.3.1 Each team has the same workplace available.

4.3.2 A solution has to be written in C, C++ or Java (unless the exercise explicitly states otherwise).

4.3.3 The jury decides per programming language which libraries and function calls are allowed to be used in the solutions.

4.3.4 All prints made by the teams are brought by a runner. Participants are not allowed to be near the printers.

4.3.5 A team is allowed to bring up to 30 A4-sized pages of documentation; no other documentation (including books and manuals) is allowed.

4.3.6 A team is not allowed to bring software.

4.4 Department rules

4.4.1 The house rules apply to everybody inside the Plexus building.

4.4.2 Inside computer rooms eating, drinking, smoking and talking in a loud voice is not allowed.

4.4.3 The use of hardware, including all calculators, which is not approved by the organisation is forbidden, with exceptions of simple watches and medical equipment.

4.4.4 Changing of hardware or operating software is strictly forbidden.

4.4.5 During the contest, communication within the team and crew is allowed. Communication with everyone else is forbidden during the contest.

4.4.6 Participants will follow orders given by the crew.

4.4.7 Participants will wear the shirt and badge provided by the organisation.

4.5 Judgement

4.5.1 All submissions are handled by an automated jury system. The organisation is responsible for behavior of the system. The jury will check the behavior of the system.

4.5.2 Each submission is acknowledged.

4.5.3 For each problem, the jury has a correct solution and test data.

4.5.4 A submission is correct when it has a solution to the input in a time limit decided by the jury and the output is the same as the output of the jury. This time limit is not announced to the teams.

4.5.5 The winner of a pool is decided by (in order):

  1. The team with the most correctly solved problems.
  2. The team with the least solving time. This is the sum of the time needed for every solved problem (defined as the time between the beginning of the contest and the submission of the first correct solution), plus a 20-minute penalty for each wrong submission until the first correct submission. (Incorrect solutions for which a team hasn't submitted a correct solution or incorrect solutions submitted after a correct solution was accepted do not add to the solving time.)

4.5.6 The jury is responsible for everything that has to do with the problem set and can be contacted for this through the "clarification requests."

5. Special rules

5.1 The organisation has the right to disqualify teams for misbehavior or breaking the rules.

5.2 The contest leaders have the right to stop the contest, extend the contest time, temporarily block submissions for all teams or change the scores in exceptional conditions.

5.3 In situations to which no rule applies, the organisation decides.