The LapTime Module will solve three common issues that occur in sports where long races with multiple laps are common:
- It is difficult to prove that a competitor has been told to go the correct number of laps. With LapTime, the operator has “proof of pace” or a list of times the competitor turned in for each lap of the race. If these lap times are consistent with the finish time, then it is reasonable to assume that the race was the right distance.
- The generated split times are useful and interesting information that can be displayed on scoreboards and used by announcers to enhance the appreciation of an event.
- Updating split times and lap counting during an event not only makes the competitor more comfortable regarding the number of laps they have remaining, but can make for interesting real-time data displays regarding things like who in a race is really moving quickly and might be “catching up” or “on record pace”.
The primary purpose of the LapTime module is to establish “proof of pace” and the most reliable indicator that a competitor completed the correct number of laps is to show the times for each lap completed. To help ensure that the split times recorded are accurately reflecting the number of laps completed, the TAG Heuer by Lynx operator can set a ‘maximum’ and a ‘minimum’ legal time for a lap to be recorded. The minimum time should be a little less than a competitor could achieve at maximum speed, and the maximum value should be a little higher than would be recorded in a highly tactical race with competitors moving slowly.
If any split time falls outside the boundaries set up by the "Too Fast" and "Too Slow" split times, that line of the results turns red. The operator can then click on one of the three buttons:
- Click on Accept Split if they determine that the split is correct (even though it fell out of range).
- Click on Delete Split to "mask" a split if the operator pressed the button when they shouldn't have.
- Click on Add Split to insert a "placeholder" split if the operator forgot to press the button.
The reason for using "placeholders" and "masking" rather than just creating or deleting data is that if an operator makes a mistake they can to go back and look at the "real" log of split data for an athlete and edit it after the race.