Timing Settings

Timing Setup defines which times you expect to record for a participant and how these times should be used. There are three key points to the timing setup:

Timing Points - The points at which you will record Raw Timing Data ("Chip Reads"). For example the START, FINISH or your Split Timing Points on course. 

Start Times / Finish Time Limits - The official start time (T0) to be used for timing the race, this is used by your Splits or Special Results setup to calculate race times. Optionally in some cases a maximum time. 

Splits: The setup of Timing Points in the order they will be crossed in the race and when, allowing calculation of times and ranks. 

For more complex setups where Splits cannot be used it may be necessary to use Special Results under Advanced Scoring Settings.

 

Timing Points

A Timing Point is a location where one or more timing systems are placed. If you have a main and a backup line at a timing point, it is usally only one timing point unless you want to run statistics over the performance of main and backup.

Timing Points can be set up in Main Window->Timing Points.

Learn more about these settings in the sub-sections.

Timing Point Settings

Set the following parameters for a timing point:

Name

Convention in RACE RESULT 12 is to write these in UPPER CASE. The name should describe precisely what the timing point measures. It can be START, FINISH, START+FINISH, ANNOUNCER or 10K SPLIT. Sometimes, one timing point has different functions for different contests. Maybe you want to name it "M_10K HM_15K" if it is the 10K split for the marathon and the 15K split for the half marathon. It may also be "10K+30K" if it is a turning point course and the timing point will be passed after 10 and 30 kilometers.

Color

You can simply assign a color for the timing point. Timing data in RACE RESULT 12 will be marked accordingly.

Position

You can select a GPS position of that timing point. This is helpful later on to validate that the timing system is set up where it is supposed to be and is also used for some Tracking Visualisation platforms.

Timing Point Details

When clicking the button, you can set more detailed parameters:

  • Subtract Start Time (T0): The global setting (as part of Special Results) can be overridden. If needed, this can be set differently for individual timing points.
  • Ignore Pre-Start Detections: The global setting (as part of Special Results) can be overridden. If needed, this can be set differently for individual timing points.

Automatic Timing Point Selection

Automatic Timing Point Selection can be configured in Main Window->Timing Points. It is especially important when working with Loop Boxes: Detections from different timing points (Loop Boxes) will be received through one timing system. That means you have to assign different timing points for different detections from one timing system.

On an event with several splits using the active system, we also recommend to use a unique channel and loop ID combination for each timing point, and to use the automatic timing point selection rules. This way, if a detection is stored on the transponder instead of being transmitted to the timing system on one split, it will be entered in the right timing point when the chip reaches the next timing system.

No matter which Timing Point is selected for a timing system, if one of the Automatic Timing Point Selection rules applies, then that Timing Point will be used. In most cases, you need to select only the Timing Point and the Loop ID.

If you choose to use the device ID as criteria, remember to include the letter prefix, for example D-4898 for a decoder, or T-20255 for a Track Box.

Special Settings

Accept Only Chips from these Order IDs: All passive bib transponders (except A-Z Tags) are encoded with the Order ID during production, this can also be seen in the raw data time RACE RESULT 12. Sometimes you may want to prevent old chips from being used, to filter to only to relevent Order(s) simply enter the Order ID here, multiple Order IDs can be entered separated by commas. This will apply dynamically and unrecognised chip reads will be ignored for results. 

Splits

Splits provide the quickest setup for races which follow a standard pattern, either a point to point or a fixed number of laps, and will also automatically generate many of the times and ranks required for output list. Splits can also be used to quickly generate sectors / legs which may span a variety of different splits. Splits also generate a wide range of fields for each Split, including different time formats, ranks and pace. 

Splits are defined for each Contest individually and each Contest can also therefore use a different scoring mode. 

Splits can use two different alhorithms for calculations which handle the calculation of splits slightly differently, the algorithm is set for all contests. 

General Splits Setup

Splits are defined per Contest, allowing for an easy way of adding additional timing points to a particular contest and also defining contest specific rules where appropriate. Split setup can be copied from another Contest. 

When setting up Splits for a race each split should have a unique name and then uses a few key settings to determine how a split time is calculated. Splits should be setup in their correct order on the course since this influences the calculations used.

Time Mode

Each contest can be set to score by default using either Gun Time or Chip Time, setting this according to the contest allows for a simple output setup for final results.

It is sometimes necessary that certain groups of athletes, such as elites, are scored according to Gun Time but the main field should be scored on Chip Time. For this you can define a filter to be used for those who should be scored on Gun Time. Note that this filter will only work with fields which do not rely on Split calculations, as such it is not possible at this time to filter based on a Rank which relies on a Split Time.

For races where both time modes may be used both Gun and Chip time can still be called, see Split Fields for how to reference each. 

Timing Point

Splits will only work with Timing Points which are set to Use Raw Data Only, since they can dynamically recalculate if new times or splits are added. A backup Timing Point can also be defined, so that if there is no time from the primary Timing Point selected then a backup time can be used, an offset either + or - can also be applied to the backup to account for the difference in time between the 2 Timing Points.

Note that 2 detections will be considered the same passing only if they are within 20 seconds. If the main / backup detections are greater than 20 seconds apart then they will be considered separately which may impact how Splits are calculated. 

Type of Sport (up to here)

The type of sport serves 2 purposes.

Firstly it defines which splits are Pre-Start (Start Check) or the start detection. The split defined as the start is also used for the Chip Time calculations, if multiple starts are defined then the last one will be used. Normally the start detection should use the last read since participants may generate multiple passings whilst standing at the start.

Secondly by choosing a type of sport for a split then a Min/Max Pace/Speed/Time is automatically suggested based on the type of sport, each sport has a unique default suggestion. 

Distance (up to here)

Entering a distance for the split aids in split calculations which rely on a Min/Max speed or pace, furthermore the distance for each split allows for automatic calculation of speed/pace for each split or leg. 

Split distance can be defined as from start, from previous split or from a chosen prior split, there are also multiple distance formats which can be used (meters, kilometers, miles). 

Min/Max Pace/Speed/Time

For each split the software must have a minimum time, for this there are multiple options on how this is calculated which may vary according to your personal preference. 

  • Race Time - Minimum and maximum race time for the split from T0
  • TOD - Minimum and maximum Time Of Day for the split
  • Time from Prev. Split - Minimum and maximum time from the previous split
  • min/km - Minimum pace (fastest) and maximum pace (slowest) in minutes per kilometer
  • min/mile - Minimum pace (fastest) and maximum pace (slowest) in minutes per mile
  • min/100m - Minimum pace (fastest) and maximum pace (slowest) in minutes per 100m
  • km/h - Minimum speed (slowest) and maximum speed (fastest) in kilometers per hour
  • mph - Minimum speed (slowest) and maximum speed (fastest) in miles per hour
  • m/s - Minimum speed (slowest) and maximum speed (fastest) in meters per second
  • From Split "Split Name" - Minimum and maximum time from the selected split

Name / Label

Split names are used to call the Split fields, thus names cannot include special characters since  this may cause ambiguity. The Split labels allow for any name to be shown in place of the Split name, and can also be translated in to multiple languages.

Advanced Split Settings

For each split the colour can be defined as well as a default Speed/Pace format. The format is set to Automatic by default which is then based on the type of Sport defined.

Legs Setup

In races with multiple splits it is often necessary to define specific Legs within the race, Legs may span multiple splits, distances or types of sport. Different Legs may even overlap where certain races require specific legs.

For example in a triathlon this may be swim/bike/run, or in a marathon it could be the first/second halves. 

Each Leg is defined "From Split" and "To Split", this can use the Start Time (T0) or any Split already setup in the Splits table. Similarly a colour default Speed/Pace format can be defined in the advanced settings. Legs also have separate Name and Label fields to allow for custom labels and translations to be applied. 

For each Leg the distance is automatically calculated, based on the distances defined for each split and Leg times / ranks / speed / pace will also be automatically calculated. 

Splits Algorithms

When calculating Splits, the Split times must always be sequential and so a later time cannot be used for an earlier Split, but how the times and Splits are handled depends on the algorithm.

Version 1

This version of the algorithm always considers all possible Splits for the calculations, and the calculation method runs through the splits sequentially to find the first matching chip read to fulfil the split. 

For each Split a valid timeframe is calculated based on the minimum / maximum values defined for the split and any previous splits already calculated. 

In this method an earlier Split will always take priority, and so if a detection is missed, but a later chip read is recorded at this timing point then this may cause errors. 

Version 2

The newer Splits algorithm instead runs through all chip reads for the participant sequentially to find the first matching Split with a valid time frame. 

When a Split is matched, then all other Splits (before and after) will recalculate the valid timeframes based on the minimum / maximum values defined for the Split and the currently calculated Splits. 

In this method if a Split is already calculated then an earlier Split will not be filled in by a later chip read, however if unexpected chip reads are recorded then this may cause errors. 

Start Times (T0) / Finish Time Limit

Start Time (T0)

The Start Time (T0) is a special result which is relied upon by several other parts of the timing setup. Start Times will be defined in Main Window->Start Times/Finish Time Limit either per contest, per bib range or based on any other field (Wave Start) and then automatically calculated for each participant.

Start Times are very important, because normally we want to ignore any detections before the start. Splits will only be calculated for times which occur after the Start Time, unless using a rule which overrides this, and when working with results the Start Time can be subtracted from the Time of Day for a simpler setup.

Finish Time Limits

Finish Time Limits on the other hand are used to define a time limit for an event, and how times should be handled after this time limit. They can also be defined either per contest, bib range or based on any other field / expression which is usually the same as your Start Times. 

There are three options on how to handle Finish Time Limits, as different types of event may have different rules / requirements. 

  • Ignore chip reads after finish time limit
  • Accept one last chip read after finish time limit
  • Accept chip reads after finish time limit

For example - some cycling events, the option Allow one last detection is important: before the winner arrives at the finish, the finish time limit is set to the current time and everyone can complete the current lap.

Setting Start Times / Finish Time Limits

Start Times and Finish Time Limits must be set according to the same reference as your timing system is running, if you are using GPS Time / Time of Day then these times should also be entered as a Time of Day. These values can also be updated at a later point in time and all results or calculations which rely on these values will automatically be updated. 

If a timing system is connected to your event file, you will see the time running in the top right corner. You can then click the Set Start Time / Set Time button to save the current time for the corresponding Start Time or Finish Time Limit. Otherwise, the top right corner will show No Decoder Time Available and you can enter the start time manually.

For Start Times, if two or more contests start at the same time, you can select them using the checkbox on the left and then click the Set Start Time link at the bottom of the box to start all checked contests at the same time.

It may happen once in a while that you accidentally overwrite a start time. By clicking the Show History link in the top right hand corner of the box, you can still find the old value.

Markers

Markers/Impulses are timestamps from the timing system that are created for example by pressing a button or through an impulse device such as a photo cell. These are most commonly used to capture an accurate T0 synced to the decoder time, but can have other applications in timing.

The timestamps are saved according to the assigned Timing Point along with all other chip reads, the list of markers stored in the event file is shown below the Finish Time Limits.

Markers are stored with the same Bib number as the Marker number set on the decoder, you should ensure that you use a marker number which does not apear in your bib number range.

Markers can also be created manually using the input below by selecting the timing point and entering the time.

Chip File

RACE RESULT disposable transponders such as the Chip Race Number are programmed with the bib number. In other words, chip number (or chip code) is the same as bib number. In this case, you do not need a chip file!

However, if you are working with reusable transponders such as the RACE RESULT HuTag or the ActivePro Transponder you need to map chip codes to bib numbers. A Chip File can be entered or imported in Main Window->Chip File. Simply enter chip code and bib number in the table.

A chip file can be imported from an Excel, TXT or CSV file with the corresponding Bib and Chip Code fields. 

You can also search the chip file by Chip Code or Bib to lookup specific participants. 

If you are using passive transponders with a chip file and need to map a different chip and bib numbers then you should pay attention to the Chip File Settings. You can also create a two-step mapping for transponders which may be pre-labelled but where chip label is not necessarily equal to bib number. 

 

Chip File Settings

There are 3 options for Chip File settings which affect how the chip file or Transponder1 / Transponder 2 fields are used.

 

"Use chip file or transponder fields only for Transponder Codes (e.g., DHANX23). Chip Codes (e.g., 1423) cannot be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number can also be used. [Recommended for most events]"

This is the most common option, it allows you to use Transponders with alpha-numeric codes (Active Transponders, HuTags, Reusable ShoeTags or A-Z Transponders) or assumes that if a numerical chip code is received then Chip Number = Bib Number. 

Below this are 2 options for how transponder codes are then mapped to a participant.

"Search bib from chip file table in field bib no. [default]" - The bib number in the chip file table will be matched against the bib field of the participants.

Chip Code -> Bib Number
(for example: ZDXED44 -> 44)

Alternatively, you can create a two-step mapping using "Search bib from chip file table in transponder fields [caution]"

Chip Code -> Chip Number -> Bib Number
(for example: ZDXED44 -> 744 -> 44)

The chip ZDXED44 has a sticker with its chip number 744. ZDXED44 and 744 will be entered in the chip file table. In the participants Transponder 1 or Transponder 2 field the chip number should be entered. In the example above, bib number 44 has chip number 744.

The main advantage is that you can more easily assign chip numbers to participants. Instead of handling complex chip codes such as ZDXED44, you only need to enter 744.

 

"Transponder Codes (e.g., DHANX23) or Chip Codes (e.g. 1423) can be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number can also be used."

In this mode you can use transponders with alpha-numeric codes, and can also map non-matching bib and chip codes. In this mode if a passive transponder with a chip number is scanned it is first checked against the chip file, and assigned to the corresponding bib, if there is no mapping for this chip to a bib then it is assumed that for this chip the Chip Number = Bib Number. 

 

"Transponder Codes (e.g., DHANX23) or Chip Codes (e.g., 1423) can be used in the chip file or transponder fields. Normal passive transponders programmed with the bib number will not be recognized unless they appear in the chip file or transponder fields! In other words, with this option you must use either a chip file or the transponder fields for every participant in the event."

In this mode you can use transponders with alpha-numeric codes, but if you use normal passive transponders then the chip code must be mapped to a bib number. Any chips which are not allocated in the chip file or transponder fields will be treated as unknown transponders.

 

Race Simulation

This tool serves to simulate the race before race day to make sure all your settings are correct. You can either generate all times all at once (so you basically get the final results after race day) or you can simulate the times live. The latter is helpful to test functions like announcer screens or result screens.

To use the function first select a contest for which times shall be generated and optionally enter a filter if not all participants shall be part of the simulation.

Manual configuration

Then, select Results in Static Mode and/or Timing Points in Raw Data Mode which shall be simulated. Enter a minimum and maximum time. In most cases, you will use the Add function to add the previous time in order to make sure that the time is greater than the previous time. Your minimum/maximum time will then be the sector times. Example:

  • Start: min 0:00, max 5:00, Add T0
  • 10K: min 30:00, max 60:00, Add Previous Time
  • 20K: min 30:00, max 60:00, Add Previous Time
  • 30K: min 30:00, max 60:00, Add Previous Time
  • 40K: min 30:00, max 60:00, Add Previous Time
  • Finish: min 5:00, max 10:00, Add Previous Time

Copy from Splits

If you are suing splits you can generate your race simulation based on the splits you configured under Main Window->Splits. To copy your split setup use the Copy from dropdown menu. Under the section labeled Splits select the contest you want to copy settings from.

 

You can also select a Read Rate less than 100% if you want to simulate some missed reads at the start or if some timing points will not be passed by everyone (for example an optional timing line to donate a certain amount).

Then click Generate All Times to generate all times all at once or Simulate Times Live to simulate the times live. In the latter case, you can see the clock running next to the button and you can also increase the speed of the clock. In most cases, you will open another browser window to check the results of the live simulation while the Race Simulation tool remains open and running. Use the icon in the top right corner for that.