To me, this seems a bit weird.... Is this a problem?
-Building429
-Building429
I had some code in there to clean up corrupted run data for a while, but I took it out because I actually want to know when things are messed up. And yes, this indicates junk data at the end of your run file. There is a distance sample taken every 10 seconds when the workout is active. If you are standing still, then the same distance will be recorded, but if you start moving then you will get an ever-increasing distance. There is no way for a subsequent distance sample to be less than a sample before it. It isn't directional. it's not like running backwards will rewind your distance, it will simple add more distance. Your graph indicates a sample that is showing a distance that is less than the distance in the previous sample. That should not ever happen. Now, it looks like just a single sample right at the end, so you can basically ignore it, but it does indicate that there is a problem and if you keep seeing this, you need to get yourself a new sensor/receiver.
well my sensor has been acting up lately.... but it seems to have been doing better lately.... it would indeed be hard to get a new receiver though, seeing as I have an iPod Touch.... Thanks!
Building429 said:
well my sensor has been acting up lately.... but it seems to have been doing better lately.... it would indeed be hard to get a new receiver though, seeing as I have an iPod Touch.... Thanks!
Interesting, this is the first run I have done with my iPod Touch, and the first time I have ever seen a graph like this:
And just for the record, the dismal graph on the Nike+ site is "normal". I wonder if this is a common iPod Touch glitch.
rlerdorf - Until you can prove some other explanation beyond a shadow of a doubt, I am going to use this graph as evidence that I can in fact run so fast that I can travel back in time....
I have a weird run graph too from my last run. On nike+ it looks allright, but in slowgeek, it seems to show only a part of my run. I tried to upload the run again, but no change in slowgeek.
Maybe a defective sensor, since it is over one year old?
Yes, that is interesting. Unfortunately there isn't much I can do about it. That is what Nike is sending me for that run. See this URL:
http://nikeplus.nike.com/nikeplus/v1/services/widget/get_public_run.jsp?id=1813806257&userID=485231611
The interesting part is the extendedData section at the bottom which is supposed to contain the distance you have run at 10 second sample intervals. The very first sample is at 15.0649 which makes no sense. Here are all the sample points:
15.0649,15.0973,15.1295,15.1613,15.1905,15.2197,15.2468,15.2754,15.301,15.3298,
15.3614,15.39,15.4154,15.445,15.4748,15.5097,
15.5455,15.5748,15.6031,15.6328,15.6618,15.6951,
15.7271,15.7566,15.7856,15.8205,15.8549,15.8796,15.9139,
15.946,15.9774,16.0058,16.0368,16.0685,16.1018,16.1312,16.1567,16.1921
Compare that to your run before that:
http://nikeplus.nike.com/nikeplus/v1/services/widget/get_public_run.jsp?id=1277054406&userID=485231611
0.0,0.0264,0.0603,0.096,0.1133,0.1645,0.1994,0.2269,0.2594,0.2958,0.3305,0.3639,...
I cut off the rest of the normal-looking data there. The point is that the first sample should be at or very near 0. Having the first sample at 15km makes no sense. The fact that Nike was able to graph that run means that they had the real data at some point but for some reason it has gotten corrupted. I'd email Nike+ support on this one. Give them that first URL and ask them if they can fix the run data.
Thanks rlerdorf, I mailed nike+ support and see what they can do. The original run data on my ipod seems ok, since it shows up fine in Running Tracker. I´ll see what nike+ is going to say.
You could try deleting the run from Nike+ and moving that run from your "synched" directory to your "latest" directory on your ipod and re-synching. I cache the Nike+ data on Slowgeek to speed things up, but let me know if you do that, or if Nike fixes it and I will flush your cache.
I deleted the run and did a new upload, since nike hasn`t been very helpful yet. Please flush the cache, but looking at the public available data
http://nikeplus.nike.com/nikeplus/v1/services/widget/get_public_run.jsp?id=471598418&userID=485231611
it seems to start with 15.0649 again.
If the graph is still weird after flushing the cache, I will contact nike+ again
Yes, I flushed it, but since the Nike API is still returning bogus data, it won't help.
What is strange is the number of graphs I've been seeing like this recently. I finally had one the other day. There have been several instances of runners in the Canadian Relay challenge.
I wonder what is happening on the Nike end to cause this. Your recent one is definitely broken:
And going to http://slowgeek.com/r2015141585 and clicking on the little "raw xml" link at the top of that page gets you the raw uncached data Nike is sending out. This is the same data their own widgets use, so if you were to look at a Facebook widget, or wherever people use those, for that run, you would see a similar problem.
My most recent run is shown properly in slowgeek, but I saw a broken graph when I looked at the data of user "DarSac". I´ll contact nike again on the problem.
Today I got my reply from nike. They asked me to delete the run and upload it again, as I did before without success. Well, I tried to be helpful and - wow- a completely different run graph appeared in nike+. Compare this to my post above, it´s the same run.
So my problem seems solved, although it is really strange to see two completely different graphs from the same raw data on nike.
You must log in to post.