Anne forwarded an email to me today that Macro sent to the membership@windwanderers email address. I'm no longer on the WW committee, so best to use my regular email address (
[email protected]) if you are trying to contact me, or better yet to post problem files into the specific problem files forum (
https://www.ka72.com/Forum/aff/10 ) that exists for that purpose. I have a handful of files there that have been brought to my attention. If there are any other odd ones out there (such as the aforementioned odd nm for Daffy) I hope that users will be proactive enough to post them there, rather than just sit back and snipe at the system.
A short time/distance error (such as one in a 2s peak) is much easier to diagnose and resolve than a long distance one such as a 1hr, so I tend to look at these first.
Macro raised a point which was:
> It will be interesting if one day administrator will run bulk processing of all historical data to check if there were many similar glitches in the past.
When a significant change is made to the KA72 engine, the version number of the engine is changed. Any time a track is subsequently viewed, the full result set is recalculated using the new version of the engine.
I have re-run the calculations on all files once before, when we moved to the current version of the site where historical results are cached. It was an extremely lengthy process which took several months in all, as there were over 100,000 track files in the database. Each file had to be retrieved from storage, reprocessed, and the results stored, without impacting too much on the normal usability of the site. The extra bandwidth and processing power required for the exercise cost me a few hundred $ too. So I'm hoping not to repeat the exercise too soon.