Mileage bug?? (Read 333 times)

Now that I checked, my yearly mileage also shows different totals in the overall run total and the goal widgets. It's a 3 mile difference and not really important, but wanted to let you know.

Any chance this has something to do with a run or runs marked as "Private entry" in your log? A couple of years back, my YTD widget did not match the Pace bunny's total and I traced it to the Pace bunny "seeing" the mileage from one private entry which the YTD widget did not show. I made that run public and then the two mileage totals matched.

There is indeed a mileage bug.  It has been particularly hard to track down.  I thought I finally fixed it at the end of last year but apparently not.  The yearly mileage is cached so that it can be displayed quickly without having to go through all the records and sum them up.  Under a certain circumstance, the yearly mileage isn't updated.  Because it happens so rarely, I haven't been able to find it.  For now, I'll just reset the yearly distance.  If you can keep an eye out for it, it would be much appreciated.

It's back. I just noticed yesterday that the overall run total and the progress towards goal total were different by about 14 miles. I am pretty sure it was okay a week ago. It's not a big deal for me, but I'm letting you know if this helps you find the bug.

I upload them from my Garmin. I usually upload each one at a time. Sometimes I might have more completed more than one workout in a day (a bike ride followed by a run or a warm-up jog before a race followed by a jog home) and then I upload two or three workouts at a time.

I edit and save each one individually. I do not click on Save All.

I thought the bug was caused by bike entries, but theyapper66 doesn't have any bike entries.  I am still not able to reproduce the problem.  It only seems to happy to a handful of users so the problem is very obscure.

half-fast: could you provide more info on your problem?  Your numbers seem to be correct so I might be looking at the wrong place.

Hi Eric - It looks like the mileage is correct, but the pace is off.  I think I have found the source of my issue, but not sure why it's the issue.  March 2013 has a pace of 4:53...no where close to reality for me   I had several runs that month that had mileage, but not times.

 

I expect that is what is causing the pace to be off, but I thought those runs would not be used in the overall pace calculation....

You are referring to the yearly pace.  The yearly data is cached to improve overall site performance.  Instead of locating all your workouts for the year and then summing them up, the year's distance and duration are stored as two numbers.  When you want to see the year's numbers, they are displayed.  Pace is calculated by dividing distance by duration.  If you have several workouts without duration, then the pace will be off.  The only way to fix it is to store another set of distance and duration values for workouts that contain both.  I'll consider that when I revamp the log.