Previous Entry Share Next Entry
Race Report
buzzed, B&W
hairylunch
So, this morning I ran the half-marathon that was part of the Marathon De Mayo here in Reno. I made a map of the course here.

Here's a graph of my pace from my Nike+ iPod thing, and generated using WorkoutDump.com since nikeplus.com's analysis tools are pretty weak. Looking at the graph, it's pretty apparent I got caught up with the crowd at the start of the race, before settling into a solid pace after the first mile. You'll notice then that I started slacking on the pace. The explanation for that is in this elevation graph. The big hill was actually at the south end of the course next to the park, staring around mile 5. I decided I'd tough it out and make it up the hill, but the first drop is at the top of the hill when I was spent.

I had another drop in pace after the loop as I came upon the hill again. Once I got past there, I maintained a decent pace before I hit the small hill at the end, and I was pretty much spent, and I struggled to finish.

Oh, for those who are curious, I was 358 out of 514 with a chip time of 2:26:06. (I also happened to be the slowest person among 25 to 29 year olds). Whee!

  • 1
The graph is upside down. Also, mins/mi make me wonder what the sampling rate is. A simple distance vs time would be better with a simple moving average of the derivative.

I'd argue the inverted scale makes sense for pace, as faster paces intuitively should be higher on the graph.

The Nike+ thing samples every ten seconds. From what I've read, it's a piezoelectric accelerometer. Similar to a standard pedometer, except because it's an accelerometer, it's able to measure the time of contact with the ground, which is used in some formula to calculate your stride length and pace. (You can calibrate it to your standard run and walk so it has some baseline points.) I'd guess that the pace graph is a moving average like you suggest, except it's plotted vs. distance as opposed to time. I choose workoutplus' graph as opposed to the nikeplus.com one since the Nike one is bad at scaling the axes, and smooths excessively.

The raw XML data looks to be distance vs. time, which then gets converted to pace. I was feeling too lazy to mess around with the XML file myself, so instead just used tools I found on google.

  • 1
?

Log in

No account? Create an account