Skip to main content

Halfway through last Saturday's 100m Dash cycling race here on Maui, I saw a bunch of ties in the standings form and realized I had set TT*Ware to the wrong resolution (1/100).

TT*Ware always captures all the TODs in whatever resolution the timer dumps out, then calcs & truncates the NET based on the resolution set by the user.

Since the TODs from the Timy (in 1/10,000) were still in the racer reccords, I exited the Timing Form, corrected the race resolution to 1/1000, and recalculated all the NETs using the Recalc Utilities.

With the standings successfully recalculated and the ties eliminated, I re-entered the Timing Form and timed the remainder of the race.

Results are here:

http://www.themightyskunk.com/DashSept17/DashSept17.HTM
Original Post
Skunk tools saved the day for us this weekend. After 177 riders had started in a 441 person DH field we had a course hold due to an injury. The race was stopped for 10 minutes and then resumed. We took the original file import and added 10 minutes to the start times for the rest of the field. Started the import at record 178 and chose not to blank other records in the database. This took a little bit of time and the race had allready resumed with the original start times in place. The import was completed on a networked machine as not to disturb timing and then the recalc util corrected times for the riders who had allready come in after the restart. This whole thing could have been a nightmare and taken much longer to fix. Thanks James!

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×