Timing report
The FIS Timing and Data Technical Report: what it holds, where every line comes from, and the FIS format it is sent in.
What it's for
Every FIS race needs a Timing and Data Technical Report Alpine (the TR). Race Bureau writes it in the FIS XML format, Timing Report XML Description v1.17, and prefills it from the race: event data, the Technical Delegate, the timekeeper, the devices, the synchronisation check, the first and last starter of each run and the best time. Open it under Results & publish › Timing report.
The report is FIS's, not Race Bureau's: nothing in it is designed by us, and the times in it are the times the devices recorded. See Units for how times are written.
Before you start
- The ACTIVE RACE picked in the header. The report is per race.
- The equipment preset filled in once under Settings › Timing Report (timekeeper, System A and B timers, start device, photocells). It is remembered for every later race.
- The synchronisation done on the desk (Sync, then the check impulse one minute later). A and B must agree within 0.001 s.
Steps
- Open Results & publish › Timing report. The header names the active race.
- Check Event data: dates, gender, codex, the Technical Delegate from the event.
- Check Timekeeper & Devices (step 2). Change anything here and press 💾 Save as my preset to keep it.
- Under Extract & synchronization press Extract from the race file(s) to fill the run boxes (first starter, last starter, best time) from the timing data, and fill in the synchronisation times.
- Say 1 run or 2 runs.
- If any result did not come from System A, add a line per bib under the table: BIB, Run, Reason, Time taken from. Leave the table empty when every result is System A's; the report then says Allresults SystemA="yes" for each run.
- Press 💾 Save report to keep it on the race, then 💾 Save DRAFT XML or 💾 Save FINAL XML.
- Email the final file to results@fis-ski.com. The subject is the file name without .xml.
What success looks like
The saved XML opens in the FIS program without a warning, every time of day has four decimals, and the A and B synchronisation check differs by 0.001 s or less.
If something goes wrong
- This event has no races yet: add the race under Set up › Event info.
- The extract is empty: the run has no timing data on this race. Time it, or import it with Import a run.
- A time of day shows five decimals: it should not. Times of day are truncated to 1/10 000 s. Report it.
Related
- Previous: Release and protest windows
- Next: Penalty calculation
- How it fits: A FIS race, from the calendar to Accepted by FIS
- For the TD: Timing report and penalty check
- Units