Tuesday, December 17, 2019

2019 Marathon race report, part 2




In Part 1 I described my race. Here I will describe the training I did.

A typical marathon training plan is pretty straightforward. A long run on the weekend that builds in length to a longest run three to four weeks before the race, then a gradual reduction in duration. There is a lot of debate about how long the longest run needs to be. Hal Higden insists that 20 miles is perfect. Others go for 25. A few take the position that running more than the goal race makes the race distance feel easy. During the week a beginner plan will have three days of easy runs, while advanced plans will include some speed work and a couple more foundation runs. Really advanced runners will do two-a-days. The key metric is weekly mileage.

The problem with this approach is getting to the start line healthy. Eighty percent of endurance runners report dealing with a run-related injury. Not being hit by a car, or bitten by a dog, or tripping over a crack in the road. The most common type of running injuries are repetitive stress injuries. Running all those miles, day in and day out. Too many miles, not enough recovery time. And, bad news for me, the older we get, the more recovery time we need.

Why do we run so much? I can think of three reasons. First, to build endurance. Second, to build muscular endurance. And third, to develop skill, to practice the movements of running in order to increase efficiency. What, I hear you ask, is the difference between endurance and muscular endurance? I use these terms the way Joe Friel does, which may or may not be common throughout sports science.

Endurance. The ability to persist or to resist fatigue for a relatively long duration.

Muscular endurance. The ability to produce the required force for the required duration in order to achieve the desired goal.

The quality of endurance is primarily about the cardiovascular system's ability to sustain activity. Doing some form of exercise for a prolonged period of time. Muscular endurance, as the name implies, is about the muscles, but also the nutritional delivery systems that impact how long a muscle can perform.

Endurance is developed by long duration, low intensity workouts. Muscular endurance is developed by moderately high intensity efforts for moderate duration. High intensity workouts often incorporate intervals to increase the total work period by dividing it into manageable sections with recovery in between. Runners often use a tempo run to achieve the same result, running at a pace well below threshold that they can hold for an hour -- their 10K pace -- without any recovery periods.

As we progress from developing endurance to muscular endurance to skill the nature of the work -- the way we move -- becomes increasingly specific to the goal activity. Riding a bike will not do much to improve your running skill. On the other hand, most of the endurance gained on a long, easy bike ride will be just as useful in the run as endurance gained by running. Does it matter? Yes, because long bike rides are much less likely to cause repetitive stress injuries.

I see myself first and foremost as a triathlete. Like many triathletes I also enjoy events in just one sport. I do not consider myself to be a good runner, yet for the last decade I have been just as determined to do run events as triathlons, and the only running event I really care about is the marathon. This year was my seventh. I missed 2013 due to a hernia, and I spent about two years preparing for my first in 2012.

For my early attempts I followed a traditional marathon training plan. Lots of running, little else. It was I think in 2017 that I first tried a blended approach after reading an article about it on TrainingPeaks. The idea was to move much of the long run work to the bike. My finishing times remained unspectacular, but I was in much better position to start training for triathlon after the race. The problem I had with this approach was a complete lack of detailed training advice, much less a plan. I made my own, as best I could, but never was satisfied.

After Honu this year I started thinking about how to train for this year's marathon when it hit me that athletes who do a full Ironman run a marathon. Instead of cooking up my own plan, why not start with a full Ironman plan? Besides, I was curious if I could survive training. I selected an introductory level plan by Matt Fitzgerald, one with a goal of just finishing. I used his 70.3 plan for Honu so I understood how they work. I followed the early base period as written, but after a bit the swims became longer than I could fit into my day, and since I did not need to swim I just did my own swim at the plan time.

Back when I was following traditional running plans I found myself out on the long run for hours and hours. So long that I was useless for most of the following week. It was from this experience I learned that coaches recommend a longest run time of around two and a half hours. They say, with studies to back them up, there is little benefit to going longer, and a much greater risk of injury.

Why did these training plans prescribe runs of four to six hours? They didn't. They are based on distance, not time, and assume the runner has some skills. Consider this: An 18 mile run at an 8:20 pace will take two and a half hours. That would be a 3:38 marathon. Those are the kind of numbers real runners can do. I run at around 18:00, so that 18 mile workout will take me about five and a half hours, and I'll be lucky to be ready to run again the following weekend.

The Fitzgerald Ironman plan I followed began with medium long runs on Saturday and long bikes on Sunday. During the build period both got too long to do back to back, so the long run moved to Thursday. Only that did not work for me because the night before was spin class and I did not want to run on tired legs, so I moved those to Tuesday morning. After the Saturday run reached two hours and moved to Tuesday morning the progression was 2:15, 2:30, rest, 2:40. At the same time the Sunday bike had reached 5:30 and progressed through 5:00, 5:30, 3:00, 6:00. You can see how endurance is being built on the bike, with as much running as possible and still be safe. I am happy to report I arrived at the start line without injury, strong and full of energy.

Throughout this same period the plan called for regular doses of muscular endurance workouts. As a rule this meant running cruise intervals or tempo runs on Tuesday morning and Dorian's spin class on Wednesday afternoon. When the long run moved to Tuesday the speed work was cut back, an example of how workouts become increasing race-like as the race day approaches.

Cycling and running require development of force, the aspect of muscular action that involves strength. To be efficient that strength must be combined with movement skills. These movement skills are best developed by practicing the specific activity. Cyclists need to ride a bike. Runners need to run. Even swimming requires some force development, particularly due to the weakness of the shoulder joint.

Carefully applied strength training in the gym offers a way to develop force specifically required by an activity while significantly reducing the likelihood of overuse injury. If strength sessions are monitored by a physical fitness expert they also provide an opportunity to correct movement flaws. Let me assure you, I have an abundance of flaws, starting with a left leg that wants to turn out like a duck and run without flexing, and a right shoulder that wants to cave in and do the work the back should do. Those are the top two in a long list. Fortunately I can work the the gym twice a week with Dorian Cuccia.

Every athlete will benefit from this type of strength training, but as we age it becomes increasingly important. Muscle development is supported by hormone levels, testosterone in particular. As we age our hormone levels decline. Doing the same workouts at fifty will not produce the same muscle response they did at twenty. Doing two strength sessions a week allows me to develop the strength I need to perform well and an opportunity to correct movement flaws, while avoiding the overuse injuries that are likely to result from struggling to develop strength through more running.

I used an 18 week training plan, which started the week of July 15. Here is my TrainingPeaks Performance Management Chart for that period plus a bit more. The sag in late September is when I had vertigo and had to cut back on my activity.


In a perfect world the conditions would not have been so brutal on race day and I would have a better assessment of how my approach worked. As it is, I cannot say how much of my inability to run was due to the heat and how much was a lack of preparation. At the time, passing outbound through Kahala, I genuinely feared there was something wrong with my heart, because I never felt that way in any of my training. My annual physical is coming up soon and I will discuss this with my doctor. I guess I should consider it a good thing that I made the adjustment, because if I had not, if my heart had not failed me I might have ended up with heat stroke. Nobody wants to end their race in the medical tent.

Tuesday, December 10, 2019

2019 Marathon race report, part 1



Honolulu Marathon 2019 was my chance to finally have a good outing. My spring "B" races, Hapalua and Honolulu Triathlon were OK, but I saw them as stepping stones to my big "A" race, Ironman 70.3 Hawaii, a.k.a. Honu. Honu was a big improvement from prior years, but there remains unfinished business. My Honolulu Century Ride was disrupted by a round of vertigo - it was all I could do to ride out to Hawaii Kai with Pattie's cruisers. That same setback set back my marathon training, but I was reasonably certain that there was enough time remaining to minimize the damage. That left last Sunday's marathon to make something of the year. It didn't happen.

In Part 2 of this series I will go into more detail about how I trained. For now I will focus on the race.

Peter Sagan has this to say about plans: "One of my mantras is that it’s good to have a plan, but plans don’t always work."  Sagan Peter. My World (p. 136). VeloPress. Kindle Edition. My preference for planning a race like this is two make two, one a stretch and one more reasonable. I do this because I tend to hold back. Call me the reluctant runner. Having an aggressive plan pushes me out of my comfort zone.

First, a bit of history. People keep asking me how many marathons I have run and I can't remember, so here it is, for the record. Including this year, 7. The data in the table below is a bit iffy as it comes from my Gamins and TrainingPeaks. Nothing official but plenty good enough to make comparisons.

I started out to examine the usual splits, 13.1 and full. This works well on a flat course, but the disruption in pace caused by Diamond Head - 18th - Kilauea distorts how I was running on flat ground. The 10K point is near the entrance to Kapiolani Park. I could have used 7.5 mi, the start of the climb up Diamond Head, but that seems like an arbitrary number. I'll did deeper into these numbers in a future post.


10KFull
YearTimeAvg PaceAvg HRMax HRTimeAvg PaceAvg HRMax HR
20121:4516:491401487:5117:40140155
2013**
20141:4116:111391457:2616:59137146
20151:4016:101391467:3716:53136148
20161:4717:121391458:2018:25128149
20171:4517:061411568:1018:29130157
20181:4717:221431568:0818:18137159
20191:5117:481371518:2818:01129158
* - DNS, hernia

Plan A. Aim for an average pace of 16:00 min/mi which should have me finish in a squeak under seven hours. If I could get even close to that I would beat my PR from 2014. That sounds like a crazy goal, but I have been training well all year with no running injuries, running well, and except for that bout with vertigo feeling great. No flu, no pulled hamstrings or wonky knees.

Plan B. Aim for an average pace of 18:00 min/mi which will get me in under eight hours. This felt totally doable because I have been running this pace regularly on my long runs.

Running with a power meter adds a whole new dimension that compliments the more traditional heart rate and pace. My first run with Stryd was October 3rd, 2017, so I do have some data to look back on. For now I'll just say that for Plan A my target power was 143 - 149, mid zone 2 to low zone 3. For Plan B, 133-135, the very bottom of zone 2, which is where I paced my long run workouts. I had done multiple runs in excess of two hours at that intensity and felt fine at the end and able to go on and have a normal, productive day.

I planned to do the first few miles as a gradual warm-up. Walk the first ten minutes, just like a workout. This is a brisk walk, not a stroll through the park. From there on I would use the same 10/1 run/walk method that I had used in my long runs. My pace would be Plan B until, maybe, we get back to Ala Moana Blvd. Or maybe sooner, along King Street. When I felt well warmed up and settled I would approach Plan A and see how it felt. At this point in a race I tend to go too hard, so I wanted to be careful to sneak up on it from below.

In the past year I read a couple of interesting books on the brain's role in regulating effort. Endure, by Alex Hutchinson, and Brain Training for Runners, by Matt Fitzgerald. My takeaway from these is that the brain has more to do with when an endurance athlete slows down or stops than the muscles or the fuel. Bonking is still a popular notion, and indeed getting your nutrition wrong will compromise your performance, but the body does not slow down and stop when it runs out of fuel, not like a car or a smartphone. Without fuel, your heart would stop beating. Since bonking does not result in death, there must be something else in play. Nobody knows for sure what that is, but so far most evidence points to the brain trying to keep you alive.

The Hutchinson book is a fascinating read (highly recommended!), whereas Fitzgerald goes more into application. He even includes training plans for 5K, 10K, half and full marathons built on his belief that carefully progressive workouts teach the brain that long, hard efforts are not going to kill you. The brain learns to stop complaining. He makes the point that you can't count on forcing yourself to overcome these survival instincts, but if you understand the mind's role you can push yourself to go harder than you would otherwise. I think this is something Ironman athletes figured out a long time ago. What is different now are studies that quantify this effect. As I trained for this marathon I worked both ends of these theories, doing the long runs and bike rides to teach my brain that long hard work is no big deal (!), and practicing how to push myself out of my comfort zone.

My Garmin 935 provides a wealth of useful data and TrainingPeaks displays it beautifully. (And let's not forget WKO, which does even more!) What these tools do not make obvious is how I was trying to run the first 10K. This is due to constant variation caused by dodging slow runners and walkers, not to mention so many people stopping to take pictures of every Christmas display and distance flag. I don't mind that. It is all a part of the crazy marathon party. I see me hitting 16:00 whenever I can after coming up Nuuanu and turning east onto King. That holds all the way to the park, which meant Plan A was a possibility even if hitting an overall average of 16:00 would require a crazy fast negative splits. Remember, 16:00 was not an absolute goal. It's not as if I was trying to hit a Boston qualifying time. It was intended to be a very high bar. My average from Nuuanu to the park was 17:30, well under my Plan B and I was seriously holding back. I felt good, and when I saw my time I felt even better.

I always struggle with the Diamond Head - 18th Ave - Kilauea section. I learned the hard way not to run the steeper sections, and to hold off a little longer before starting to run again. I did this section exactly as planned, at an average pace of 18:34, only a little slower than Plan B. Not too shabby! I was a bit concerned that coming down 18th I had sweat running down my face. It was then that I noticed how clear the sky was. I stopped to take some pictures to show why I felt so hot.

No clouds, no wind, lots of sun.

It was while coming up the long false-flat climb on Kilauea to the Aloha gas station when I began to feel in trouble. This was supposed to be a recovery section after the recent ups and downs, but when I tried to run I soon felt exhausted. My nice 10/1 run/walk deteriorated into a 1/1.

I was pacing myself primarily by power, with an occasional check on pace, leaving heart rate to do its thing. I set my Garmin to display the new Stryd Zones Connect IQ app on page one, time, pace and average pace on page two, and heart rate and zone on page three. As I came up Kilauea I was telling myself that things will get back to normal when I out onto the highway, but I also started looking more often at page three. Sure enough, my heart rate was high and topping zone 4 whenever I felt like I had to stop running.

When getting past the gas station failed to bring any improvement I tried a new plan. (Remember what Sagan said.) I would do my run/walk based on heart rate. I would run until my heart rate just reached zone 4, then walk until it just fell into zone 1. I kept this up until the halfway point, where I finally realized that this was not sustainable. In three miles I had done a dozen LTHR intervals, with insufficient recoveries. I was slowly dying.

Not literally, perhaps, but I actually was concerned. I get a physical every year, and although my doctor says I am as fit as anyone could be I do have a heart murmur and my heart is more likely than average to miss a beat. It seemed to me that my heart was misbehaving. Nothing like this happened in those eighteen weeks of training. Why now? What was different? I had no idea. What I did know was that to continue running in this condition could result in me finishing in the ER.

It was at this point I switched to a new plan. Just walk, like everyone around me had been doing since Diamond Head. The deal I made with myself was that I would walk as fast as I could. I was concerned that because I did not practice this way my muscles would give out. Nothing could have been further from the truth. With my heart now under control I found that I had a lot of strength. I was passing a lot of people and nobody passed me. Hydration and nutrition were fine. I felt good.

When I sat down to  review the data for this post it wasn't long before I spotted something. Temperature at the start was around 80 and remained there until we turned onto 18th. Remember it was there that I suddenly felt sweat coming down my face? Temperature shot up to 88. When I was doing my ultra-short LTHR intervals it was hitting 90. Later, on the way back over Diamond Head, it reached 100! And all this time, no wind. No wonder!

I had some hot days on my long bike rides, but we must not forget that the bike creates its own cooling breeze. My long runs were all early morning. During Base and Build-1 on Saturday morning starting a 6:00. In Base-2 the Saturday runs and Sunday bikes got too long to do back to back without an intervening recovery day, so the long run moved to Tuesday mornings, starting around 5:00AM. In eighteen weeks I never ran for long in this kind of heat.

That about does it for this race report. In Part 2 I will go into more detail about how I planned my training, and if I ever get to it, Part 3 will look to the future.

One small thing to be thankful for. Along with no cramping or sore shins, I did not lose a toenail. Yet. But I see no sign of trauma there. I have Danny Abshire's new shoes to thank for that.