I have a run somewhere in 2009 that says I did a 5 minute mile.I'm not even close to that pace... I suspect this happend when I ran down a hill and the sensor thought I was running much faster than I was. I am trying to find a way to remove this run from the NikePlus site so that I can accurately find my 'best mile'
Any advice?
Thanks
Easiest way to locate and remove misscalibrated run?
(7 posts)-
Posted 8 months ago #
-
You mean somewhere inside a run you had a 5 minute mile, but the overall run was slower? That's a bit hard to find. Presumably with a 5-minute mile included, your overall pace was a bit fast as well so you could sort your runs by pace here on Slowgeek. Just click on the Pace column on your run table either on your profile page on on the run page with the bigger table there. Then look at the top runs visually and see if you can find one with a sustained mile up around 5 minutes.
I looked at your fastest 25 runs, and I didn't see any that came anywhere close. This could be a Nike screwup as well. Where are you seeing this 5-minute mile? On the Nike main 2009 summary page? Nike is notoriously bad at math when it comes to this stuff. They don't understand the concept of local regression or weighted smoothing of noisy data points and tend to simply take a sample of points and connect them. So, it could be that something like this run
could have caused this. You are obviously not running a 5-minute mile here, but your interval spikes up there, especially with the added noisy data spikes. If Nike simply connected the noisy spikes and ignored the valleys, they might conclude that you ran somewhere under 6 minutes per mile there. For the fastest mile numbers, I don't think they do this though, but that is about the only explanation I can come up with given the data.
Posted 8 months ago # -
Thanks (as usual) for the quick and accurate reply.
I think I found the run that is causing this.on the 19th of Jan a had a very small run of .21 miles. my calculated mph in excel was =E13/60/1.61
E being the pace, which shows 9.25mph.
I will go back to NikePlus and delete this run (and the one next to it as it is overly fast as well)
I think the problem was I calibrated my sensor on a track, then ran on the road and the two were way off from each other. I went back to the default calibration after that.I'll report back if this fixed it. thanks for the help
Posted 8 months ago # -
But if you only ran 0.21 miles, it shouldn't get marked as a fast mile. Each run file contains per-mile (and per-km) indicators. They show up as those little red and green squares on the graphs here on Slowgeek. I am pretty sure that is where Nike gets the fastest mile, fastest 10k, fastest half-marathon, etc. timings from.
Posted 8 months ago # -
Your site was working correctly. When I looked on NikePlus for that run, it showed that the pace was not that fast, yet it was only 5 minutes in length. Not sure why it reported at such a high mph avg. maybe if I parsed the actual file it may show a spike.
I could care less what NikePlus says, what I didn't like was that my fastest mile was never accurately being listed on my Ipod. Hopefully this is fixed now.
Thanks again.
Posted 8 months ago # -
Here's a copy of the run data before being deleted, if you want to see if you can figure it out
id date distance duration pace calories description emp_id temperature timezone start_time sync_time Miles Minutes MPH
1344860757 1/19/2009 0.3425 305933 893.2350365 35 "" 4H752K2HVSX 48.2 -08:00 11:51:25 21:33:56 0.21 0.00 9.25
Posted 8 months ago # -
Just to clarify, I wasn't worried about whether Slowgeek was interpreting anything correctly. I meant that the little green and red boxes you see on the graphs are actually just showing exactly what is in the run data. The run data contains these split times, but for some reason Nike doesn't show them to you. But, I am pretty sure they use these split times in the data for figuring out your fastest mile. That's what I meant by a 0.21mi run not being the cause of your problem. You wouldn't have gotten a mile split in your data on that run.
Posted 8 months ago #
Reply
You must log in to post.