Pace bug or rounding error?

[mandohack]

Hi, gerhard.

Thanks for one of my favorite plugins.

I think I found a bug In listing my high scores (High Score v 2.0.419) for my last run, it shows 6:46 pace for 5k (3.11mi) and a slower pace for the 3.00mi at 6:47. I know, I'm being picky, but thought you might like to know about it anyway. They do have different start times and places, but the fastest 3.00mi should be contained within that 3.11mi. That or it's simply a rounding error.

Again, I appreciate your great work on the very useful plugins, Unique Routes being one of my absolute favorites.

--Ian

HS v2.0.419
ST 3.1.5349
Win 8.1

[gerhard]

In listing my high scores (High Score v 2.0.419) for my last run, it shows 6:46 pace for 5k (3.11mi) and a slower pace for the 3.00mi at 6:47.

This is a rounding error in how the "parts to compare" is done. As it currently is implemented, the rounding error is not in the plugin itself.
The plugin uses the ST built in method to chop up in laps (20m long). These laps are then compared, step by step. The precision is lost in this chopping.

I have considered handle the time vs distance special, to avoid this chopping. The primary reason is performance, but this issue would likely be handled better too. (Personally, the rounding error in this issue is not something I find important (GPS has bigger issues)).

Note: A similar display "issue" could occur if the grade filtered away the shorter distance (grade was < -2%) but not the longer one. Not in this case.

[mandohack]

Thanks for the great explanation, gerhard, I appreciate your time.