File, Session, Tools and Help menus
The four menus of the header: the session and its files (File), its configuration and the timing mode (Session), the photo finish, the records and the database (Tools), then help, the license and the language (Help).
- File: the session (open, load from the database, synchronize), athlete import, .EVT output.
- Session: the session configuration, the timing mode, race management.
- Tools: FinishLynx, the records, the backup and database aggregation.
File
Where: header, on the right
The session menu: the competition being timed today and the list of its races. The races come from a file (written by EVENT or other management software) or from the shared database.
Open a session…
Where: File
Reads a session file and makes it the new race list. Recognized formats (offered together, “Session files”, then one by one):
| Format | Written by | Use |
|---|---|---|
.cfevent | EVENT (“Export to FINISH…”) | Everything: positions, helmets, transponders, languages, start position colors, track of each event. |
.json | SpeedSkatingResults | Long track: pairs, mass starts, pursuits. FINISH then asks for the long track mode. |
.evt | photo finish and management software | Mostly short track. The distance is the first number in the event name. |
.xlsx, .xlsm | Excel | Everything, training included: first sheet = athletes and options, then one sheet per race. The old .xls format is not read. |
It is a new session, even when reopening the same file: the races in the tabs are closed (loaded → not raced; in progress or finished → raced, standings saved), the list is emptied, then the file fills it. Races that the database knows as raced stay raced. Athletes who are people go into the athlete database, without duplicates (Add the session's athletes to the database). The file is remembered: Refresh and automatic synchronization then reread it by merging.
The window opens in the Session files folder.
Load a competition from the database…
Where: File
Takes the session from the database instead of a file: the list of competitions in the database (deleted races excluded), with a search (all words, ignoring case and accents) and, for each competition and then for each distance (“500 m (40)”), the number of races in each state, with the colored dots of the race list. Load makes this competition the session, like an opened file: races in the tabs closed, list replaced. A race already raced on this computer stays raced.
This is how FINISH takes the races sent by EVENT when both share the same database: each EVENT heat is a race, with its positions, helmets, transponders, languages, colors and the track of its event.
The race order is the one EVENT gives through the database: the running order of its schedule (all events together),
the same as after importing the .cfevent file of the whole event. The list therefore has the same numbering (1, 2, 3…) and the same
“next race” as with a file, even if this computer has already written its races. When EVENT changes the schedule, the races in the list take
their new order at the next reread; a loaded, running or raced race keeps its own, and an order changed by hand in the list is kept.
If the competition has several events, the window Choose the events to load opens before loading: only the races of the checked events enter the list.
Then Refresh rereads the competition in the database (merge), and automatic synchronization, if checked, rereads it when EVENT has changed it. No file is remembered and nothing is reread on its own at the next launch.
See the scenario Long track competition.
Choose the events…
Where: File (active when the session comes from the database); also opens on its own after Load a competition from the database… when the competition has several events
FINISH discovers the events of the competition in the database: those EVENT published with each race (name, distance, gender, category), in program order; a race that does not come from EVENT is grouped by its distance (“500 m”). Each event has a check box, its number of races and their states (same dots as the race list).
- The events, in EVENT's program order. “new”: appeared in the database since the last choice; it is not loaded until it is checked.
- All checks every event: the events EVENT adds later will be loaded too. None unchecks everything.
- Load: available when at least one event is checked.
The choice is remembered for the competition on this computer: loading the same competition again uses it. Two FINISH can thus share an event (women on one, men on the other). The first time, all events are checked; a competition with a single event does not open the window.
Reopened with FileChoose the events… during the session: the races of a checked event enter the list, at their place in the program; those of an unchecked event leave it, except a loaded, running, finished or raced race, which stays (a message names it). Nothing is deleted from the database. When EVENT adds an event that is not in the choice, the log says so: “1 new event(s) in the database, not loaded: 1000 m Men. File → “Choose the events…” to add them.”
Settings required by the event
Where: opens on its own after Open a session… (.cfevent) or Load a competition from the database…
An event prepared in EVENT says how it must be timed. If the session is not set that way, the Settings required by the event window shows it: “The event requires: Multiple races + grouped automatic loading + one start per race”, “The session is in: One race”, the reason (for example quartets: the two races of a group G1 share the track) and the list of settings that differ (Setting, Requested, In the session).
- Apply these settings
- The default button (Enter): the session takes the requested settings, then automatic loading loads the races (a whole group for quartets).
- Keep my settings
- Nothing changes (Esc). You can set the session later in the Configuration.
Only these settings can change: Timing mode (One race / Multiple races), Auto-load, Grouped, Number of races to load and Same start. Transponder assignment, the decoder, the track lines and loops and broadcasting stay those of this computer. “One race at a time” is already met by multiple races with 1 race to load.
If the sport or the discipline of the event are not those of the session, a warning says so; FINISH does not change them (if needed, change them in the session configuration). The choice is written to the log. The question is not asked again at each reread; it comes back if the event changes its requirements or at the next session opened. A file from an older EVENT, or in another format, changes nothing.
New session…
Where: File
Not available yet: a message says so. To time without a file, create the races by hand (Add in the list) or start an emergency race.
Synchronize the session
Where: File
Not available yet. To reread the file right away: Refresh in the List (waves) tab.
Import athletes…
Where: File (also in History › Athletes)
Opens the wizard for importing athletes from an Excel, CSV or JSON file: mappings, preview, matching with the database, import. See Import athletes.
Load finished races
Where: File (check box)
Checked: the race list also shows the races raced during a previous session (grayed out). Unchecked: only the races raced during this session remain visible. It is the same setting as the list's Show races already run (greyed out) box and as Load races even if they are already in the DB.
Automatic loading
Where: File (check box)
The same setting as Configuration › Mode › Automatic loading and as the Auto-load box in the status bar. It also decides whether the file is reread at launch: without it, FINISH does not reread the last session's file at startup (the list stays empty until “Open a session…”).
Automatic synchronization
Where: File (check box)
Regularly rereads the session file (EVT, JSON, Excel, .cfevent) that the management software rewrites with the new races.
The reload waits until no race is started and unfinished (“Reload pending: a race is in progress.”). It is a
merge: a new race is added; a race that is only in the list and came from the file is updated; a race that is loaded, in progress,
finished, raced or edited by hand is never touched.
A session loaded from the database is reread the same way: at each interval, FINISH checks whether EVENT has changed the competition (published races, schedule order, races added or removed); if so, log “The competition changed in the database: it will be reloaded as soon as no race is in progress.”, then the merge, with the chosen events. A race changed by hand here still takes its new order (only the order). What this computer writes itself triggers nothing.
Synchronization interval
Where: File (“Synchronization interval: 3 min…”)
The label shows the interval between two reloads; a click opens the input (a duration: “30 s”, “3 min”; a number alone counts as minutes).
EVT output
Where: File
The submenu for exporting in .evt format (the “lynx.evt” of photo finish software).
Export to .EVT…
Where: File › EVT output
Writes an .evt file with all the races in the list, in order, and their athletes. This is the file to give to
FinishLynx so that its races carry the same names as in FINISH (see FinishLynx). What is
written is set in Settings › EVT export. Whatever has no place in the format is lost
(state, pair, group, loops, min/max, elimination, bell…); the session log reports each case (race name changed, athlete without a
reference…).
Each athlete has a unique ID in it (2nd field of their lines), the same in the list at the top and in all their races: FinishLynx recognizes the athlete by this ID. It is their bib; if bibs repeat (mass start, where the bib is the position in each race: 1, 2, 3… for the women, then 1, 2, 3… again for the men), all athletes are numbered 1, 2, 3… in race order, and the log says so. The lane (3rd field) remains the start position.
With venue
Where: File › EVT output
Not available here yet: the venue name is set in Settings › EVT export.
Athlete with 8 fields
Where: File › EVT output
Not available yet: an athlete line always has its eight fields.
Exit
Where: File, at the bottom
Closes FINISH. The races in the tabs are put away (loaded → not raced; in progress or finished → raced), then FINISH gives a few seconds to the broadcast, the overall standings, the passings and the laps to be written. With A backup when FINISH closes, the database copy is made afterwards.
Session
Where: header, on the right
The context of the session and the way of timing.
Session configuration…
Where: Session
Opens the Timing session configuration window: activity (Competition, Training, Demo), sanction level, sport, discipline, country, venue and track, free session. Opened from here, Cancel does not quit FINISH.
Timing mode (decoder)…
Where: Session (also in the Configuration module)
Opens the Timing mode window: decoder, manual, hybrid or photocells, the equipment and its connection.
Race management mode…
Where: Session
Shows the Configuration tab of timing, Mode pane: one race, multiple races, time trial or automatic.
Timing options…
Where: Session
Shows the Configuration tab of timing, Race flow pane.
Favourite races…
Where: Session (also Settings › Files and tracks, and the list's menu)
The race templates: the discipline's races supplied with FINISH and your favorites. They are used by the
emergency race, the “Use” button of the race sheet and when reading
SpeedSkatingResults and .cfevent files (loops, min/max, lap forecast). For each one: name, distance, track length,
start line (m before the finish), number of laps, finish loop, minimum and maximum lap, acceleration and top speed (expected times
per lap displayed), bell ratio, elimination (formula, or Elimination rule of the federation or one of yours, read back in plain words; the … button next to it opens the elimination rules), final time and which athlete counts for a
team. A discipline race that you edit becomes a favorite that replaces it; deleting that favorite restores the supplied value. The
window warns when laps × track does not give the distance.
Elimination rules…
Where: Session (also Settings › Files and tracks, and the “…” button in favourites and the race sheet)
The elimination rules of the session's discipline: the federation's, received with the shared data (view, duplicate), and yours (“My rules”: new rule, duplicate, edit, delete), with the same grid editor. Updating the shared data never touches your rules. Every control and message: Elimination rules and grid editor. Step by step: Create my own elimination rule.
Coaches (ChronoFEED-COACH)…
Where: Session
The coaches' ChronoFEED-COACH tablets: the Accept ChronoFEED-COACH option, the coaches' access requests (accept all, some or none), the tablets and their athletes (withdraw an access), the log. Each control: Coaches (ChronoFEED-COACH). Step by step: Pair a coach's tablet.
Tools
Where: header, on the right
Finish-Lynx
Where: Tools
The photo finish: FINISH receives the final times of the FinishLynx software over the network. Three commands, the same settings as Settings › FinishLynx.
Connection (server active)
Where: Tools › Finish-Lynx (check box)
Checked: FINISH listens on the configured port; FinishLynx can connect to it and send its results. See FinishLynx server active.
Server (IP address, port), race field…
Where: Tools › Finish-Lynx
Opens Settings › FinishLynx.
Debug
Where: Tools › Finish-Lynx (check box)
Checked: each line received from FinishLynx is written to the log. To see at which position the race name arrives.
Update the records (SpeedSkatingResults)…
Where: Tools
The Records window: the records in the database for the session's discipline. For each race in progress, FINISH broadcasts to the displays those for its distance and gender (world, Olympic, of the chosen country, of the session's track) and, with each athlete, their personal and season bests.
- Update the records (SpeedSkatingResults): check the lists (World records, Olympic records, National records of country: with the three-letter code, Masters records), choose the Track (SpeedSkatingResults):, then Records of this track, Personal bests of the session's athletes, Absolute best time of the track if needed, and Update. A bar shows the progress; Cancel stops (what has been written stays). The site is queried only in long track.
- Add a record by hand: type, distance, gender, category, time (“34.03” or “1:06.42”), holder, country, date, venue (for a track record: the name of the track, as in the session configuration); Delete the selected record.
After an update, the races already loaded receive the new records and are republished; each race's Records tab shows them.
Database backup…
Where: Tools
Aggregate from another database…
Where: Tools
Copies into this computer's database the raced races of another FINISH database of your organization (another computer, the club server, an archive): their times, their laps and their standings. The chosen database is only read.
- Known databases: New database, name (recorded as the origin), server address, port (5432; 54329 for the local database of another computer), database, account, password (kept encrypted by Windows); Test the connection, Save, Remove.
- Aggregate from this database…: refused during a race; a question says what is going to happen, a bar shows the progress, Cancel stops after the race currently being copied. A report follows (also in the log).
No duplicates and nothing overwritten: running it again copies nothing twice, picks up races corrected since in the chosen database, and never replaces what was timed or corrected on this computer. Races in progress in the chosen database are left for next time.
Synchronise the database system files…
Where: Tools
Not available yet: a message says so.
Help
Where: header, the button
At the top of the menu: ChronoFEED-FINISH Help (F1: this help, at the section for the targeted item; see Context help) and ChronoFEED suite help.
Update shared data…
Where: Help
Downloads the shared tables published by Technofeed: countries, sports, venues, tracks, clubs, federations, annotation types… What was added locally is not touched.
Licence…
Where: Help
The state of this computer's license (trial, activated, expiry) and its activation.
About ChronoFEED-FINISH…
Where: Help
The version and build number. The title bar of the main window also shows them (“ChronoFEED-FINISH 2.0.17 (…)”).
Report a problem or suggest an improvement…
Where: Help
A window for writing to Technofeed: a text, annotated screenshots, attached files. Without Internet, the package is saved to be attached to an email. Technofeed acknowledges receipt and lets you know, in your language, when the version containing your request is published.
A box, ticked by default, also attaches the installation topology and settings: the ChronoFEED software on each known computer (under an alias, “Poste 1”, never its name), their versions and language, their links and their status (broadcast, Redis, COACH, clock offset), the equipment, the operating system and the database, and the settings useful for diagnosis. Only what the software already knows: no network scan. Never a password, an email address, nor any athlete or race data. Preview shows the exact text that is sent; Do not attach (or unticking the box) removes it.
Contact support…
Where: Help, just after “Report a problem or suggest an improvement…”
A live written conversation with a ChronoFEED support agent. The window leaves FINISH usable and never comes to the front by itself: a message received does not disturb you during a race.
- Looking for an agent
Only when the window opens (never at startup or in the background), FINISH looks for an agent online in the interface language, for this program and, if it knows it, for your sport: 5 seconds at most.
- An agent in your language
“An agent is online.” Enter your email address (required, for the rest of the conversation) and, if you wish, your name. The conversation starts with your first message; Ctrl+Enter sends it.
- An agent in another language
“An agent is available in English. Accept help in English?” Accept opens the chat in that language; No, write a request opens the feedback window.
- During the chat
Your messages on the right, the agent's on the left, with their first name. A lost connection is announced; your messages wait and are sent when the connection is back, only once. Close the conversation ends it.
The three tools. Nothing is sent without your consent: each tool first shows a preview, with Send and Cancel. When the agent asks for one, a banner says so, with View and send… and Ignore: you are always the one who sends.
- Screen clip…: a window of this program or of another program of the suite open on this computer, never the whole screen. Annotate and mask… lets you write on it, black out what must not be sent and keep only an area (Whole image goes back to the full image). An image can show athletes' names: mask them if needed.
- Settings…: the settings useful for diagnosis, with secrets masked; one checkbox per line to remove some.
- Topology…: the ChronoFEED programs of the installation, their versions and their links, each computer under an alias (“Poste 1”); you see the exact text.
The fallback. No agent free, chat closed, server unreachable or too slow, licence refused, limit reached, or no reply from the agent for 2 minutes: the feedback window (Report a problem or suggest an improvement…) opens instead, without an error message, already filled in with what you wrote, and it says why at the top. Your request goes that way; the answer reaches you by email.
Language
Where: Help, at the bottom
The interface language (French, English…). The choice takes effect at the next launch of FINISH.