Hi,
This weekend we had a big problem with the results in one of our races. We actually had two different things go wrong:
1. A racer skied off the course and the operator did not catch it, so for the next few racers SpiltSecond was applying each racer's finish time to the previous racer, giving an incorrect of very slow times.
2. We had a long slow GS course, and some of the slower racers were skiing it in the 1:30 to 1:40 range. But the resort was starting them at about 25 second intervals, and this meant that twice we ended up with 5 racers on course. SplitSecond it seems has a limit of 4 racers on the course, so when this happened it would log "too many on course" in the timing log and ignore the 5th racer's start. Again the operator didn't catch it for a while and so we got the opposite to above with each racer's finish time getting applied to the following racer, giving an incorrect run of very fast times.
We eventually managed to sort all this out and manually re-calculate the times of the racers involved from the start/finish times in the timing log once we'd worked out what had happened, but it was a tedious manual task involving digging through the data in the XML files.
So my question is, is there an easier way to fix the incorrectly applied finish times when this happens? I've never seen the 2nd problem before, but a missed DNS is certainly something that we see occasionally.
If not, how about this as a feature request for SplitSecond: a screen that will display the racers' start and finish times in run-order, and allow the user to select a series of finish times and shift them either up or down to the next/previous racers?
Ian
Original Post