Event workspace
The Event module, when an event is open: a banner that names it and links it to FINISH, then its modules in the usual order of organizing, from the races to the standings. On the left of the window, the log follows everything that happens.
- The event's name and type, and under it the status of the exchange with FINISH through the database.
- Exchange with FINISH through the shared database.
- Exchange with FINISH through files.
- The template (the rules) and going back to the list of events.
- The modules, in the order of organizing.
The banner
The title gives the name and the type: “Coupe Hollywood longue piste (Time)”, “Omnium Hollywood courte piste (Position)”. To its right, the Publish ON / OFF switch. Under the title, a line sums up the last exchange with FINISH through the database (“FINISH: 12 heat(s) sent, 0 unchanged.”, “FINISH read again at 13:42:05: up to date.”).
Publish ON / OFF
Where: event banner, to the right of the event name
A sliding switch, like those of FINISH: Publish ON (green) or Publish OFF (red). It decides whether the results of this event may be published to the ChronoFEED results server (Publish official results to ChronoFEED…).
- Publish ON: publishing is allowed (it only sends official, saved results).
- Publish OFF: nothing goes to the server. The Outputs menu item is greyed out, with the tooltip “Publishing disabled for this event (Publish OFF)”, and any attempt is refused with a message, without any call to the server. Choose it for a test or trial event, so that its results are not mixed with real ones.
The setting is specific to each event and saved with it in the database: every computer that opens the event sees it, and it keeps its last value when you close and restart EVENT. An event that has never been set (new event, copy, event from before this switch) opens with the last value chosen on this computer (ON as long as you have never switched it off). Each change from ON to OFF or from OFF to ON is written to the event log (who, when, before, after).
Send to FINISH
Where: event banner (and File menu)
EVENT and FINISH on the same database: each heat of the event creates or updates its race in FINISH, with no file. In FINISH, you load it through . The summary is shown (“FINISH: 12 heat(s) sent, 0 unchanged.”) with, if relevant, the heats that have already started (“2 already started: can no longer be changed.”) and the removed heats.
A heat that has started (a start given in EVENT or in FINISH, by any technology) is no longer changed by the sending.
Sending also writes the heat order: the running order of each heat in the event (1, 2, 3…, all races
together), according to the Schedule tab, then the order of the races and heats of the Composition — the same order as the .cfevent
file of the whole event. FINISH sorts its list in this order. When the order changes (schedule saved, heats moved, regeneration, races
reordered), it is rewritten two seconds later if the event is linked to FINISH, without sending the heats again; the banner says so (“Heat
order given to FINISH at 10:42:15: 3 heat(s) reordered.”). A heat loaded or started in FINISH keeps its rank; the others take the remaining
ranks, without duplicates.
Read FINISH again
Where: event banner (and File menu)
Compares EVENT's heats with FINISH's races:
- before the start, an athlete added, removed or moved in FINISH comes back into the EVENT heat;
- after the start, the heat becomes “raced” and its results come back into EVENT;
- a heat changed on both sides opens the “Differences between EVENT and FINISH” window: for each heat, the two line-ups and the choice Keep EVENT (the heat is sent again as it is in EVENT), Take FINISH (FINISH's athletes go into the heat) or Later (nothing changes; the difference will come back). Keep EVENT for all, Take FINISH for all, then Apply. Nothing is settled without you.
Reading again also happens automatically: when the Heats tab opens and every 30 seconds while the workspace is displayed, for an event already sent through the database. A difference already shown does not reopen the window at each automatic reading; the button, however, shows everything. With no difference: “FINISH and EVENT agree: nothing to take over.”
Each reread also updates the heat order given to FINISH (see Send to FINISH); the banner counts the reordered heats (“FINISH read at 10:42:15: 3 heat(s) reordered.”).
Automatic sending
Where: event banner
When ticked, each heat changed in EVENT is sent automatically to FINISH, two seconds after the last action (a series of drag-and-drops makes only one sending). Ticking the box sends right away. The setting is kept on the computer.
Export to FINISH…
Where: event banner (also File menu and Results tab)
Writes the session file that FINISH opens. The “Export to FINISH” window asks for:
- What
- “Whole event”, one race (“Race: 1500 m Femmes”), one round in Position mode, or “Selected heats” (a list of boxes, with the status of each heat: planned, exported, raced, results; “Tick at least one heat.”).
- Format
- .cfevent (recommended): everything goes across — colors, positions, helmets, language, rule, seeding. .evt: for FinishLynx and compatibility; colors, language, times of day and performances are lost, and this format has no field for the track (a warning says so if the races are on different tracks).
- Transponders by lane Time
- FINISH then assigns the transponders by the lane's usual code.
The file also tells FINISH the sport and discipline of the event and the timing settings its races require: races that share the track (same group G1…, quartets) require multiple races and grouped automatic loading; otherwise one race at a time. FINISH compares with its session and offers to apply them (Settings required by the event). Send to FINISH passes the same through the database.
Then Export… asks for the file. Exported heats become “exported”; a raced heat keeps its status. The message says “12 heat(s) and 38 athlete(s) written to coupe-hollywood.cfevent.”.
Import results
Where: event banner (also File menu and Results tab)
Fills the heats with the results from FINISH. The “Import results” window first reads, without writing anything:
- Read .LIF files…: the “Complete” .LIF files written by FINISH (with the athletes' reference);
- Read the database: the overall standings in the database, when EVENT shares FINISH's database.
It then shows the heats that receive results, the entries made by hand that differ from FINISH (heat, athlete, entered, FINISH) and the notes. Also replace results entered by hand (otherwise they are kept), then Import. FINISH codes (DNF, DQ…) become those of the event template; an entry made by hand is never replaced unless the box says so.
Template…
Where: event banner
Opens the editor of the event template: categories, officiating codes, point tables, performance sources, start colors, mode parameters. It opens directly, without a password.
Change event…
Where: event banner
Goes back to the list of events in the context to open another one. Opening another event removes this one's broadcast races from the scoreboards (Broadcast).
The modules
The modules follow the usual way an event is organized: you choose the races, enter the athletes, get their performances, compose the heats, then come the schedule, the results and the standings. The order follows the usual organization; you can go back to any module at any time: none is locked or greyed out because an earlier step is not done, and a module that lacks data says so and explains what to do. Each module loads the first time it is opened and refreshes when you come back to it if another module has changed what it depends on. Only what the event's mode uses is shown: Performances exists only in Time mode, Results only in Position mode.
Races
Where: module 1 of 7
The list of the event's races and their record (distance, track, model, point table, heat names, broadcast). See Races.
It comes first: there you choose the races to hold, and the entries import uses them to know which athlete is entered in which races.
Entries
Where: module 2 of 7
The entries and their races: import, statuses, categories, groups, bibs. See Entries.
It comes next: once the races are known, you get and update the athletes there, and see who is entered in which races.
Performances Time
Where: module 3 of 7
The entries' past performances: seeding calculation, venues allowed and excluded, SSR and ChronoFEED performances, corrected times, joker. See Performances.
It comes after the entries, because it works on the entries, and before the line-up, because performances are used to form the groups.
Line-up
Where: module 4 of 7
Composing the heats, in both modes: Line-up view (athlete and heat cards, drag and drop), heat formation settings Time, round plan, groups and standings Position. It was the Heats tab. See Line-up.
It comes after the performances: the groups and heats are composed from them.
Schedule
Where: module 5 of 7
The program: order, numbers and planned times of the heats, sessions and breaks. See Schedule.
Once the heats are composed, you set their order and times.
Results Position
Where: module 6 of 7
The results heat by heat: import, entry, correction, making official. See Results.
Then the heats are raced and their results come in. This module is shown only in Position mode: in Time mode, the results are in the overall standings (Standings module).
Standings
Where: module 7 of 7
The combined standings (formula, points, converted times) and, in Time mode, the overall standings lap by lap and technology by technology.
It comes last: it brings together the results of all the races.