The race catalogue
The race catalogue is a shared list of race formats — a name, a distance, a track, a number of athletes per heat — delivered to every computer with the shared data. It is a starting point for creating a race of the event, which you then complete in its form. It contains no rules: no heat formation, no seeding, no points.
| # | Broadcast | Event | Distance | Approx. time | Field | Mode | Laps | Track · start | Heat | Seeding | Point table | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | 500 m Femmes | 500 | (1:45) | Women | Paires | 1,25 | 400 · 100 | 2 | Performances t500 → Entry (template) | Coupe | Preparation | |
| 2 | 1000 m | 1000 | (2:30) | Individual | 2,5 | 400 · 200 | 2 | Performances t1000 → Entry (template) | Preparation |
- “From the race catalogue”: the shared list, for the event's sport and discipline.
- The catalogue rows, from the shortest distance to the longest.
- Add creates the event's race.
- The race created: name, distance, track and heat size come from the catalogue; no gender, no point table, and the “Mode” is the catalogue's until you choose a model in the form.
Where an event's races come from
Each event has its own races. They are created in three ways, in the Races tab, Add bar:
| Source | What is copied | What is left to do |
|---|---|---|
| From the event template (a race type from the federation's rules) | The whole rule: heat formation model, point table, formula variable, approximate time, finish line, heat names, seeding; one race per allowed gender. | Nothing required. |
| From the race catalogue | The name, the distance, the variable “t” + distance, the athletes per heat (minimum and maximum); a link to the catalogue row. | Choose the model, the point table, the gender, the category in the form. |
| Empty race | The name “New race”. | Everything, in the form. |
When an event is created, the Create the races of the template box of its form creates all the race types of the chosen template at once.
Where the catalogue comes from
The catalogue is part of the shared data, like the countries, the clubs, the categories or the federations' templates. ChronoFEED keeps it up to date and sends it to every computer in a signed package; your computer receives it:
- at start-up, if Check the common data over the internet at start-up is ticked (Settings › Database);
- when you ask for it: menu.
EVENT only reads the catalogue: there is no screen to change it, and what you change in a race of the event never changes it.
What a row contains
- Name
- The name offered in the list and given to the race created (“1000 m”).
- Sport, discipline
- To offer only the event's rows (see below).
- Race mode
- Shown in the Mode column as long as the race has no model.
- Distance
- The distance of the race created.
- Track length, start line
- Default values, as a last resort (see “What you can change”).
- Number of laps
- Shown when neither the distance nor the track allows it to be computed.
- Athletes per heat (minimum, maximum)
- The heat size of the race created.
Which rows the list offers
Only the rows of the event's sport and discipline (event form) are offered, plus the rows that do not specify them. An event with neither sport nor discipline sees the whole catalogue. The list is sorted by distance, then by name.
What “Add” does
- the row's name, made unique within the event (“1000 m”, otherwise “1000 m (2)”);
- the distance and the formula variable (“t1000”);
- the heat size (minimum and maximum);
- a link to the catalogue row, which still gives default values as long as the form has none;
- no gender, no category, no model, no point table: the race is open to everyone and the template's seeding applies.
The addition is written to the event log.
What you can change
Everything, in the race form (the name, the distance and the approximate time also directly in the list). What you type in the race always takes precedence over the catalogue:
| Form field | Left empty, it takes… |
|---|---|
| Distance (m) | the rule's distance, otherwise the catalogue's |
| Track length (m) | the context's, otherwise the template's, otherwise the catalogue's |
| Start line (m) | the catalogue's if it is meant for the same track and the same distance, otherwise it is computed |
| Heat: minimum, maximum | (copied from the catalogue when added; can be changed) |
| Model, point table, gender, category, heat names, approximate time, finish line | nothing comes from the catalogue |
Examples
Invented data: the Coupe des Érables, speed skating, long track.
1. A standard distance
The catalogue offers, among others:
| Name | Distance | Track | Start line | Athletes per heat |
|---|---|---|---|---|
| 500 m | 500 | 400 | 100 | 2 – 2 |
| 1000 m | 1000 | 400 | 200 | 2 – 2 |
| 3000 m | 3000 | 400 | 200 | 2 – 2 |
You choose “1000 m”, then Add: the race “1000 m” appears, distance 1000, heat 2, track · start 400 · 200. In its form, you choose the gender Women, the category Senior, the model Pairs and the point table Cup, and you rename it “1000 m Women Senior”.
2. The same distance twice
You add “1000 m” again: the new race is called “1000 m (2)”. You rename it directly in the list “1000 m Men Senior” and give it the gender Men in its form.
3. Another track
The Club Vitesse Aurore races on a 333.33 m oval. You add “1500 m” (track 400, line 300 in the catalogue) and type 333.33 in Track length (m): the catalogue's line, meant for 400 m, is no longer used; it is computed (166.68 m) and the preview under the oval says so.
4. A distance missing from the catalogue
The catalogue has no 700 m. Take Empty race, type 700 in the distance: the track comes from the context, the start line is computed and the suggested approximate time is 2:00.