Rules

This page summerizes the rule changes with respect to last year's Pentathlon as well as the rules regarding how the Pentathlon works, the disciplines and projects, the overall score and the statistics.

The BOINC Pentathlon is a competition by and for Volunteer Computing enthusiasts. The organizers do not approve of systems that are based on monetization instead of enthusiasm, and will not provide a stage for teams which have the main goal of creating and spreading such systems, not least because of incidents in the past. It should go without saying that the goal of participating in the Pentathlon is to advance the projects and the own team. Any behaviour that intentionally harms the projects or other teams devalues the Pentathlon and may lead to consequences from the organizers, the other participants or the project administrators.

Modifications

2019

  1. New discipline: Javelin Throw. This discipline consists of five not necessarily consecutive days. Credits are counted for each day separately, and the rankings are based on each team's third best day. Javelin Throw replaces Swimming.
  2. While the choice of projects for the disciplines is still based on the teams' suggestions, it will be more flexible in order to avoid that the most popular project is automatically chosen for the shortest discipline. In any case, Sprint and Javelin Throw will happen at projects that provide workunits with a quorum of 1, and there will be only one discipline at a GPU project.
  3. This year's Marathon takes place at a subproject of the World Community Grid chosen by the project administrators. Hence, the World Community Grid and its subprojects are not available for the other disciplines.

All teams should sign up for the Pentathlon until 27 April 2019 using this registration form. Subsequent submissions are possible until 02 May 2019, but the project suggestions cannot be taken into account anymore.

The BOINC Pentathlon starts on 05 May 2019, 00.00 UTC, and ends on 19 May 2019, 00.00 UTC. So, it will run for exactly 14 days.

No team will know the complete Pentathlon schedule right from the beginning! The exact time and the project for each discipline are announced on the main page and via Blog (Feed ). This announcement happens on the fifth day prior to the start for the Marathon and one other discipline, and on the third day prior to the start for the Sprint and one other discipline. Each day of Javelin Throw is announced three days in advance. While all disciplines start and end at 00.00 UTC, the projects may be announced at different times (00.00 UTC, 06.00 UTC, 12.00 UTC, 18.00 UTC) to avoid that some teams are always surprised in their sleep.

The disciplines differ in runtime and possible projects. For example, the Marathon runs during the whole Pentathlon, while the Sprint lasts only three days. Hence, at any time at least one discipline will run, but often different disciplines will run simultaneously.

The BOINC Pentathlon consists of 5 disciplines:

  1. Marathon (14 days)
    • Subprojekt of the World Community Grid chosen by the project administrators
  2. Sprint (3 days)
    • CPU or GPU project with a quorum of 1
  3. City Run (5 days)
    • CPU project
  4. Cross Country (5 days)
    • CPU or GPU project
  5. Javelin Throw (5 x 1 day, only each team's third best daily score counts)
    • CPU or GPU project with a quorum of 1

Each team may cast four votes for projects from the preselection below while signing up. These votes will be taken into account for the final project choice. However, only one discipline can take place at a GPU project, and only projects that provide workunits with a quorum of 1 can be chosen for Sprint and Javelin Throw. The projects chosen for the Pentathlon will therefore not necessarily be the four projects with the most votes.

Quorum CPU GPU
Quorum 1 Cosmology@Home
LHC@home
NFS@Home
SRBase
YAFU
yoyo@home
Collatz Conjecture
Quorum 2 Amicable Numbers*
RakeSearch
Einstein@Home
SETI@home

*: Amicable Numbers is listed as a CPU project this year, because the GPU application is relatively inefficient and uses very much CPU time at the moment.

Projects are not eligible if they

  • were chosen in last year's Pentathlon (Asteroids@home, NumberFields@home, PrimeGrid, Rosetta@home, Universe@Home)
  • cannot provide a sufficient number of workunits
  • do not support at least Windows and Linux
  • provide non-CPU-intensive (NCI) applications
  • use buggy or test-only applications
  • do not allow the creation of new accounts
  • do not support WebRPC

To keep it as transparent as possible, we will publish the suggestions of every team when announcing the final project.

For the overall score, points are awarded in every discipline to the best 30 teams that received credits. The champion of a discipline collects 100 points. The exact distribution of points:

Place Points Place Points Place Points
1
100
11
45
21
15
2
90
12
42
22
12
3
80
13
39
23
10
4
70
14
36
24
8
5
63
15
33
25
6
6
60
16
30
26
5
7
57
17
27
27
4
8
54
18
24
28
3
9
51
19
21
29
2
10
48
20
18
30
1

The team which is able to collect the highest number of points in all 5 disciplines will win the BOINC Pentathlon. This also means that the champion may get a maximum number of 500 points.

In case of a tie in the overall score, the tied teams are ranked by their head-to-head comparison. Hence the team which is placed better than the other teams in more disciplines is ranked higher.

Of course, also the champions of the single disciplines are being honored. Therefore teams have the possibility to reach for the pedestal in a single discipline if they don't see a chance for themselves to succeed in the overall placings. In the end, they are being honored as well.

Only the statistics on https://www.setigermany.de/boinc_pentathlon/statistiken/pentathlon.php are considered to award points and choose the champions. They are based on data provided by the projects via WebRPC and are updated every hour. For the Marathon, the hourly updates are based on incremental updates provided by World Community Grid in addition to their daily updates.

A race day will start and end at 0:00 UTC (also known as GMT).

If a project's server is unreachable at the starting time of a discipline or at the beginning of a day of Javelin Throw, only credits granted after the first successful statistics update will be counted. Likewise, the last successful statistics update will be the final result, if the server is unreachable at the ending time of the discipline or the end of the day, respectively.