Timing data technical report ver 7 2
Download
1 / 63

TIMING & DATA TECHNICAL REPORT ver 7.2 - PowerPoint PPT Presentation


  • 70 Views
  • Uploaded on

TIMING & DATA TECHNICAL REPORT ver 7.2. Timing & Data Technical Report is required for all scored events – USSA & FIS. It is also required for USSA non-scored Championship events, e.g. U12 Championships, Masters Championships.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' TIMING & DATA TECHNICAL REPORT ver 7.2' - nigel-horn


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Timing & Data Technical Reportis required for all scored events – USSA & FIS. It is also required for USSA non-scored Championship events, e.g. U12 Championships, Masters Championships.

(This part of the presentation addresses the paper copy of the report which can only be used for non-FIS events.)


Event identifiers
EVENT IDENTIFIERS

USSA Transmittal #:

Alpha character + 4 numbers assigned by USSA and used only for non-FIS events.

FIS CODEX #:

FIS events use 4 numbers assigned by FIS; FIS-supplied software must be used to generate the report and to use the FIS online reporting system. Software also generates a PDF copy for signatures/required packets. (Details at end of presentation.)


Location:As listed on website

Event:* Type of race: DH, SL, GS, SG, AC

Event Name: As listed on website

Gender:* Ladies or Men

Date:Actual date of event

*“Check Boxes” enabled!


Equipment Identifiers

This information must be accurate; equipment must be currently homologated!

Sys Timer A

Sys Timer B

Start Gate

Finish Cell A

Finish Cell B

  • Brand Name

  • Model or Type

  • Serial Number

  • Homologation #





SOFTWARE / RESULTS VERIFICATION

Brand: Name of Software

Version: Version used by timing & results computers

Date: Date of version used – not date of event

Results = Tapes: Confirmation that assigned times = printed timing tapes


CONNECTIONS

How do we communicate signals/data from Start to Finish?

How is voice communication handled between Start and Finish?

  • Cable

  • Radio

  • Snowmobile

  • Ski Lift

  • Skier

  • ??


POWER ON & SYNCHRONIZATION

At what time is the run scheduled to start?

  • Is there a rule about Synchronization?

  • What is the minimum recommended warm- up time?

  • Why do you have to wait to synchronize?


Synchronization and Sync + 1 Minute

  • Are Systems A and B synchronized?

    • How close are they?

  • What is the maximum difference acceptable?

  • What about Hand Sync (Manual Timekeeping)?


First Competitor Quality Check

  • Is Net Time the same as A time-of-day difference?

    • How close are they?

    • Does Net Time agree with Official Results?

  • What is the B time-of-day difference?

    • Discuss the difference?

  • What about Hand Sync (Manual Timekeeping)?


Last Competitor Quality Check

  • Is Net Time the same as A time-of-day difference?

    • How close are they?

    • Does Net Time agree with Official Results?

  • What is the B time-of-day difference?

    • Discuss the difference?

  • What about Hand Sync (Manual Timekeeping) ?


First Run Summary

  • Why do we show Best run-time?

  • Why do we show the Bib #?


Second Run Sync +1 minute

  • Are Systems A & B synchronized?

  • Do the rules require re-synchronization between 1st & 2nd Runs?

  • Why do you think there was no Hand re-sync?


Second Run Summary

  • Notice First and Last racer data quality!


Race Summary

Were all Results from system A?If you answer “NO”, you must list any or all bib numbers – in all runs – where an assigned time was obtained from any system other than system A (indicate run).

WHY? List the reason:BatteriesSnow obscurationWire break

Photocell alignmentOther? (describe)

Data source for replacement system A time (resp. ACR 611.2.1)?What did you use?System BSystem CManual

NOTE: If Replacement Time (EET) calculated, include calculation worksheet(s) with this form. (Sent to TWG representative.)


Race Comments

  • What comments might or should be shown?

  • What should NOT be shown?


Certification

  • We certify that the timing and calculations of this event adhered to the USSA rules.

  • Any discussion on this?

  • Are we through now?


Sign Off

  • Chief T & C

    • Printed Name and NAT

    • Telephone nr.

    • Email address

    • USSA #

    • SIGNATURE

  • Technical Delegate

    • Printed Name and NAT

    • Telephone nr.

    • Email address

    • USSA #

    • SIGNATURE


Completed tdtr
COMPLETED TDTR

  • The Chief of Timing & Calculations is responsible for the accurate completion of this form.

  • The Technical Delegate is responsible for verifying the accuracy of the data.

  • Both officials must sign the form as their confirmation of the accuracy of the timing for the event.

  • A TDTR is required for ALL scored events.

  • A TDTR is required for ALL non-scored Championship events; e.g. U12, U14 and Masters Championships.


Online tdtr
ONLINE TDTR

  • Software that allows online filing is available

  • Data requirements are identical to paper form

  • Its use is required for all FISevents: Depending on connection, download time can vary – DOWNLOAD, INSTALL AND TEST IN ADVANCE OF YOUR EVENT!

  • It is available in (Windows, MacOS & Linux)

  • Available for review/download at:

    ftp://ftp.fisski.ch/Software/Programs/TimingReport/AL/

    Race result XML and TDTR XML files must be submitted prior to filing online TD Report!


TIMING & DATA TECHNICAL REPORT SOFTWARE *

Versions 2.1.2 / 2.1.3

*Please verify you are using the most current version of the software!

(Edited XML from prior season’s event used for this presentation.)


The new tdtr software program can be found on the fis ftp site
The new TDTR software program can be found On theFISFTP site.

Select OS & Download


Tdtr software installation
TDTR SOFTWARE INSTALLATION

Select Option & Continue


Tdtr software step 2
TDTR SOFTWARE, Step 2

Select Option & Continue


Tdtr software step 3
TDTR SOFTWARE, Step 3

Change

or

Accept

and Continue


Tdtr software step 4
TDTR SOFTWARE, Step 4

Select Storage Location

Continue


Tdtr software step 5
TDTR SOFTWARE, Step 5

Select Options

Continue


Tdtr software step 6
TDTR SOFTWARE, Step 6

Verify Preferences

Go Back to Change Preferences, Install or

Cancel


Tdtr software step 7
TDTR SOFTWARE, Step 7

Finish Installation & Launch Software


The software p1
The Software: P1.

Event Information as listed on applicable website for level of event

Officials’ names as listed on applicable website for level of event (name on FIS site may be different than that listed on USSA site, e.g. Randy Rogers on FIS and Randall Rogers on USSA!)





Prompt for new version after initial installaton devices

New Version Information (Uninstall/Re-install may be required.)


Options preferences timekeeper
OPTIONS/PREFERENCES: Timekeeper devices

Insert ALL “Timekeeper” Defaults & Save


Options preferences timing devices
OPTIONS/PREFERENCES/TIMING DEVICES devices

Select “Timing Devices” Default Choices & Save

Check for device updates!

This is not the same function as “NEW VERSION”


Options preferences program options
OPTIONS/PREFERENCES: Program Options devices

Insert ALL “Program Options” Default Choices & Save



Timekeeping equipment
TIMEKEEPING EQUIPMENT devices

Dropdown boxes for equipment brand and model selections

Homologation number automatically inserted

You must insert Serial Numbers!

Additional selections & continue

(Select “Other” if your software not listed.)




Select your connections
Select Your Connections devices

Drop down boxes make it simple!


Technical timing information
Technical Timing Information devices

Prior to “Finish”,

Software will prompt for all error corrections!


Summary of race all times from system a yes
Summary of Race: devicesAll times from system “A”? YES


Summary of race all times from system a no
Summary of Race: devicesall times from system “A”?NO

“NO” is selected; information required.

Can add / delete / select, as needed.


If no enter bib run select the reason
If “ devicesNO”, enter Bib, Run & Select the Reason

Drop-down Selections make it easy!

“Other” allows you to key in a reason.

“Add to List” inserts your keyed data.

Followed rules?


Outputs save pdf view xml save xml and email
OUTPUTS: devicesSAVE PDF / VIEW XML / SAVE XML and EMAIL

Select “Output”

Select your option –

“Save PDF” allows for TD’s review.


Option save pdf will save to location of your choosing
Option: SAVE “PDF” devicesWILL SAVE TO LOCATION OF YOUR CHOOSING


Print pdf saved as 2015al6623tr
PRINT “PDF” devicesSaved as: 2015AL6623TR

Print for TD’s review, signature and race result document packet copying

Must be signed by Chief of Timing & Technical Delegate

Note date & time stamp


Option view xml
Option: “VIEW XML” devices

This is the format of the file you will be transmitting to FIS.

[email protected]


Option save xml will save the transmission file to location of your choosing
Option: SAVE “XML” devicesWILL SAVE THE TRANSMISSION FILE TO LOCATION OF YOUR CHOOSING


Select auto send preferred option
SELECT “AUTO-SEND” devices(Preferred Option)

More data required!

Loading default information in “Program Options” will eliminate necessity to enter email address.



Save xml and
SAVE XML and… devices

You will be prompted for a “save” location!



Submitting the tdtr xml file

The [email protected] XML and the RACE RESULT XML files must be submitted before the TD submits his online TD Report.

After all the data is entered in the software:

- TDTR must be saved as PDF and printed/signed for result packets

- TDTR may be viewed as XML

- TDTR must either be auto sent or saved as XML

- Saved XML TDTR must be attached to an email and sent to

[email protected]

Errors? Corrections can be made and the XML can be resent

NOTE: FIS results will not be scored to the FIS Points List until the TDTR XML file & FIS TD Report are submitted.

SUBMITTING THE TDTR XML FILE


What about non fis events
WHAT ABOUT NON-FIS EVENTS? [email protected]

  • A TDTR is required for all USSA-scored non-FIS events

  • A TDTR is required for all USSA non-scored Championship events, e.g. YSL, U10, U12 Junior Championships, Masters Championships, etc.

  • Either the original paper copy USSA TDTR can be prepared or the FIS TDTRsoftware can be used to produce a PDF report, as required, for non-FIS events.

  • FIS TDTR software may be used for non-FIS events (FIS logo instead of USSA logo is a non-issue.)

    -“National Race Code” is used for USSA Transmittal # (alpha character + 4-digit number) - “Category” must be selected; JUN-Junior or CHI-Children are acceptable

    - “Race Codex” is left blank.

  • The TDTR XML file must not be submitted to USSA’s autoscoring system as USSA is not currently set up to accept the TDTR XML file

    The TDTR for a non-FIS event must never be submitted to FIS!


USSA Race Transmittal Code [email protected] ALPHA designator with assigned USSA Race Code

Ufor USSA scored,

N for USSA non-scored,

Mfor Masters,

O(text not number) for Other

For non-FIS events:

Select “Category”:

“JUN-Junior” or “CHI-Children”

“Race Codex” is left blank; (no error message will be generated)


Tdtr for non fis event
TDTR FOR [email protected] EVENT

“U” for “USSA SCORED” +

4-digit USSA Transmittal number

Document must be printed/signed and included in scanned/PDF electronic or paper copy non-FIS

Race Result Document Packets, as required.

“JUN - Junior Race” selected; this and “CHI -Children” were only selections that seem to apply for non-FIS events


Thank You For Your Attention! [email protected]

This is an upgraded presentation. It has taken advantage of the work done by many Alpine Officials and we are grateful for their contributions.

The intention was to build a vehicle that can be used for explaining the intricacies of the TDTR as well as for updating Timing Chiefs and Technical Delegates.

This presentation is dedicated to Allen Church and includes a special “THANK YOU” for his many years of service to the USSA and the FIS Alpine Officials’ community.

Allen “The Pope” Church has been a valuable mentor and is a valued friend. He encouraged us to do our best and helped us to be better than we thought possible!


ad