Tag Archives: correlation

More on the Nike+ Running Club Experiment

As I progress through the marathon training programme concocted by the Nike+ app, I am enjoying the challenging runs that it is assigning me. 

After last week’s benchmark run it has started to add pace requirements to the runs that I do. Currently, they are all well below the pace that I generally run at which seems a little strange. Perhaps this will adjust as the programme continues?

On Sunday I decided that I didn’t want to do the suggested exercise which was to tryout the Nike+ Fitness Club application. Instead, I opted to run 12 miles. 

The run went well and was an enjoyable run on the Perkiomen Trail from Schwencksville. 

On completing the run, I chose to categorise it as an ‘Other’ event as I had already competed all the runs for that week. 

Come Monday morning and a new training week and guess what? The app tells me I need to do an 11.5 mile run. On a Monday morning. After doing 12 miles the day before. Bugger off!

I tried to reclassify the previous day’s run so that it would count as this one, but to no avail. There’s no way to edit the assignment of previous runs; even the website doesn’t offer a way to do this. Boo. 

Because of this, the app thinks I bailed on the long run for the week. :-(. 

I did actually go out and do a four miler but that isn’t twelve miles!

Roll on to Wednesday morning and the prescribed run was a speed run with 8x800m intervals and 2:45 recovery (strangely specific). 

I wasn’t too happy about this as that’s a lot of intervals but opted to hit the streets. Running track intervals on the road is tough as you have to allow for traffic and the ground is not flat; hills in fast intervals. Yuck. 

For the recovery periods I simply jogged a little and ended up running a total of around 7.5 miles. 

Did you notice how vague that was?

Why? Well, the speed test only counts the distance you run during the speed intervals and not what you cover in the recovery. 

Four miles is all that counted from the 7.5 I covered. Grrr. Not best pleased. 

Any way, one useful thing you can do with these 800s is use them to calculate your estimated marathon time using the “Yasso 800” approach. I know this is a correlation prediction rather than a causation, but it is fun to play with numbers. 

After some finagling of the numbers I worked out that my marathon time would be 3 hours 43 minutes. That’s pretty close to my current expectations of my performance. 

Back to the Nike+ stuff: I’m not best pleased that I have to run the speed tests with the phone in my hands. As I got sweaty I was worried I’d drop my phone. I think I’m going to stick some strong magnets inside my gloves so that they will grip the metal plate in my phone case and take some of my worry away… I’ll let you know how that works out. 

Have a fun week running. 🙂

Advertisements