Select to expand quote
boardsurfr said..
We've got two conflicting issues here: accurate results and inclusiveness. I think the current situation can be improved, and will outline what would be needed in a separate post. This one is just about accurate results.
1. Accurate results:
This is a must for a competition that (a) uses hundreds of results every month, and (b) is scored automatically, without an expert examining every jelly bean track.
What is confusing is that many non-approved devices are very accurate most of the time. But all GPS devices will sometimes report inflated results. This is true for every single GPS device I have ever looked at, including the GT-31, GW-60, the Motion, and the Suuonto watch.
Software uses a variety of data to automatically identify "spike results". This includes the number of satellites, acceleration, and error estimates (called SDoP or sAcc). The worst spike occur when crashing, waterstarting, and swimming. Anyone who learned foiling with lots of crashes and slow waterstarts can produce tons of examples, I do it every session.
Non-approved devices do not provide the necessary data to automatically identify spikes. That's the problem. The Suuonto files I looked at do not even report the number of satellites, which is essential for swimming spikes. Furthermore, the currently approved devices (GW-60, Motion, and u-blox based prototypes) use higher data rates, which make it much less likely that spikes that slip through the filters affect the result. One wrong number in 1-Hz data will be 50% of a 2-second result; for 5 Hz data, this drops to 10%, and it drops to 5% for 10 Hz data.
I have written GPS analysis software that anyone can use for free. I have quite a bit of experience in algorithm development, and have demonstrated that speed results can be calculated a lot faster than other software does. I could imagine some new software filters that would identify some artifacts in data from non-approved devices, but I cannot think of algorithms that would identify "fake top speeds" without satellite and accuracy data at a level that is adequate for a competition like GPSTC.
boardsurfr,
I agree with 99% of what you have presented. I do think that your proposed changes are more than I was thinking (surely we can trust people to manually set the field that indicates whether the device is approved, and then only minor mods are required to GPSTC and nothing else).
On an aside, I do a lot of algorithm development also. I am really perplexed as to how someone crashing could not be easily identified from a speed plot and nothing else. Erroneous GPS data will result in acceleration/decelerations that are just not possible on a windsurfer and the speed would go close to zero in close time proximity to the high speed spike. A simple algorithm that identifies implausible speed data and then masks out a period before and after would surely catch 99% of crashes. It could be developed further to look at position. We could identify a function that has the minimum radius for the current velocity that a highly skilled sailor can achieve and if the position plot is outside of plausibility we invoke a similar masking. Likely this would catch most errors automatically and at least flag them for a human to decide upon.
My point being that with some smart heads working on it, I believe that data errors could be detected in most cases without the requirement for accuracy data.