Friday, June 10, 2016

Sub3 before 73

What is the marathon question (with the emphasis on "the")? If you're thinking it’s when someone will run a sub-2 hour marathon, you would be wrong! What? How could that be! The sub-2 marathon has been, for some time, the subject of intense debate. Michael Joyner et al. (2011), in The two-hour marathon: who and when? (Journal of Applied Physiology), discussed how investigations into the physiology of the 2-hour marathon could inform who might be first and when. Using past finish times, the authors projected a when between 2022 and 2035. Joyner has long been studying the physiological factors of human endurance. He had published, in the same journal some 20 years earlier (1991), a paper on Modeling: optimal marathon performance on the basis of physiological factors. The fastest possible marathon time predicted by his model was 1:57:58. See also Phil Maffetone’s 2014 book, 1:59.

Some three months after Dennis Kimetto ran 2:02:57 at the Berlin Marathon in September 2014, a dedicated campaign, the SUB2 project, was begun to help achieve a sub-2 hour marathon within five years. The New York Times recently had a two-part article, “Man vs. Marathon,” on this project (Part1, Part2). The following figure from this article shows a projected achievement year for the sub-2 marathon in the 2030s.


Not surprisingly, the SUB2 project elicited many responses. The most critical perhaps was Ross Tucker’s article, comparing the 2-hour marathon and the 4-min mile. His objection was not that a sub-2 marathon was not possible but that it was not possible to achieve within the next five years (i.e., 2019). Alex Hutchinson took a different approach in responding, by providing a detailed analysis of what will it take to run a 2-hour marathon. A similar extrapolation of past marathon records in Hutchinson’s article as that in the SUB2 project article showed a sub-2 marathon being achieved sometime before 2030, though he ended the article with a prediction of 2075. Richard Lovett provided a similar analysis in Looking for Mr. 1:59 but without a predicted achievement year.

Of course, a sub-2 hour marathon would be a really, really big deal! But, the marathon question for me personally relates to the sub-3 hour marathon, or, more specifically, Ed Whitlock's 2:54:48 that he ran in 2004, at age 73, a world record for that age group. See two recent articles on Whitlock (1, 2). Theoretically, then, I can still run a sub-3 marathon! So, my dedicated campaign is the SUB3 project. J

Much of what Hutchinson described about the perfect race and the perfect runner that would be needed for a sub-2 marathon also applies to a sub-3 marathon. For example, one of the factors of the perfect runner is “towering self-confidence.” Hutchinson noted that “physiologists have shown that what you perceive as your physical limits depends on what you believe is possible—change your beliefs and you can push your limits.”

If I also “extrapolate” my past marathon times, my sub-3 finish would take place somewhere around 2020. J This downward trend line is representative of the adaptation to training—It is still mostly a matter of training!


The other trend, of course, is my aging curve. Aging lowers the VO2 max, decreases muscle mass, makes one less flexible, and requires longer time for healing and recovery. (VO2 max is a measure of the maximum volume of oxygen that one can use.) See Richard Lovett’s article, “The science of aging and running” (2009). Lovett wrote a related article (2015), “Mastering running as you age,” in which he discussed how to adapt to the approximately 0.7% decline in the body per year, for each major age group. There was another article that, unfortunately, I can’t locate right now that contained this key idea: The decline in long-distance running with age is relatively slow, i.e., not until around age 65 (?) does one’s potential decreases down to that of a teen. I like that! J The journal Age had a paper on the development of sport and chess performances over a lifetime (Berthelot, 2012). A characteristic growth and decline could be described by a simple model. (Here’s a summary of the paper.) Ray Fair (2007) described a similar study on age effects on rates of decline. Handy calculators based on the results from the study give predicted minimum times by age in various running and swimming events, given one’s best previous time. (Here’s a related NY Times article on Fair’s work.)

For me, there’s also a lingering outlier. Using race time predictors, my predicted and actual best times are remarkably close for all distances, except for the marathon (see figure). For the latter, even with my recent BQ time of 3:55, I’m still about 13 minutes slower than my predicted potential of 3:42. Similarly, on Athlinks, my rankings for various distances, up to the half marathon, range from a top 21% for the 10-mile to a top 34% for the 8K. For the marathon, I rank only in the top 56% (see table).



My rankings on Athlinks 
Distance
Ranking (%)
5K
28.4
8K
34.3
4M
29.8
10K
26.0
10M
20.9
13M
33.6
26M
55.8


Why is that? Typical training long runs are at about 60-90 seconds slower than one’s goal marathon pace (GMP). In the recent one to two years, my training long runs have been at only about 10-15 seconds slower than my current GMP (or BQ pace of 8:58). How come I can't seem to be able to run marathons at a much faster pace than that of training runs? True, training runs don't go 26 miles. But, is there something else? Is it a need for more mental training? Or, more physical training, e.g., to increase the strength of the back kick? Not sure, but I am working on both. The photo below (from a NY Times article on Kenya, running shoes, and bribery) shows the beautiful back kick and form in general that I'm trying to work towards.


Anyway, here’s the general plan for my SUB3 project. I don’t have a September marathon scheduled this year. Instead, before the training cycle begins for the November Harrisburg Marathon, I’ll work on speed. That will allow me, instead of using the 5K and 8K in September (that my kids and I traditionally run together) as training runs, to actually race them and try for PRs. Speed work will also help improve my efficiency for Harrisburg. My goal for the latter is 3:50 (8:47 pace), which would qualify me for Boston 2018 by 20 minutes (will be in new age group!). The qualified by 20 minutes or more group is the first one to gain entry, followed by 10 minutes or more, 5 minutes or more, and then all other time qualifiers (until all spots for that age group have been filled).

Goal for 2017: To realize my predicted potential of 3:42 (8:28 pace) and remove that lingering outlier.

Goal for 2018: To become competitive with the top finishers in my age group or ~3:30 (8:01 pace). That's around my current tempo pace. Yea, I know. J But, I do think it's realistically achievable. This is my main goal for the SUB3 project, part 1. Will see how far I get!

That would leave a couple more years to complete part 2--which is an altogether different kind of story! J

Sunday, May 29, 2016

Run without regret (Run for the Red Marathon 2016 race report)

That’s what my son said, when I told him that the Pocono Marathon two Sundays ago would be my last chance to qualify for Boston (2017) in my current age group (threshold qualifying time of 3:55). My third and last planned marathon for this year is in November, a qualifying result from which would be for Boston 2018. For the latter, I’ll be in the next age group, with 15 more minutes for BQ (threshold qualifying time of 4:10). So, I’ll all but certain qualify and actually be able to get in. I will have “aged” into qualifying. Meh! That’s why I so wanted to BQ at Pocono.


Run without regret. I really like these three words and what they represent. Perfect as a mantra, of which I made good use during Pocono’s run. It made the difference between yet another missed-the-BQ-by-just-a-few-seconds run and BQ, albeit by just making the threshold time (3:55:00).

                                          Oh, yea, oh, yea, my GPS watch says BQ!

                                                      Just ahead of the 3:55 Pacer Yoshiko

The Pocono Marathon is kind of special for me. It was here where I ran my first sub-4 marathon (2014) and, now, where I finally BQ’ed. But, with just a threshold qualifying time, my chance of actually getting in for Boston 2017 is pretty much nil—unless everyone in my age group, for some strange reason, decides not to run next year. :) I’ll still submit my registration, of course. Regardless, I’m absolutely thrilled! Before the race, I’d thought, well, if I just qualify and don’t actually get in, it doesn’t quite count. Afterwards—and after five years of trying—it feels like a pretty big deal!

At bib pickup the day before the race, I talked with the pace group people about pacing strategy. There were pace groups for 3:55 and 3:50. I needed ~3:52 or faster (to qualify and get in for 2017). So, my question was should I stay with the 3:55 pacer for the front half and then try to catch up to the 3:50 group? Or, should I go with the 3:50 pacer and try to hang on for the last 10K? At the pasta dinner hosted by the local Rotary Club the night before the race, a fellow runner sat down across from me who had been a pacer for other races. I asked him what he thought I should do. He suggested, given the course profile, I should take advantage of the elevation loss in the first 2/3 of the course and follow the 3:50 pacer and, then, just try to hang on.

Which was what I ended up doing. The following chart shows my pacing and finishing times for Pocono 2014, 2015, and 2016. It also shows the three fairly distinct segments of the course: Miles 1-18, Miles 19-23, and Miles 24-26. I’ve named the front 18 the “primrose path” and the series of rolling hills of Miles 19-23 the “buzz saw” (to the unwary!). (See course profile and map.) The last three miles are relatively flat, starting on Wallace Street, followed by N 6th Street and then Main Street, before turning into the parking lot of Stroudsburg High School and ending with a ¾ run around its stadium track—Olympic style!


The pace chart shows 4:00, 3:55, and 3:50 pacing for the first 18 miles, for 2014, 2015, and 2016, respectively. I used the even pace strategy in 2014, by staying just ahead of the 4:00 pacer pretty much all the way to the finish. In 2015, I began with the 3:55 pacer, even though that was risky, given the forecast high temperatures in the 80s. And, sure enough, that run ended with the usual “death march” after Mile 18. This year, I began with the 3:50 Pacer Dan; but, then, feeling good—and with visions of a sub-3:50!—I stepped onto the “primrose path” between Miles 5 and 16 and went ahead of Pacer Dan. He eventually caught up with me around Mile 17. We ran together the next couple miles, before he went ahead shortly after we got into the “buzz saw” segment. What saved me this year was the almost ideal temperature, which began in the upper 30s and ended in the upper 50s. The cool temperatures helped me contain the upward trend of the “death march.” The forecast ~15 mph wind turned out to be not much of a factor. This year, then, I used the “banking time” strategy—though not on purpose! (This strategy, of course, is not recommended.)

                                  Pocono Marathon course profile: Net elevation loss, but deceptive!



                                 Pocono Marathon course map

The pace chart also shows the importance of pacers. Pacer Dan helped me maintain a sub-3:50 pace for the front 18. That “banked time” mitigated my error of succumbing to the temptation of the “primrose path.” But, what really helped me cross the finish line not one second slower and, thus, BQ was having Pacer Yoshiko pass me shortly after I got out of the “buzz saw” and onto Wallace Street. As I was struggling through the “buzz saw,” and as those mile splits steadily slowed, I saw my BQ slipping away. I kept saying to myself, you blew it—and all kinds of other negative things! On Wallace Street, with three miles left, I felt as I had nothing left.

But, then, something happened, as Pacer Yoshiko passed me with some words of encouragement. It brought back the thought of running without regret. I said, damn it, I’m not going to miss BQ again by a few seconds, regardless of my earlier pacing error. I'm not going to, on the drive home, once again regret that I was not able to run a few seconds faster over 26 miles. Or, chose not to.

It was the first time I felt I was able to really reach deep down and tap into that 50-65% unused potential that the body reserves to prevent catastrophic failure. (See Tim Noakes’ 2012 review article in Frontiers in Physiology, "Fatigue is a brain-derived emotion that regulates the exercise behavior to ensure the protection of whole body homeostasis.") I thought if I could just keep Pacer Yoshiko in sight, then I’d still have a chance to BQ. Many pacers run to finish with a few seconds to spare. I took a final 5-second walk right before the turn onto Main Street, around Mile 25, and just hanged on for that last mile. I don’t know how I did it—that last mile was kind of blurry—other than just one stride at a time. My pace even got slightly faster. Pacer Yoshiko then did a really nice thing; using some of those spare seconds, she stopped at the entrance to the Stroudsburg High School stadium and said “You did it!” as she encouraged everyone onto the track. She then followed me to the finish.


So, that was how I finally, after five years of trying, managed to BQ--with not a fraction of a second to spare. :)

I’ve written about the Pocono Marathon itself the previous two years (Pocono 2014, Pocono 2015). Here are a few more details:

- The national anthem right before the start was one of the best renditions I’ve heard in all the races I’ve been to. I found out later that the singers were a group of students from the Pocono Mountain East High School. Very impressive!
- As usual, the volunteers were superb. Helpful and cheerful, sunshine or rain. There was a period of the latter, not too heavy but cold, around Miles 17-18. I was glad that I’d decided not to dress for the finish temperature (in shorts) and went for, instead, a pair of light tights.
- I love that volunteer who stood at the top of the last significant hill before Wallace Street around the beginning of Mile 24 and said, this is the last hill, I promise!
- For a mostly non-city race, the spectator support was really good and helpful. Numbers varied along the course but were particularly high around Mile 9, at the intersection of Routes 314 and 611, and at the half way point, shortly after turning from Red Rock Road onto Route 191, a main road going down to Stroudsburg.
- Race shirt is short-sleeved this year, with a nice and simple design.



Of course, I’ve been rethinking quite a bit about my pacing decision and implementation. Had I not gone onto the “primrose path” and, instead, stayed with Pacer Dan, would I have been able to keep up with him longer? Had I started with Pacer Yoshiko, would I have been able to better negotiate the “buzz saw” and perhaps push ahead of her in those last three miles? Either way, could I have finished three minutes faster (3:52)? I would never know, of course.

No matter: Boston qualified, I am. :) And, I ran without regret!

Saturday, March 26, 2016

Mental lapse (Rock 'n' Roll Washington DC Marathon race report)

Of course, at the time, as I was going up the hills on Fort Dupont Drive SE in Fort Circle Park (Mile 23 of the Rock 'n' Roll Washington DC Marathon), what I was doing didn't occur to me as a "mental lapse." I had one gel in my wrist wallet that was planned for Mile 20; but, I couldn't get it out of the wallet while running. With six miles left, I figured I'll just skip it. Once I got to those hills, however, I thought maybe I better still take it. So, I slowed to a fast walk, got the gel out, and was then supposed to pick up the pace again, as I down the gel over the next 1/4 mile or so. Once those legs started walking, however, they just kept on walking! I rationalized by telling myself that a fast walk up a hill is not that much slower than a slow run. :) The following map of the last 10K of the course shows the location of the Fort Circle Park hills. (All maps shown are annotated versions of parts of the course map on the RnR Web site)


By the time I finally convinced my legs to get moving again, about a minute had gone by. For that Mile 23, my pace ended up some 90 seconds slower than the average of the previous 22 miles. So, by how much did I miss my BQ? 49 seconds!

One cause of the mental lapse, I think, was my overconfidence. I thought I had it. I was passing people for much of the front half. Now, usually, that would have been of some concern. But, I wasn't straining; my average pace of 8:47 felt easy. Then, as I was heading into the hairpin part of the course (First St SW, Mile 16), I saw the 3:40 pace group coming out. I didn't know at the time how far in the hairpin goes; but, in my mind, seeing the 3:40 just added to my confidence. Unjustifiably, as it turned out. I was actually about 1-1/2 mile behind the 3:40 group, at that point, or about 13 minutes. 3:40 plus 13 is 3:53, which is borderline for me actually getting into Boston. My BQ of 3:55 would not be sufficient, based on the past few years. Had I known all this at the time, that mental lapse seven miles later might not have occurred. About a mile later, as I was heading out of the hairpin (2nd St SW, Mile 17), I saw the 3:55 pace group still heading in towards the turnaround point. That, totally unjustifiably, solidified my confidence. I was thinking to myself that I just have to stay ahead of the 3:55 group and try to catch up with the 3:40 group--I got it! I was still confident, as I was approaching the finish line. Or, I must have been hallucinating. Because, when I checked my GPS watch, I was sure I saw 3:52 something. So, I was all smiles crossing the line. The digital "5" and "2" could easily be misread--especially when one's mind is zoned out!

At least my finish line photos showed an exhilarated, photogenic runner!


What I didn't ask and should have asked of the pace groups was from which corrals did they start? That information was critical, because several minutes separated each of the starting corrals/waves (some 30 in all). Similarly, shortly after coming out of Fort Circle Park, about half way into Mile 25 along Minnesota Ave SE (see course map of last 10K above), I passed a different 3:55 pacer, all by herself at that point. But, without knowing her starting corral, I couldn't determine where I was with respect to my BQ.

Overall, my strategy for the race went according to plan (pacing, fueling, water stops, etc.) and worked well. As planned, I took a gel just before the start, four dates each at Miles 5, 10, and 15, and that gel at Mile 23. I skipped a couple water stops; otherwise, I sipped about half a cup over a 10-count walk through each stop.

What happened during Mile 23 was a tactical error resulting from a 60-second mental lapse. I should have slow run those Fort Circle Park hills. As the following pace chart shows, except for Miles 23 and 24, I maintained a generally even pace, with just a very slightly positive split. And, I was able to bring the pace back down to ~nine minutes again for the last two miles. There was no wall.

I should have BQ'ed. I had it but then lost it. The fact that a mental lapse-free finish time would most likely not have been enough to get me into Boston 2017 is small consolation.

I do like very much that, between 2013 (the other time I ran this race) and this year, my pace improved by about one minute or a finish time of about 26 minutes, and there was no "hockey stick" finish. Plus, my finish time of 3:55:49 was a 31-second PR, relative to last November's Harrisburg Marathon; and, unlike Harrisburg, the new PR was run without a pacer. Like fine wine, getting better with age!


This being a Rock 'n' Roll race, there was plenty of music. Loud music. Though, in some stretches of the second half of the course, it was too quiet. Part of the reason might be that, of the total field of about 20K runners (for marathon and half marathon), only about 1/8 ran the marathon. No wonder, then, once the marathoners split away from the half'ers just before Mile 13 and headed along East Capitol St NE towards the Supreme Court, it got noticeably quieter!


Overall, the race was well managed. The course was very runner friendly. The corral/wave starts created space for everyone to run his or her pace, even though this was a big city race. UPS gear check was efficient. The first 2/3 mile along the wide Constitution Ave., with the Washington Monument on the left and the White House on the right, allowed the runners to sort themselves out and avoid the usual congestion. Spectator support was great, especially through the Adams Morgan neighborhood, shortly after the hill up to Calvert St NW. And, all the support people at water stops were very friendly and efficient. A big thanks to all of them!

The weather was also well managed. Rain was forecast up until a few days before the race. Instead, it was just cloudy, with temperatures in the 50's for the entire race. Almost ideal.

And, for finishers, a nice "heavy medal" and light jacket. Though, for the latter, I would have preferred one without "FINISHER."




I've just a few gripes. Pacers were not well marked. At least I didn't see any in my starting corral (#8). Also, their starting corral numbers should be visible on them somewhere. I much more prefer the chip on the bib, instead of the loop kind held by shoe laces. I like to tie my shoes with just the right amount of tightness, and looping the laces through the chip interferes somewhat with that. Porta- potties: Start line area could use a few more (well, most races could use a few more!).

I now have just one more chance to qualify for Boston (2017) in my current age group, before I would age into qualifying (for 2018)--which would be far less satisfying. I've a shortened 8-week training cycle before the Pocono Marathon in May, to figure out how to lapse-proof the mental part of my race.

Monday, February 15, 2016

My legs were like, whoa, running outside on the road!

Two Saturdays ago, I participated in a stride clinic offered by my local runners club (MCRRC). Then, on the day after, I did my weekly long run (20M) at a pace, for the first time ever, faster than my BQ pace--by 10s. Coincidence? I think mostly so. Now, even though much of what I heard at the clinic I had already read from books and articles, what I did learn that's really important was that what I thought I've been paying attention to (mindful of) and doing in my training runs might not have been quite what I actually have been doing, at least not all the time. During that Sunday's run, I was more mindful (than usual) of my form and stride, and, perhaps, doing that improved my efficiency and thus pace. Still, I think it's mostly coincidence that my "PR long run pace" (8:48) immediately followed the clinic. I'd give more credit to the two Snowzilla-imposed treadmill runs (18 and 19M). I think my legs were just so ecstatic to be running outside that they were beside themselves. :)

The following pace chart shows the mile splits for both the post-clinic run (Feb. 7) and yesterday's 21M run on the treadmill (Feb. 14). The two red lines mark my GMP (8:58) and stretch GMP (8:30). Because 8:58 would not actually get me into Boston (need ~8:51), I've been mentally using 8:30 as the goal pace. For the Feb. 7 run, around Miles 5 and 10, I was fumbling with gloved hands a plastic bag of dates; and, around Mile 15, PowerGel. So, the pace slowed a bit for those miles. The chart also shows a generally even pace running outside vs. a controlled negative split pace on the treadmill.


So, what happened on Feb. 7? It was a training run, just myself, without the advantage of a race situation. I wasn't really trying to run sub-GMP; the pace just felt relatively easy. I can think of two possible factors, one related to all those treadmill runs I've been doing recently (14 so far this year, including this morning's) and the other related to some changes I've made in how I do lunges in pre- and post-run exercises.

A treadmill enforces pace--and enforces it absolutely! It's the "perfect" pacer. Running outside, of course, is always more preferred. But, when it's icy or sub-zero windchill, though the scenery may still beckon, the quality of the run will necessarily suffer. In contrast, on a treadmill, I can plan out exactly each mile split, for each kind of run (tempo, easy, etc). Perhaps, from all those times when I opted for quality over scenery and ran on the treadmill, I've gotten used to running and sustaining sub-GMP's. Perhaps, the treadmill has trained my mind to be comfortable with dropping ~7s per mile (0.1 mph) in the last 10K of a long run, from what's already a sub-GMP just before the 10K. The latter kind of 10K was what I did on the Feb. 14 run. Because running on a treadmill is like running with a pacer, a particular pace seems easier on a treadmill than it is on a road by myself. The difference in perception of effort from increasing by 0.1 mph from mile to mile is very slight; and, yet, from the first to the last mile of the last 10K of a long run, there's a 35-second or so difference in pace!

As I had noted in my post on those Snowzilla runs on the treadmill, if one is mindful about running, then whether it's on a treadmill or on a road or trail outside should make little difference. By breaking the long run into 5-mile segments and focusing on the current segment and its components (each mile, each 0.1-mile, etc.), I'm starting to find running on a treadmill to be, well, not too bad. :) At least, I no longer think of it as "dreadmill"! I think these treadmill runs are helping to strengthen the mental aspect of long runs. Being mindful is not just of form and stride, but also of fatigue. Being mindful of fatigue, though, does not mean dwelling on it, but, rather, acknowledging it and moving on. So, to the mantra that was so useful in Pocono 2014, "dumb it down," I now add, "let it pass."

Some months ago, I began doing lunges that are in the pre- and post-run exercises as if they're part of Tai Chi Chuan (Tai Ji Quan)--slowly, mindfully. I think the strengthening of the legs, as a result, is one factor in the recent pace improvement. Here are couple illustrations of the lunge element in Tai Chi (from googling "taiji images").



There could be other factors. I've been experimenting with dates replacing gels. In the Feb. 14 run, I fueled with 4 dates each at Miles 5, 10, and 15. No gels at all. But, I don't know yet what difference fueling with dates makes. I haven't yet decided how exactly I'll fuel for the upcoming March RnR USA marathon.

Regardless of whatever explanatory factors, I feel the Feb. 7 run is another occurrence of punctuated equilibria. Right now, I'm feeling cautiously optimistic about BQ'ing in the March race. :)

And those legs? They're still talking about that morning's high!

Tuesday, January 26, 2016

#blizzard2016 long run

Last week, as I was following the weather reports on the approaching Snowzilla Jonas and the minimum 18" that were forecast for my area, I was thinking (dreading?) about the upcoming Sunday 18-mile run that will have to be done on the treadmill. Here's my preparation the night before (4 dates @ at Miles 5 and 10; PowerGel at Mile 15).


The previous longest distance I've run on a treadmill was something like 13 miles, so I wasn't totally sure I could go the distance. The NordicTrack goes erratic when the duration exceeds an hour and sometimes just stops. Maybe the programmer didn't think anyone could handle the "dreadmill" for more than 60 minutes and left out the "if (duration > 60)" part. Anyway, that was partly why I reset it every 5 miles, each time taking about 10 seconds, while my cell phone stopwatch continued. Thus breaking the 18 miles into four parts, 3 x 5 miles and 1 x 5K, helped somewhat the mental aspect of the run. At least, "dreadmill" became just treadmill.

Still, 18 miles on the treadmill was a lot tougher than 18 miles on the road! This was so, even though I didn't simulate the hills of my usual long run route and kept the treadmill level for the entire run. And, I didn't carry the water bottle. To break the monotony, I made full use of the WBS (Work Breakdown Structure) applied to running (see Running WBS, Intestinal runs, and Running WBS (2)). Starting with the 18 miles in four parts and Miles 5, 10, and 15 being fuel+water breaks, I further broke the run down with water breaks every 2.5 miles and then individual miles of each 5-mile segment, as follow:

Mile 1: Warm-up, getting into the rhythm (even after the first 5-mile segment).
Mile 2: "Historical," especially the second 0.5 mile. The NordicTrack shows distance with three decimals (i.e., 1.xxx). So, 1.620 would be Pilgrims at Plymouth; 1.776 would be Declaration of Independence; 1.860+ would be Civil War, etc. Once the distance gets to 1.900, the historical events get more personal (birth years, high school, college, work, etc.).
Mile 3: Water break at mid-point.
Mile 4: Toughest mile of the five!
Mile 5: Fuel intake starting at ~4.500; first date until ~4.700; second date until ~4.900; third date just before 5.000 then water; fourth date just after resetting the treadmill for the next 5-mile segment (more on this later). At Mile 15 (end of third 5-mile segment), PowerGel starting at ~4.500 and mostly finished just before 5.000 then water; last bit of gel just after resetting the treadmill for the final 5K segment.

Beyond the individual miles, there were the individual tenths of a mile. And, ultimately, there was the present moment and being mindful of it, so that, as I ran, I knew I was running. I knew whether or not I was relaxed; I knew on what part of my soles I was landing; I knew whether or not I was breathing properly. Ultimately, being mindful makes running on a treadmill not that different from running outside.

Back to why that fourth date just after resetting the treadmill and starting the next segment. I didn't take water after the fourth date, so the sweetness lingered in the mouth. I'm still testing the results from Chambers et al. (2009), who showed how rinsing the mouth with a carbohydrate solution without swallowing affected performance. For the same reason, I took that last bit of PowerGel at the start of the last 5K segment.

Another thought occurred to me during the run, as I was looking at the open container of dates. Usually, on an outside run, the dates would be in a plastic bag and out of sight in my hand. On the treadmill, those dates were staring at me. Could there be some biochemical effect (on performance) from the visual cues of dates? :)

Anyway, what was the result of 18 miles of mindfulness? An average pace that's just one second slower than my current marathon PR pace set at Harrisburg.


Oh, if I could only maintain this kind of pace in an actual race--overall even and progressively negative! Of course, using the treadmill as a pacer did make this part of the mental aspect easier. For the past couple some years, my GMP of 8:58 would not have been enough to actually get into Boston. I would have needed about 8:51. So, for the current 16-week training cycle, I've been using 8:30 as a stretch GMP on which to base my long runs.

In case I've gotten you all eager to jump on a treadmill, here are some treadmill workouts. :)

As for me, after this #blizzard2016 long run, I went outside and did 8 x 1 hour core exercises--of the non-standard kind.







Saturday, January 2, 2016

Like fine wine, getting better with age

Day 2 of the new year. A good time to take a look at what's coming up. I've three marathons planned for the year, two in the spring (Rock 'n' Roll DC in March and Pocono in May) and one in late fall (Harrisburg in November). All are repeats. 2016 is the last year I can still qualify for Boston in my current age group (3:55). Only RNR and Pocono would be in time for Boston 2017; Harrisburg would be for Boston 2018. By then, I'll be in the next age group, with an additional 15 minutes for qualifying (4:10). I've already run three races faster than 4:10 (two under 4:00). Mentally, I now expect myself to finish under 4:00 for all future races. Thus, for Boston 2018, I would basically "age" into qualifying, which is not very satisfying. It wouldn't feel as I "earned" it. :) Which is why all three 2016 races but especially the two in the spring will be run on familiar courses. I want to keep the number of variables as low as possible. I feel quite good right now, in Week 6 of the 16-week training cycle for RNR, and cautiously optimistic about "earning" my BQ in one or both of the spring races. :)

One scheduling change I've made is to not do an early September race. A race at that time (e.g., Potomac) would mean another opportunity to qualify for Boston 2017. But, the Washington, DC summer being what it is, it's just too hard to properly train and be ready by September. Instead, I plan to modify the first half of the 16-week training cycle for Harrisburg to partly train for speed. This way, I'll be able to actually race the 5K and 8K in September that my kids and I have traditionally run together. Those are always a lot of fun. In recent years, with the focus almost solely on qualifying for Boston, all the shorter races (half marathon and shorter) have become basically training runs; or, in the case of last year's September 5K, which was on the day after the Potomac Marathon, a post-marathon evaluation run!

Before totally leaving 2015, a quick look back. The 3-minute PR at Harrisburg definitely tops the list. But, the Walnut Creek Half Marathon time is a new course PR (previous one was two years ago). And, in all the shorter races, the finish times are all within the year-to-year delta--even with no focused speed training. What else?

The most scenic course? Golden Gate Trail Half.


The most photogenic finish? Kensington 8K. At least compared to the more usual finish with the gaping mouth. :)



So, my finish times are still improving; the adaptation curve is still staying above the aging curve; it's still mostly a matter of training. This is the advantage of starting serious training later in life, past the prime long distance running age of around 30. Most of one's PRs are still ahead! With that in mind, I plotted my marathon finish times for the last five years, since I began seriously to train, and to train for Boston. I excluded one of the 12 marathons completed, the Grandfather Mountain Marathon, which is basically, well, running up Grandfather Mountain. It's not really comparable to the other 11. The trend line for the plot shows a nice downward slope with increasing years--and age. In fact, if one were to extend the line, it would eventually intersect a finish time of 3:00 at around the year 2020 ... :) :) :)


Like fine wine, getting better with age!

Monday, December 28, 2015

"Pacers are electrolytes for the soul." (Harrisburg Marathon race report)

The title quote is from a Runner's World article by Laura Beachy on her first 100-miler. It's #9 in her list of 15 observations/lessons learned. As I had previously noted (Treadmill as pacer), running with a pacer is kind of like running on a treadmill; the mental effort is greatly reduced.

The advantage of having a pacer is especially significant in ultra races but also makes a big difference in marathons. Over ultra distances, pacers provide such an advantage that rules exist as to when they are allowed. In the Western States 100, pacers are allowed starting at the Foresthill School aid station at ~Mile 62 (http://www.wser.org/pacer-rules/). In the Tahoe 200, for most runners, pacers are allowed starting at the Camp Sacramento aid station at ~Mile 110 (http://www.tahoe200.com/crew-pacing/).


In the Harrisburg Marathon seven weeks ago, pacer Dan provided me with the much-needed electrolytes. In contrast to Pocono 2015 in May, the weather for Harrisburg was almost ideal. The course was a new, flatter one that thankfully avoided those hills around Wildwood Lake. It also replaced the drab, monotonous Industrial Road with the scenic Capital Area Greenbelt and North Front Street along the Susquehanna River. The course maps below are from the race Web site, with my added annotations.




I had no excuses. But, I had pacer Dan.

The result was a new 3-minute PR (3:56:20). I am mostly thrilled and only slightly disappointed in missing the 3:55 BQ (in part because 3:55 would not have been enough to actually get into Boston; I would have needed 3:52:32, based on the 2015 times). After the turnaround near Mile 18, just past Fort Hunter, and going downstream, pacer Dan said we just needed to coast to the finish line. In that moment of what turned out to be premature self-congratulation, I was thinking could this race finally be the one in which I qualify for Boston, such a beautiful day and all!

But, alas, it was not to be. The dreaded Mile 20 came and went without incident. But, in Mile 25, I was off pace (from the 3:55 pace group) by ~20 seconds, and in Mile 26, by ~60 seconds. The problem actually began just before Mile 25, at the aid station. I was just a few steps behind pacer Dan and the few runners who were still with him. The pace group did a 10-second walk through the station for water. In hindsight, I shouldn’t have stopped for water myself and, instead, should have tried to catch up. There was no need for water that close to the finish. I think I just wanted to rest for a few steps, and the water stop provided an excuse. It’s a lot easier to stay with, than to catch up to, a group, especially mentally. In hindsight, what I did was a tactical error—and a valuable lesson learned!

Also, in hindsight, of course, I questioned whether I could have caught up with the pace group, if I had really wanted to. I questioned that if I couldn’t BQ under such ideal weather conditions, then could I ever? I questioned whether I had given up and already decided to not finish under 3:55, just as, according to the Noakes 2012 review article on fatigue, exercise, and homeostasis, those who finish behind the winner may have already, even before a race starts, decided to not finish first. If something really critical was at stake, surely I could have run 3:55? My overall pace was only three seconds slower than my BQ pace. Surely, I could have run three seconds per mile faster? And, of course, there’s that end spurt down Second Street to the finish line. If I had nothing left, where did that spurt come from?

But, I also went easy on myself. I asked whether I got as close to 3:55 as I did because I didn’t give up and because the weather was so ideal. I had all these thoughts, even though a 3:55 wouldn’t have been enough to actually get into Boston 2017. One thing for sure, though: I didn’t walk (other than through the planned water stops), and there was no wall! And, I got the new PR with a shortened 8-week training cycle, coming after Potomac 2015 in September, with relatively low weekly mileage (in the 40s) and only three good long runs.

For Harrisburg, I added a new mental aid to the usual mantras, counting strides, and counting breaths. My predicted finish times from those race time predictors are quite close to my actual times, for all distances but the marathon. For the latter, the predicted time is ~3:45. So, during the race, I kept reminding myself that I ought to be able to run faster than my BQ time. I think that helped my confidence in being able to keep up with pacer Dan. Overall, though, I still need a lot more training for that 90% mental part of a race. Of the mental obstacles discussed in a recent article, "The Racer's Brain," hitting the wall or, more to the point, running through the wall is where my work lies.

On the physical side, I was able to do something different in Harrisburg. In past races, I usually could only take three gels, at around Miles 5, 10, and 15. Usually, around Mile 19 or 20, the body refuses that 4th planned gel. This time, I took a gel before the start and four more, as planned. I skipped only the 6th optional one (gel picked up at the Mile 18.8 aid station). The table below shows the miles at which I took gels and then water at about half mile or so later. So, physically, I had more energy in my system in Harrisburg, compared with that in previous races. But, there was also a mental aspect. Previously, I’d wash all the gel down with water. This time, taking a cue from Chambers et al. (2009), who showed how rinsing the mouth with a carbohydrate solution without swallowing affected performance, I left some of the gel in the mouth. Now, I’ve no idea how that affected my performance; but, I figured it couldn’t hurt—though, my dentist surely would not have approved! One other detail: I had both the gooey type of gel (Gu or Clif Shot) and the more liquidity type (PowerGel). Of the five gels, the first three were gooey and the last two were liquidity. The latter type goes down more easily in the later miles of a race. I actually numbered the five gels, so I didn’t have to think about which one to take next during the race.


The new Harrisburg course is great—a much better Boston qualifier! And more scenic: Photo below shows the course near the end of Mile 11, approaching the Harrisburg Sunken Garden along the Susquehanna River, with Harvey Taylor Bridge in the background.


The finish line on Second Street is also much better, for both the runners and spectators.


The race organizers did a nice job in implementing the many changes from last year, with one exception (see below). They were also responsive to runners’ comments regarding Industrial Road and Wildwood Lake and, perhaps (?), to mine on putting the race date on swag. This year, both the finisher medal and sweatshirt (a nice change from tech shirts) had the race date on them.

 

Volunteers were, as usual, superb. A big thanks to them all! During the race, I didn't always remember to do so.

I don’t usually buy race photos. But, this time, the pricing was reasonable enough that I actually bought some, this being a new PR race! If it were up to me, I'd price race photos at $10-20 and include them in the registration (with an opt-out selection) for unlimited digital access. Prints and other value-added products can cost more. So far, only one race I’ve done, RunTheBluegrass, had this option.

I’ve only one small complaint: It took a while to find where the checked bags were delivered to. No one seemed to know, perhaps because this was the first time that the start and end of the race were not co-located.

And, I’ve one suggestion: Put first names on bibs, so one could address other runners by names instead of numbers. In my case, because I was wearing my Wineglass 2013 shirt, some of the spectators called out encouragements to "Wineglass." J

It’s really nice to see the “3” in front of my marathon time. Harrisburg 2015 is my second sub-4:00; so, Pocono 2014 is no longer a fluke! I've three marathons planned for 2016. But, only the two in the spring would be in time for Boston 2017, when I'll still be in my current age group. I'd rather not "age" into qualifying. J For those two spring marathons, I'll be looking for my electrolytes!

Friday, November 6, 2015

Finishing in the rain (Abebe Bikila Day International Peace Marathon race report)

This is a short report; in fact, it could be as short as ...

I finished.


And, that was not just trying to manage expectations. For this race some eight weekends ago, crossing the finish line was almost the sole thought in my mind from start to finish. Well, other than that nagging one from my only DNF at this race last year. Even though I've completed two other marathons since that DNF, I had to complete this one, in order to put that DNF thought completely to rest. The mental aspect of a DNF is very real, and a decision to not finish, as Brian Morrison had said, shouldn't be taken lightly, because "once you drop that first time, it gets easier and easier to throw in the towel." (See #4 in the article, "The long and short of running wisdom.")

As for the race itself, many of the details are already in my Potomac (Abebe Bikila Day International Peace) Marathon race report from last year. Here, I mention just a few more items specific to this year's race.

It began with a rainbow welcoming all the runners.


But, then the rain began. The course was 6.55M out and back along the C&O Canal Towpath, starting from Fletcher's Cove, done twice. It's a beautiful course, shown here before the start, when everything was still calm and dry.


At the end of the first out-and-back, the Towpath was already pockmarked with pools of accumulated rainwater. Initially, I went for the grassy sides of the path--which was a bad idea, as water from the saturated soil flooded my shoes. It turned out to be better, and the shoes actually remained drier, to stay on the path and just run through the pools. They were shallow enough that most of the water splashed away from the shoes. I was wearing my relatively new Merrell Bare Access (MBA) 4 trail shoes.


One very nice feature they have, which I didn't know when I bought them, is effective drainage. So, those flooded shoes soon felt "dry." Being trail shoes, their soles are relatively thick. But, despite the soles, the shoes are remarkably light. The fit is not as snug as that of the Merrell Trail Glove (still my favorite!). But, overall, I like the MBA 4.

Anyway, back to the rain. A lot of credit has to go to the race organizers and, even more, those wonderful, persevering volunteers at all the aid stations and the post-finish recovery area. The rain gradually intensified during my second out-and-back. (I was really glad I had my hat on!) But, it really began to pour not too long after I'd crossed the finish line.

I finished in 4:28. There were actually several races going on at the same time: 3 starting times, with an hour stagger in between, and runners for both the half and the full. So, at any given time, it's hard to know which group(s) the runners around me belonged to. Basically, I was running alone for the entire race. That factor, along with the rain, probably contributed to my relatively slow time. Mostly, though, it was the incomplete training cycle over the previous 16 weeks, interrupted by work-related travel and various other activities. I ran only three good long runs, out of the scheduled 9-10 runs. Plus, the long hot summer. Then, of course, there was that DNF factor. I ran very conservatively, continually reminding myself that, no matter what, I have to cross that finish line!

So, it was a soggy but satisfied drive back home, nourished, along the way, by one of my favorites: Injera!




Running forward ... on climate - An update

An unexpected update.

When I last wrote about the Forward on Climate Rally (the only post I've written thus far that's not really about running), I said that I came back from the rally hopeful, not because I expected President Obama would reject the Keystone XL pipeline, but because of the multi-generational makeup of the crowd, particularly the younger generation. That hopefulness was for the long run (no pun intended!), not for the rejection of the pipeline.

So, today was quite a pleasant surprise! Whether the Obama administration deliberately timed today's announcement to reject the pipeline to be sort of an opening statement for the upcoming Paris climate talks or the upcoming talks spurred the deliberation and decision making, or whether President Obama is truly out of fucks--wouldn't it be nice if politicians would all operate in a low fuckery mode all the time?--he decided on the side of our children and all future generations. We should thank President Obama for his decision. But, I agree with 350.org that the decision (I'd add "probably") wouldn't have happened without all the people that was the movement that fought the Keystone XL. A big thanks should go to all those people.