IronScholar wrote:
DKMNTRI wrote:
download the USAT app. It's just like the IM app in the way it operates.
IDK what was going on with the app this weekend, but it was terrible. My husband said so many people he talked to said they missed seeing their athletes because the tracker was so off. I came in about 10 minutes ahead of my predicted time and my coach almost missed me.
I did the open sprint wave on Sunday, and the tracker currently says that that wave is still waiting to start. But for some reason, I show up in the championship category of my AG, which I shouldn't be.
Download it, but it's got issues. I wish they'd put them up on the website.
So if you are talking about run finish on Saturday, the tracker had a problem. The first split reader on the run (1.2 miles) was way short of 1.2 miles (somewhere around 1.0 miles). I am guessing that happened because of a rookie mistake -- they wanted a time at 1.2, but that was on the back portion of the first out and back -- so the split got triggered when we were on our way out to the point (and then when we crossed the reader the second time on the way back it was ignored because we had already triggered the split). Check out your first split -- I think everyone's was way faster than reality.
So once you have too fast of a time for the first split, you get way too slow of a time (and therefore pace for the second split) assuming that the second split was the proper distance. Then the predicted finish time (based on the second split pace) will be way off.
I think USAT does a great job with its races (e.g., AGN and Multisport Festival), but this is one area where it struggles. I wish it would hire the required expertise either in house or a timing subcontractor.
On the other hand, I have a little more sympathy for the tracker on Sunday. They made the change to Super Sprint at the last minute and it would be a lot harder to accommodate the change (e.g., repositioning split readers, reprogramming the computer, etc.). Yeah, maybe there could have been a contingency plan for this, but . . .