No, I'm not running in my marathon shoes anymore—I'm using them as everyday shoes. Yet, I can't bring myself to take my timing chip off. Sure, if anyone has an RFID reader, they'll be able to pick up my name, age, and hometown, but how many people carry RFID readers and hold them up to people's shoes?
Another reminder of the marathon that lingers is my watch. No, it isn't normal to get rid of your watch after a marathon. What does remain is my split times in the memory of my watch. This isn't too big of a problem (my watch has a 150 lap memory, and the marathon takes up 27 of those laps), but I don't know how to erase individual workouts. So, if I save a set of hill repeats or some intervals, I can't delete just that workout, leaving me with the choice of deleting all workouts (including the marathon) or deleting none of them. I'm down to about 70 laps left, so the day when I have to erase the marathon is fast approaching.
Geeky engineer alert! Data ahead!
That day won't be too bad, though, because I've already recorded the data. Today, I analyzed the data:
Here's a plot of my split time for each mile. Excel isn't too great at working with times, so the y-axis has some funky gradations. You'll note that my average pace up through mile 17 was 10:20—which is almost exactly a four-and-a-half hour pace, which was my goal. If you remember, mile 18 is where my quad got all funky, and my pace slowed considerably (the overall average pace was 11:02). All this to say that had it not been for my quad, I would have hit my goal time. Of course, other things could have happened, and my main goal was to finish. This year, however, I already know I can finish the marathon, and I've got my sights set on a sub-4-hour time.
No comments:
Post a Comment