Long track competition: the Coupe Hollywood

1. Load the competition

Two paths, depending on whether FINISH shares EVENT's database or not.

Through the shared database (recommended)

1. A single database

   FINISH and EVENT are connected to the same server (SettingsDatabase). In EVENT, Send to FINISH has written the heats: “FINISH: 110 heat(s) sent”.

2. Load

   FileLoad a competition from the database…. Type “hollywood”: the row Coupe Hollywood longue piste shows its races by state (white dots: not raced); the breakdown by distance “500 m (40)”, “1000 m (38)”, “1500 m (32)”. Load.

   The strip shows “Coupe Hollywood longue piste”. The List (waves) tab shows the 110 races in EVENT's order, with their athletes in the colors of their position (white, red: the color scheme sent by EVENT, made active), the track of each event (400 m, start line 100, 200 or 300 m) and the Group column (G1, G2…). Athletes missing from the database are added to it, without duplicates (log: “Session athletes: …”).

If the competition has several events, the window Choose the events to load lists them (500 m Women, 500 m Men…): keep everything checked, or only yours if another FINISH times the rest (Choose the events…). The 110 races are numbered 1, 2, 3… in the order of EVENT's schedule, as after importing the .cfevent file; if EVENT changes the schedule, the list follows at the reread.

Through a file

• .cfevent (EVENT, Export to FINISH…): FileOpen a session…. Check FileAutomatic synchronization: when EVENT rewrites the file (a late entry added), FINISH rereads it between two races (merge: races that have started do not change).
• SpeedSkatingResults .json: on opening, the long track Timing mode window: Olympic style (pairs), Automatic loading of races, the track; Confirm.

2. Check the race flow

Configuration tab (Olympic style sets it):

• Multiple races; automatic Loading, Number of races to load 1, Grouped: a pair on its own, or the two pairs of the same group, loaded and closed together;
• Same start unchecked: one start per pair;
• Laps completed or time elapsed and a Delay before closing of a few seconds;
• Auto-assignment if your transponders have a start position (otherwise the usual codes in the file are enough).

The status bar reads “Multiple races”, “Auto-load ON · 1”. The first race changes to “Loaded” (yellow).

3. Time a pair

1. The race commands.
2. The timer and the laps to go.
3. One row per skater, one tile per passing at the line.

1. The start

   The starter fires: the start gun connected to the decoder starts the loaded race with the lowest order.

   “In progress”; the Starts tab records “500 m Women — P03”. The TABLEAU display shows the timer.

2. The passings

   In the 500 m: 100 m, then a full lap. Each passing at STA fills the skater's tile; at loops L1 to L3, the split times.

3. The finish

   Both have done 1.25 laps: the race is “Finished”, the rows gold and silver, “Closing in N s”.

   Then it becomes raced: the .LIF is written, the race leaves the screen and the displays, the next pair loads. EVENT reads the result in the database.

4. Two pairs on the track (1000 m)

   “1000 m Women — G1 P01” and “1000 m Women — G1 P02” carry the same group: they are loaded together (positions 1/2 and 3/4, four colors). Each start starts the next waiting one. The first to finish “waits for the group”; when both are finished, a single countdown closes them together.

4. Incidents

5. At the end of the day

• History › Races: the races of the Coupe, “Raced”; Detail and report… for the control room.
• History › Overall standings: the times by technology; the official time is set in EVENT.
• Exit: the races still on screen are put away; with the backup on closing, the database is copied.