Software is nice, but it isn't always correct. When I'm
scorekeeping I often have to manually score a pilot from an obviously messed up
track log when the scoring software can't make the correct calculation. I can
usually figure out the time that he crossed the goal line even if the software
can't.

Scoring software isn't perfect and can't handle all the possible cases of messed
up data that gets thrown at it. The scorekeeper just has to use his judgment to
fix problems.

Scott Barrett apparently had his flight instrument go out on him half way into
the flight and he had to rely on his backup GPS to record the flight for him
(and other pilots to help him find the thermals as he had no vario). Apparently
he  was first in today (amazing given how much of the flight he flew
without a vario) but there are some strange happenings with the track log and
even stranger things happening with the FS program not displaying all the track
log data.

Apparently Scott made goal (400 meter virtual cylinder) in front of Christian
Chiech, but the obviously odd track log data (which appears to be correctly
displayed in SeeYou) has him 14 seconds behind to the best of our calculation
(so far) given the odd nature of the data.

The assumption is that he was covering the backup Garmin with his body while
pulling in fast for final glide and the Garmin was not getting good satellite
position fixes.

Anyway it was very tight in the top places at goal today with about fifty pilots
in goal.

Christian, Alex, Jonny, Rohan, Scott, Christian Voiblet, were some of the top
scoring pilots today.

It was very disconcerting to see that FS did not display all the data (track log
points) that were in the track log file. It was interesting to note that the IGC
file created from the KML file used by FS when displayed in SeeYou did display
all these wayward track log points and that really told us how screwed up the
track log was (and how FS is a little less than trust worthy).

We assume that the track log continued to display the poor satellite reception
that the Garmin was recording so that even though there are some reasonable
looking tracklog points they aren't necessarily reflective of where Scott was at
the time recorded for these points.

Again, judgment is needed to determine the more accurate result, but you are
limited by the bad data and must make the best of it that you can. You don't
just adjust it to reflect what pilots think that they saw.