Bob, I will be right there with you in Atlanta. We can discuss it for the first 10 miles @ 8:00 pace and then decide. <img alt="biggrin.gif" src="http://files.kickrunners.com/smilies/biggrin.gif"><br><br>
Since Boston is more important to me, it wouldn't phase me if I ran the entire 26.2 at easy pace. Since it's a hilly course, it should be a strength building long run, even at easy pace. IMO, there is plenty to be gained from running it easy. Particularly in respect to physiological adaptations from the slower fat-burning pace.<br><br>
If truly using as a training run for a marathon three weeks later, I think a good approach is to run the marathon with a frame-of-mind to rebound in time for the next scheduled quality workout. I don't see any benefit of running the 26.2 in training if it takes me away from subsequent quality workouts.<br><br>
As an aside, I have backed into three of my best marathons because my A-race did not go well (once due to weather and another to flu.) Because I "pulled-the-plug" by mile 18 of my A-race, I was able to turn it around and re-race the marathon three weeks later. I applied the last 18 days of the Pfitz "Four weeks between marathons" plan as my template to make it work.<br><br>
My latest example was Grand Rapids (3:04) three weeks after Steamtown (3:16.) So, intuitively speaking, racing a marathon (three weeks out) for 18-20 miles could be argued as a good idea. Not sure I would recommend it, though.
Since Boston is more important to me, it wouldn't phase me if I ran the entire 26.2 at easy pace. Since it's a hilly course, it should be a strength building long run, even at easy pace. IMO, there is plenty to be gained from running it easy. Particularly in respect to physiological adaptations from the slower fat-burning pace.<br><br>
If truly using as a training run for a marathon three weeks later, I think a good approach is to run the marathon with a frame-of-mind to rebound in time for the next scheduled quality workout. I don't see any benefit of running the 26.2 in training if it takes me away from subsequent quality workouts.<br><br>
As an aside, I have backed into three of my best marathons because my A-race did not go well (once due to weather and another to flu.) Because I "pulled-the-plug" by mile 18 of my A-race, I was able to turn it around and re-race the marathon three weeks later. I applied the last 18 days of the Pfitz "Four weeks between marathons" plan as my template to make it work.<br><br>
My latest example was Grand Rapids (3:04) three weeks after Steamtown (3:16.) So, intuitively speaking, racing a marathon (three weeks out) for 18-20 miles could be argued as a good idea. Not sure I would recommend it, though.
