I've been sampling from the workouts on my future schedule like a Chinese menu. I want to make sure I know how to execute them. This includes fitting them into the very hilly terrain of my running routes. Today's run was 10 mile moderate 20-minute continuous alternating 5k/5k+60sec pace (roughly 6:25/7:25). I figured I should cover about 3 miles in the 20 minutes, so I'd start when the Garmin hit 5 miles, which would leave me 2 miles to "cooldown" (or at least go back to moderate). Unfortunately, 5 miles in puts me at the lowest elevation point in the routeThe first 90 sec MP/90 sec 5k was on the flat and I hit it pretty well (6:26/7:14). Then I went up a comically steep section (steeper than where I do hill sprints) and my 5k pace was 7:58. The rest of the splits times are barely correlated between fast and slow as I went up and down over hills. The graph above shows the terrain roughly although gps elevation completely stinks. I miss wearing my Suunto with the barometric altitude. If they can fit that in a reasonably sized wristwatch, why didn't they put one in the 305?
I did the rock circuit yesterday, but only did one circuit instead of two and cut down the number of pushups. I'm searching for some sort of equilibrium the lets me get through the week in one piece.
No comments:
Post a Comment