Settings
The computer's settings: how EVENT completes and imports the timing .LIF files, how it ranks the overall standings, and which database it works on. Changes apply immediately; there is nothing to save.
The window opens with the header's Settings button, or with one of the three status bar buttons, which open it directly on their tab.
Each timing system writes one .LIF file per race into a folder. One folder per technology: the folder a file comes from tells which column of the overall standings receives its time. An empty folder is not used.
Green: the folder exists. Red: it does not exist, or cannot be reached for now.
ImportWatch the folders: import a new or modified file automatically3
Also save the race and its laps
- The four tabs.
- One folder per technology, green if it can be reached, red otherwise.
- Monitoring: automatic import of new or changed files.
Current event
Where: Settings, first tab (and the “Event: …” button in the status bar)
A .LIF file reports a race; it does not always say which competition it belongs to, nor on which track it was raced. These fields complete the files imported into the overall standings.
Competition
Where: Settings › Current event
The results from all folders are imported under this name, whatever name each timing system gave to the event. Empty: the name written in the file (the “Complete” format of FINISH).
Discipline
Where: Settings › Current event
The discipline of races imported from a file that does not carry it (“Long track”).
Track length (m)
Where: Settings › Current event
The distance between two split times. 0: unknown (only the final time of a file without the complement is imported).
Start line (m)
Where: Settings › Current event
The distance from the start to the first crossing of the finish line. 0: calculated for each race (the remainder of its distance divided by the track length: 300 m for a 1500 m on 400 m).
The discipline, track and start line are used only for a file that does not carry them: FINISH's “Complete” format writes them, with each athlete's distance, gender and category.
Sport
Where: Settings › Current event, Saved races
Written with each imported race (viewable in the History module).
Venue
Where: Settings › Current event, Saved races
The place, also written with each imported race.
.LIF folders
Where: Settings, second tab (and the “.LIF folders” button in the status bar)
Each timing system writes one .LIF file per race into a folder. You need one folder per technology: the folder a file comes from tells which column of the overall standings receives its time. An empty folder is not used. The button to the left of each field chooses the folder; a network folder (\\computer\share) is fine. The field is green if the folder exists, red if it cannot be found or reached for now.
Transponder
Where: Settings › .LIF folders
The folder for files from transponder (chip) timing: their times go into the “Transponder” (TR) column.
Photocell
Where: Settings › .LIF folders
The folder for photocell files: “Photocell” (PC) column.
Photo finish
Where: Settings › .LIF folders
The folder for photo finish files: “Photo finish” (PF) column.
Manual timing
Where: Settings › .LIF folders
The folder for manual timing files: “Manual timing” (MAN) column. Manual times can also be typed into EVENT, lap by lap (overall standings tiles).
Watch the folders: import a new or modified file automatically
Where: Settings › .LIF folders, Import
When ticked, EVENT imports each new or changed file as soon as it appears. A file is imported once; it is imported again if it changes (a race whose standings are corrected is rewritten by the timing system). The folders are also reread every 15 seconds, for network folders. Monitoring works whatever module is shown; the status bar says “.LIF folders: 3 watched”.
Also save the race and its laps
Where: Settings › .LIF folders, Import
When ticked, each file also fills the Races and Laps tabs of History. When unticked, only the overall standings are filled.
Import now imports the new or changed files right away; Import everything again forgets what has already been imported and takes all the files in the folders again, after confirmation (times already there and identical do not change). The import status is shown underneath.
Overall standings
Where: Settings, third tab
How EVENT ranks the overall standings rows and what it takes from the .LIF files. The same display options are also in the Display menu of the event's overall standings.
Provisional time: preferred system
Where: Settings › Overall standings
Transponder, Photocell, Photo finish, Manual timing or Database. A row without an official time is ranked with the time of this system; if it is missing, with the time of another one. This time is called provisional (in italics) until an official time is selected.
One row per athlete
Where: Settings › Overall standings
Ticked: only each athlete's best row is kept. Unticked: one row per race of the athlete (useful when an athlete raced the same distance twice).
Ties: dense positions (1, 1, 2)
Where: Settings › Overall standings
Ticked: after two tied first places, the next one is 2nd. Unticked: it is 3rd (1, 1, 3).
Import the split times
Where: Settings › Overall standings, .LIF file import
Also imports the intermediate times (at each lap), not only the final time. The track length must be known (in the file, or Track length).
Import the annotations (DNF, DQ, DNS…)
Where: Settings › Overall standings, .LIF file import
Takes the officiating codes written by the timing system into the Annotation column.
Also keep as the official time (if empty)
Where: Settings › Overall standings, .LIF file import
The imported time also becomes the row's official time when it does not have one yet. An official time already there is never replaced by the import.
Replace the times already there
Where: Settings › Overall standings, .LIF file import
Ticked: a file corrected by the timing system updates the time in its column. Unticked: the time already there is kept, and the row is flagged in the log.
Database
Where: Settings, fourth tab (and the database button in the status bar)
“This EVENT session uses”: this computer's database or a network server.
- The local database
- A PostgreSQL engine installed with FINISH or EVENT and reserved for ChronoFEED: nothing to configure. FINISH and EVENT installed on the same computer share this engine and this database. Its password is created during installation and kept encrypted by Windows: nobody needs to know it. Uninstalling the program does not delete the data.
- A network server
- When several computers work on the same event (EVENT in the race office, FINISH at the timing desk), all of them connect to the same PostgreSQL server on the venue network: server address, port, database, account, password; Test the connection, then Use this server. You then need to close EVENT and restart it. Return to the local database does the opposite; a procedure explains how to install a PostgreSQL server.
Check the common data over the internet at start-up
Where: Settings › Database, Common data
When ticked, EVENT checks at launch whether Technofeed has published new common data (countries, sports, venues, tracks, clubs, federation templates…) and installs it. What was added locally is not touched. The same update can be done on request through .
Results server
Where: Settings › Database, ChronoFEED results
The address of the server of the worldwide results database, read by the ChronoFEED
performances button. Empty: the usual address, https://resultats.chronofeed.ca. An address that does not start with
https:// (or http:// for a test server) is refused. Only identifiers computed on this computer are sent, never a
name or a date of birth.