Skip to content
ChronoFEED EVENT Help

Races

The event's races, in order: 500 m Women, 1500 m Men… The list takes the full width; above it, the means to add races. The name, the distance and the approximate time can be changed directly in the list; everything else in the race form, which opens in its own window. This is also where you choose the races sent to the scoreboards.

Edit…Delete…Print the heat list…4Drag a row to change the order. The name, distance and approximate time can be typed directly in the list (click the cell of the selected row, or F2).1
AddFrom the event template1000 mAddFrom the race catalogue3000 mAddEmpty race
2
#BroadcastEventDistanceApprox. timeFieldModeLapsTrack · startHeatSeedingPoint tableStatus
1500 m Femmes500(1:45)WomenPaires1,25400 · 1002Performances t500 → Entry (template)CoupeHeats generated
2500 m Hommes500(1:45)MenPaires1,25400 · 1002Performances t500 → Entry (template)CoupeHeats generated
31500 m Femmes U1715003:15Women · U17Paires3,75400 · 3002Performances t1500 → Entry (template)CoupeIn progress
41500 m Hommes1500(3:00)MenPaires3,75400 · 3002Performances t1500 → Entry (template)CoupePreparation
3
The Races tab of the Coupe Hollywood long track: the name of the third race is being typed in the list (example data).
  1. The actions on the selected race: Move up, Move down, Edit… (the form, in a window) and Delete….
  2. Add a race: from the template, from the catalogue, or empty.
  3. The race list, across the full width. Double-clicking a row opens its form; clicking the Event, Distance or Approx. time cell of the selected row (or F2) lets you change it in place.
  4. The heat list of the selected race, to print (also with a right-click on a race).

The list

Race list

Where: Races

One row per race, in the event's order. To change the order: drag a row to its new place, or use the arrows. The order is used everywhere (tabs, default schedule, exports).

Broadcast
Ticked (default): the race's standings go out to the TABLEAU scoreboards when broadcasting has started. Unticked: the race is removed from the scoreboards at once and does not go back as long as it stays unticked (useful when the results need to be reworked). The change is saved immediately and written to the log; neither the form nor heat generation touch it.
Event, Distance
The name and the metres. Can be changed in the list.
Approx. time
The approximate race time, from one start to the next (“3:15”); in brackets and in grey, the one the schedule suggests from the distance when the race has none. Can be changed in the list.
Field
The gender allowed (Women, Men, Mixed, All) and the race's category, if it has one.
Mode
The template's model (the rule for forming the heats); without a model, the catalogue's race mode.
Laps, Track · start
The values as FINISH will receive them: laps = distance ÷ track; track and start line. An asterisk “*” marks a value given in the form (otherwise, a default value).
Heat, Seeding Time
The size of the heats (“2”; “2–4”: from 2 to 4) and the chain of performance sources in short (“Performances t500 → Entry”) (“(template)”: inherited from the template).
Point table, Status
The points; Preparation, Heats generated, In progress, Finished.

Changing values directly in the list

The name, the distance and the approximate time can be typed in the list: select the row, then click the cell (or press F2), type, and confirm with Enter or by clicking elsewhere; Esc gives up. The value goes through the same checks as the form: an empty or already used name, a distance that is not a number, an unreadable duration (“fast”) or a start line that no longer fits the new distance are refused; the row then keeps its value and the status bar says why. Each accepted change is written to the log.

Move up, Move down

Where: Races, top bar

Move up and Move down move the selected event one place, like dragging a row. The event order renumbers the order of the races sent to FINISH (direct link, races in the database, .cfevent file): if the event has a saved schedule, within each session the races of the moved events take the new order (breaks and other events do not move, an event never changes day); without a schedule, the event order decides alone. A race loaded or started in FINISH keeps its rank.

Edit…

Where: Races, top bar (also: double-click a row)

Opens the form of the selected race in a window, filled with its saved values.

Delete…

Where: Races, top bar; also in the form

Deletes the selected race, its heats and the entries for this race, after confirmation. Refused if there are results.

Print the heat list

Where: Races, above the list (Print the heat list…); right-click on a race

Opens the preview of the heat list of the chosen race: each heat (wave or pair) with its scheduled time, its start positions and its athletes (bib, name, club, category, colour or cap, seeding or entry time, transponders), on A4 or Letter paper, then Print…. A right-click on a row selects it and also offers Edit… and Delete…. All the details: Line-up › Print the heat list.

Add a race

A name already taken becomes “500 m (2)”. Each addition is written to the log. The race added becomes the selected race: open its form to complete it.

From the event template

Where: Races, Add bar

A race type from the template: the rule (model, point table, variable, finish line, heat names) and the seeding are copied. A race type that allows several genders gives one race per gender, with the gender added to the name (“500 m Femmes”, “500 m Hommes”). The race types of the bundled example templates have no gender: they give a single race, “500 m”, for everyone.

From the race catalogue

Where: Races, Add bar

A row of the shared race list (shared data), for the event's sport and discipline: name, distance, athletes per heat. No rule is copied: then choose the model, the point table and the gender in the form. Everything is explained, with examples, in The race catalogue.

Empty race

Where: Races, Add bar

A “New race” to fill in in the record.

The race form

The form opens in its own window with Edit… or by double-clicking a row. Its settings are grouped by theme. Each field has a tooltip explaining it (hover over the label or the field); numeric fields have a list of suggested values (the field's arrow), but you can always type something else.

Edit race "1500 m Femmes"
Race identity
Name1500 m Femmes 1
Categories and genders
GenderWomen CategoryU17
Qualification and ranking rules
Model (template rule)Paires
Heat: minimum2
maximum2
Point tableCoupe Seeding is set in the template (“Template…” button).
Schedule
Approximate race time (m:ss)3 min 15 Race time: a duration (3:00, 2.5, 90 s), or nothing. 2
Distance and track
Distance (m)1500
Formula variablet1500
Track length (m)Empty: 400 m (context: Long track)
Start line (m)Empty: computed (300 m)
Finish line (m after the track zero)Empty: 56 m (template's event type)
1500 m on a 400 m track: start 300 m from the finish → 3.75 laps, first crossing after 300 m.
3
Heat names
◀ Distance ▶ ✕◀ m — P▶ ✕◀ Number (1, 2, 3)2▶ ✕
{distance} m — P{numero:2} Its 4 heat(s): 1500 m — P01, 1500 m — P02, 1500 m — P03, 1500 m — P04
Delete… Race time: a duration (3:00, 2.5, 90 s), or nothing. OKCancel 4
The 1500 m Women's form: the approximate time typed is not a readable duration, OK waits until it is corrected (example data).
  1. The themes: race identity, categories and genders, qualification and ranking rules, schedule; on the right, distance and track, heat names.
  2. A field that is wrong is framed in red and says why, as you type.
  3. The oval diagram and the sentence about what FINISH will receive follow the distance and the track.
  4. OK saves and closes; it stays greyed out while a field is wrong (the list of problems is next to it). Cancel, Esc or the close button close without saving anything. Delete… deletes the race.

OK writes all the fields at once (log: before / after). There is no undo / redo in this tab: Cancel in the window only forgets what is not saved yet.

Form: race identity

Name

Where: race form, Race identity (also in the list)

The name shown everywhere (“1500 m Femmes”). It goes into the names of the heats sent to FINISH.

Required, and unique within the event (regardless of capital letters): an empty or already used name is flagged at once.

Form: categories and genders

Gender

Where: race form, Categories and genders

All, Women, Men or Mixed: who can enter it (“Category races” takes it into account), and the gender sent to FINISH.

Category

Where: race form, Categories and genders

The race's age category, among those of the shared data for the event's discipline (“U17”, “Senior”…). (all): the race is open to every category. Category races in Entries uses it to enter each athlete in the races of their category; the list's Field column shows it.

Form: qualification and ranking rules

Model (template rule)

Where: race form, Qualification and ranking rules (advanced setting)

The template's race model that says how to form the heats: pairs, waves, group start, pursuit Time, or round plan and qualification criteria Position. Changing the model removes the formation settings adjusted in the Line-up module (they came from the old model); the seeds stay.

Heat: minimum Time

Where: race form, Qualification and ranking rules (advanced setting)

The minimum and maximum number of athletes per heat (“Heat: minimum” … “maximum”): 2 and 2 for pairs. The Skaters per heat field of the Line-up module sets the same limit.

Suggested values: 1, 2, 3, 4, 5, 6, 8, 10, 12. A number that is not a whole number, or a minimum greater than the maximum, is flagged.

Point table

Where: race form, Qualification and ranking rules (advanced setting)

The template's point table (“(none)”: no points). It gives the race's points in the combined standings and the overall total.

Time A race's seeding (performance) is set in the template (“Template…” button).

Form: schedule

Approximate race time (m:ss)

Where: race form, Schedule (also in the list, Approx. time column)

The time from one start to the next for a heat of this race (“3:00”): the schedule uses it for the duration of each heat. Empty: suggested from the distance (one minute plus 0.08 s per metre, rounded up to 15 s: 500 m → 1:45, 1000 m → 2:30, 1500 m → 3:00), shown under the field; without a distance, the schedule's default duration. It comes from the template's race type when the race comes from it. A duration entered by hand in the schedule takes precedence.

The suggestion from the distance comes first in the list of suggested values. Type “3:15”, “3.25” (minutes) or “195 s”.

Form: distance and track

Distance (m)

Where: race form, Distance and track (also in the list)

The distance raced. This is what goes to FINISH (not the catalogue's).

Suggested values: the distances of the template's race types, of the catalogue and of the event's other races.

Formula variable Time

Where: race form, Distance and track (advanced setting)

The name of this distance in the seeding and combined standings formulas: “t500”, “t1500”… A formula “t500 + t1000/2” uses these names.

Suggested value: “t” followed by the distance.

Track length (m)

Where: race form, Distance and track

The length of one lap. Empty: the context's track (the event's discipline), otherwise the template's (400 m in long track, 111.12 m in short track in the examples), otherwise the catalogue's, otherwise another race's; with nothing, FINISH uses its session's track. The default value is shown under the field (“Empty: 400 m (context: Long track)”).

Refused: 0 or less, or more than 10,000 m.

Start line (m)

Where: race form, Distance and track

As in FINISH: the distance from the start to the first crossing of the finish line (1500 m on 400 m: 300 m). 0: start on the finish line. Empty: the catalogue's for the same track and distance, otherwise computed: the remainder of the distance divided by the track.

Refused, with the expected value: a line outside [0, track[, greater than the distance, with no known track, or that does not leave a whole number of laps after the first crossing (“1500 m on a 400 m track: the start line must be 300 m from the finish (first crossing), not 250 m.”).

Under the oval diagram, the preview says what FINISH will receive: “1500 m on a 400 m track: start 300 m from the finish → 3.75 laps, first crossing after 300 m. Finish 56 m after the track zero (middle of the bottom straight); start 156 m after the zero.”.

Suggested values: the computed line and 0.

Finish line (m after the track zero)

Where: race form, Distance and track

Where the finish line is, in meters after the track zero (the middle of the bottom straight), in the direction of racing. 0: at the zero. In long track, usually 56 m, except the 1000 m and pursuits (0). Empty: the one of the template's race type, otherwise 0. Must be between 0 and the track length.

The oval diagram places the zero (dotted), the finish, the start (the finish minus the start line, brought back into the lap: 56 − 300 + 400 = 156 m) and highlights the partial first lap; the legend gives each position.

Form: heat names

Heat names

Where: race form, Heat names

The naming pattern for this race's heats. It is written with tokens: each token moves with ◀ ▶ and is removed with its cross; the Add list puts one at the end. The pattern can also be written as text, with elements in braces:

TokenTextValue
Text(as is)Prefix, separator, suffix; spaces count
Event{epreuve}The race name
Block no.{bloc}The heat's number in the schedule (Position: in the round); empty without a schedule
Distance{distance}The meters, without a unit: write “{distance} m”
Gender{genre}“Femmes”
Category{categorie}The race's category
Round{ronde}Position the name of the round
Group{groupe}“G1” (heats raced together)
Number (1, 2, 3){numero}, {numero:2}The heat's rank in the race (in its round in Position); “:2”: two digits (01, 02…)
Letter (A, B, C){lettre}A, B… Z, AA, AB…

The preview shows the result on the race's actual heats (“Its 8 heat(s): …”), otherwise on an example. Empty: default naming (“Pair 3”, “Heat 4”, “12A”). Examples: “{distance} m {genre} — P{numero:2}” → “1500 m Femmes — P03”; “{bloc}{lettre}” → “7C”. The name is cut at 50 characters; an unknown token stays as text; “{{” and “}}” write a brace.

The pattern is applied when heats are generated, after the schedule is saved and on request (Rename heats), never to a heat that has started or been raced, nor to a heat named by hand.