2012 Wk 6, Bouncy, trouncy, flouncy, pouncy

It’s been an interesting week, running wise. It started off with the first run for six days on Monday. It wasn’t very good, my ankles and calves hurt. My knees started protesting after the event, and it just all felt very wrong. I tweeted about it and got a few good responses with ideas of what it could be – a lack of practice, the requirement for new shoes, the cold weather. I suspect that first run may have been a mixture of all three.

However, the second run on Wednesday was equally painful and I knew it was time to purchase some new shoes. Considering how long I’ve been running on them, it’s a wonder that I haven’t had any problems before. I managed to pick up some new trainers on Thursday, and rearranged my schedule so I could try them out on Friday.


With new shoes, it was much better, the pains were completely gone, but my thigh muscles felt quite strained. That does happen occasionally, but I thought in this instance I might have been overcompensating the previous two runs and the muscles needed some time to unwind.

I remember when I got brand new trainers for the very first time, and all I could think about was how bouncy they were. This time was no different and I felt awesome walking out for that run on Friday. I could feel that there was a certain bit of my foot that was going to blister, and it did, but other than that, they were pretty good.

The weather was finally on board this weekend, and I got to go back to my route. I was hoping to extend the distance, ignoring speed, but as I was still getting used to the new shoes, I stuck to the normal 5k.

The graph is ridiculous. I’ve been battling the GPS for my weekday runs and Gavin suggested the iSmoothRun app as an alternative to the Runkeeper one. I gave it a go, and it’s really good. It has space for a lot more information, and makes use of the accelerometer. But, whilst the app read the above figures, when I exported it to Runkeeper, it read a totally different distance. I wasn’t sure which one was right, but I’ve manipulated the graph in Runkeeper to reflect what the app says. I’m not convinced. I think I’ll stick to the Runkeeper app just for the sake of them both at least reading the same.

8 thoughts on “2012 Wk 6, Bouncy, trouncy, flouncy, pouncy

  1. There is something fabulous about new running shoes. All that bounce and spring!

    I was once told that after about 700 – 800km you need to buy new trainers as all the cushioning has been worn out. I’m not sure if Run Keeper lets you keep track of cumulative figures like that? I keep track via my Garmin and it’s remarkable how ‘fresh’ my trainers still look at that stage. I’d never think of replacing them via looking at them, but trying to avoid injury I get a new pair at that point. (In fact I now always have two pairs on the go that I alternate.)

  2. They do a cumulative total on Runkeeper, but that’s from all time with no resetting. I do export a spreadsheet of the numbers though, so I can keep a note of it there. A countdown to new shoes sounds like good motivation to go out πŸ™‚

  3. How totally different was the distance? If you have paused your run at some point, say to cross a road then perhaps Runkeeper is counting that distance too when it shouldn’t be? Normally I get a discrepancy of 100m and I run 10-15km, so it’s hardly worth worrying about for me. Sounds odd though.

    I am convinced iSmoothRun is more accurate because the paths deviate less than those of RunKeeper – especially near water or around buildings. I have found that while running with friends who had different GPS devices that we always had slightly different distances anyway, and I think using GPS to track your runs should only ever be used as a guide and not an absolute way of measuring pace.

  4. iSmoothRun measured the route as 5.01km, but when I looked at Runkeeper, it was 4.77km. I don’t know which was right, the map looked like it had cut some corners so there may not have been enough data points, or who knows why it was different?

    I’m not so bothered about pace, I’m slow enough that it doesn’t really matter. I think that as I’ve been using Runkeeper to this point, and they are measuring differently, I’d rather stick with the one to compare historically. Also, I just don’t want to complete a run, of whatever distance, and then be in for an unpleasant surprise when I get home.

  5. Hi there

    there are usually two cases.
    1. if RK gives a longer distance, it’s because pauses are not exported. iSR doesn’t add the distance between pause start/end.
    2. if RK gives shorter distance it’s usually because there was a part without GPS signal, the app switched to accelerometers, and this data cannot be exported to RK (extreme case is a treadmill run, where there is no signal at all and only summary can be exported)

    In general RK recalculates everything based in GPS data (unfortunately GPS data is not the whole story).

    GPS performance depends on device (3GS, 4, 4 verizon, 4S all different), weather, location, and environment (forest, buildings etc).
    A very good idea is the use of a footpod (very consistent and excellent for pacing).

  6. and always remember the most important thing in running is not distance, pace or speed.
    It’s running form and cadence πŸ˜‰

Comments are closed.