Custom Search

Monday, October 3, 2016

Marathon training, week 13

Monday: 10 total. This was 6 x 1 mile in the park with a quarter mile jog between. As usual, my pace slowed drastically after it got dark. 6:37, 6:34, 6:40, 6:42, 6:46, 6:44. You want to know how to have the park COMPLETELY to yourself? Run at night, in the dark, in 99% humidity with oppressive heat lightening all around you, during a Saints game. That's how.
Tuesday: Off.
Wednesday: 11 total: my last tempo! Unfortunately, I was running on 6% Garmin charge, and it didn't make it to the end. Too bad, because for my last tempo I wanted to purposefully hammer mile one, then recover and still manage a good overall tempo pace. This was just in case I screwed up the start of the marathon. Now I'm not sure if I did, but I do know the distance (I had the route perfectly calculated so I could ensure I'd make it to work on time), and I tried to maintain the same pace by feel. Hopefully I did. 6:55, 7:09, 7:12, 7:15, 7:07. 7:08,7:12, 7:08, ?, ?. By the way, if you noticed my tempo paces getting faster toward the end of this training cycle, it's not better fitness. It's just a function of this Garmin 620 compared to the Garmin 305. The lap pace showing as you run doesn't update as often due to how the data smoothing is executed, so when the mile actually beeps, sometimes I'm surprised. 
Speaking of Garmins, this tempo run was how I messed up my pace in Saturday's race: I didn't realize that my Garmin wouldn't turn on because it had a dead battery because I thought I charged it. So I thought I needed to reset it. Then I saw that, actually, it had no battery. Once I reset the data screens, i messed it all up. Drama. 
Thursday: 8 oh-so-easy.
Friday: 8 easy. 
Saturday: 6+ total. Blue Doo 2-mile race. I warmed up to the race, grabbed my shirt, ran home and dropped it off, and ran back. Then I ran the 2-mile race (I just realized I forgot to do pre-race strides! Darn!). I ran a lovely 6:11 followed by a terrible 6:25. Woot. Then I ran home. 
Sunday: 4 easy on soft surfaces. This was intended to be 8, but you know what? My legs were tired, and running over 50 miles the week before a marathon sounds like a terrible idea. I've tried to stick very closely to the Hanson's plan, but I called it a day at the halfway point because my legs felt like they weighed a million pounds. 
Total: 47 miles.

That's more than my maximum weekly mileage for some training build-ups! And it's right before the marathon! So here I am, ready for this race I suppose. I'm very glad I ran the two-miler. Not just because I won, since that's largely a function of who didn't run that day, but also because even totally inappropriate tune-up races like a 2-miler before a marathon can still boost confidence. For me, it was mostly that I was positive I'd end up hurt before or at the marathon. Were my hips ok? Did my knee bother me? Why is my foot bruised? Then I ran the little race, and everything was totally fine. So I think Sunday will be fine, too. Now it just remains for me to see how long I can actually hold race pace on race day! 


  1. Ufda, that is a big week before the marathon! It's tough to trust the training when the program is SO different from what you are used to! I hope that you have a great race experience on Sunday! I'm looking forward to seeing you out on the course. Send me an email and let me know what you'll be wearing so I can keep an eye out for you. I'll be on the left side of the road around mile 21 or 22. Hopefully I can spot you!

    1. Exciting! I emailed my brother for some details about the schedule, but didn't hear back yet - I will try to get together with you and, if nothing works out, definitely let you know what I'll be wearing!

  2. Woo! Can't wait to see you how do!

  3. Good luck! I heard the forecast for Twin Cities is pretty good!

  4. Good luck! I heard the forecast for Twin Cities is pretty good!