Sunday, December 21, 2014

Race Post-Mortem: Rehoboth Beach Seashore Half-Marathon

Post race with my age group third-place trophy.  Photo courtesy of Craig.

Saturday, December 6, 2014
Rehoboth Beach, DE
Difficulty score: 2/10 (0 for weather, 2 for course profile, 0 for altitude)

Initially, I had planned to run the Jingle All the Way 8K (which was temporarily transformed into a 5K this year due to construction near Freedom Plaza) this weekend, but instead decided to register for the Rehoboth Beach Seashore Half-Marathon after learning that three other members of DC Front Runners were running the marathon.  I had several reasons for wanting to do this race.  I knew a weekend in Rehoboth Beach would be fun, even in December; actually, I prefer Rehoboth on "off" weekends when it is not inundated by beach-bound people from Washington, DC.  But also, I wanted to do a half-marathon for some points toward my race circuit total score.  DC Front Runners has a race circuit in which your score for a particular race equals the age-graded score according to USA Track and Field.  However, by the rules of the race circuit, those that complete a half-marathon receive an additional 5 percent bonus on top of their age-grade score (i.e. their circuit score for that race equals the age-grade score times 1.05); as a result, half-marathons are one of the best race distances for maximizing your race circuit total score.  

I was not expecting to run a PR this time.  I would not consider this half-marathon course a PR course; I knew from my first time running this course in 2012 that the half-marathon course is deceptively tricky, primarily because miles 7 through 11 take place entirely on trails of packed dirt and gravel.  However, I did know I was probably capable of a 1:26:00 to 1:27:00 on this course, and that would have gotten me a score of 71 to 72 points, a high score for me.  Plus, with a time like that, I would have a relatively good chance of placing in my age group; I finished in 1:28:12 in 2012 and had won third place in the Male 30-34 age group.

Thus, I set finishing in 1:26:59 or faster as my primary goal, hoping that was enough for me to place in my age group.  Running a PR and finishing in the top 10 overall would have been bonuses.  My plan for this race was to firmly stick to a 6:35 to 6:40/mile pace for the first six miles, before we reached the lengthy trail segment.  I would allow about a five second per mile slowdown for the trail segment, and after the trails were behind me for the last mile and a half or so, I would pick up the pace to make up some time.  Given perfect execution, I was expecting to just dip below 1:27:00.  I was also hoping that the trails would help me overtake some runners by draining their energy, and I aimed to pass some people during my surge during the last mile.

I ended up finishing in 1:26:30 (6:37/mile), which translates into 71.89 points toward my race circuit total score.  That time was also good enough for third place in the Male 30-34 age group.  It was not a PR (my half-marathon PR was 1:25:12 at the Rock and Roll Philadelphia Half-Marathon earlier this year), nor did I finish in the top ten overall.  But I was happy with my 15th place finish; with 1400 finishers in this half-marathon, this was probably my highest overall placement in any race.

Training and the Days Leading Up to the Race

My preparation for this half-marathon was not particularly thorough.  When I had registered, I had just finished recovering from the Chicago Marathon and had less than five weeks to get myself back into half-marathon racing shape.  I probably would not have been able to get my weekly mileage much above 40 miles, but that would have to do.

This time, I made sure that I was a little more serious about my tempo runs and speed workouts.  During my training for Chicago, I had turned my focus away from these toward increased mileage.  But when I ran the Veteran's Day 10K four weeks after Chicago, I realized that this decision probably was not a particularly good one.  Whereas I was able to run a 10K PR in the 2013 Veteran's Day 10K in 38:19 following the Wineglass Marathon and another 10K PR in the 2014 Pike's Peek 10K this past April in 38:10 following the Shamrock Marathon, I finished the 2014 Veteran's Day 10K in 38:55.  Given that I had been able to PR in shorter distances following previous marathon training cycles, I concluded that I had indeed lost speed; my body simply could not go faster than the 6:16/mile pace I ran that day.  Looking back at my workouts at garminconnect.com, I noticed that many of my tempo runs may have been too slow this summer; I knew I would have to slow down my tempo runs due to the heat and humidity here in Washington, DC, but I think I slowed them down a little too much.  Also, I had done no track workouts, hill sprints, or hill repeats during my training for Chicago.

During the weeks leading up to Rehoboth, I ran five to six days per week, with a tempo run on Tuesdays, hill repeats on Thursdays, long runs of up to 13 miles on Sundays, and easy runs of four to six miles elsewhere.  I made sure that I hit a 6:20 to 6:25/mile pace during my Tuesday tempo runs, until the two weeks before the half-marathon, during which I ran my Tuesday tempo runs at my target race pace.  I was able to run one 35-mile week and one 41-mile week.  I would have liked a string of weeks of mileage in the forties, but what I had was still better than nothing.

I drove with Brian to Rehoboth Beach the day before the race, arriving at around four in the afternoon.  Our first stop was the expo, where we picked up our race packets and I picked up a visor in case it rained on race day morning; I had stupidly forgotten my visor back in DC.  We then went to check into our hotel, after which we met Eddie, Thorne, and Jacques for dinner.  Given the 7:00 am start of the race, that was pretty much the extent of our activities that day.

The Race

Race morning temperatures were great; when I arrived at the start line, it was 48 degrees.  The weather forecast predicted that the temperatures would not exceed 55 degrees that day.  However, the humidity was extremely high.  I felt it when I was running; I could feel sweat just dripping down my body even as early as mile 3.  Many of the runners agreed that the humidity was high enough to affect most people's race performances that day.

As I mentioned before, the Rehoboth Beach Half-Marathon is a deceptively tricky course.  That would most likely not be evident to first-timers during the early miles; the first six miles are fast, being flat and on asphalt.  Marathoners and half-marathoners start together in downtown Rehoboth Beach, on Rehoboth Avenue in front of the bandstand near the boardwalk and go through subdivisions of Rehoboth Beach before running along the shore down Ocean Drive.  Near the terminus of Ocean Drive, half-marathoners go back down Ocean Drive toward the start while marathoners continue north along a trail.  The remainder of the half-marathon is the last ten miles of the marathon; half-marathoners travel through another subdivision before crossing Route 271 and entering the Junction and Breakwater Trail.  The next four to five miles are an out and back segment on this trail.  The surface of this trail portion can be problematic, particularly when it is wet; often, you will slip backwards a little for every step you take.  Also, I knew from my run on this course in 2012 that a seemingly never-ending trail segment could be very mentally draining, particularly for first-timers who did not know they would be running five miles on this packed dirt and gravel; I certainly was blindsided by this when I ran this course for the first time in 2012, and it took enough out of me that I slowed down during the last few miles.  We then retrace our steps back toward downtown Rehoboth Beach, finishing right next to the building where Rehoboth Beach Running Company is located.

Map of the half-marathon, from the race website.

The start through 6 (splits: 6:37, 6:33, 6:37, 6:37, 6:36, 6:35): I used the first mile to ease into my target pace, being careful not to waste any energy weaving around people and trying my hardest to hit all of the tangents; after all, beating my competitors would be much easier if I covered 13.17 miles while they ended up covering 13.27 miles, a difference that could translate into more than 40 seconds at the pace I intended to run.  From that point up until I arrived at the trail segment, I focused on staying within the 6:35 to 6:40/mile range.  Since 6:36/mile felt relatively comfortable, I decided to run on the faster end of that target range for this portion of the race.

I was not really focused on passing people, although I found I was able to easily pass several half-marathoners and marathoners while running at my target pace.  On Ocean Drive, a few other half-marathoners passed me, including one named Alex, who I formally met after the race, and another guy in green who looked to be about my age that I didn't really see again after we got off Ocean Drive.  I spent most of the Ocean Drive segment trying to catch up to Alex and this other runner, only to have them surge right back ahead of me.  I could not drop Alex; for the remainder of the race, we would be locked into a battle to beat one another.  The other guy, on the other hand, I knew would not be a problem; his breathing was a little too heavy at that point in the race, and both Alex and I quickly dropped him.

Miles 7 through 11 (splits: 6:37, 6:50, 6:39, 6:38): The trail portion did not slow me down nearly as much as I thought it would.  Other than my split for mile 8, I was still able to more or less maintain a 6:35 to 6:40/mile pace for this segment of the race as well.  I still cannot figure out why my pace for mile 8 was that much slower.

Here, I focused on staying away from the patches of loose gravel and dirt and on running on the more packed-down parts of the trail, as well as hitting the tangents.  I ran by myself for most of these miles.  I was able to see a pack of three or four people several hundred feet in front of me.  I was able to put a little distance between Alex and everyone else behind me.  On the way out, I tried to maintain a steady effort; I did not focus too much on trying to close the gap between me and the runners in front of me.  I felt this point in the race was too soon to begin making any moves.  Besides, like I said before, I was trying to let the trails do some of the work for me in draining the energy of some of the more reckless runners in front.

As I approached the turnaround near the mile 9 mark, I counted 20 people in front of me.  I figured that if I finished in 21st place overall, I would probably have a pretty good chance of placing in my age group in this race.  Besides, at least five of the people in front of me were not in competition with me for an age group award.  Among the 20 people in front of me, I counted two women, including the eventual female winner and the Women's Masters winner, and two guys that were clearly younger than 30 years old.  Remembering the awards structure from 2012, the male winner was not eligible for an age group award either.

I was actually closer to the pack ahead of me than I had thought.  I changed my plan to speed up and start trying to overtake runners at the Mile 11 mark.  However, I would not have cleared the trail portion yet at that point.  But I figured I could probably classify this move as a little risky and not totally stupid; this new plan would have me running 0.7 miles of my end surge on trails, which was doable but possibly difficult.  I did inadvertently speed up a little before I hit the Mile 10 mark anyway; that was probably a result of me getting excited as I got to see some other friends from DC also doing the half-marathon as I ran back toward downtown Rehoboth.

I ended up passing three people between the Mile 11 and Mile 12 mark, two of which I overtook on the trail portion.  One of these people was the eventual Women's Masters winner.  However, I did discover that Alex was not far behind me; I could hear his friends cheer his name as they ran past me in the opposite direction.

Mile 12 through the end (splits: 6:25, 6:18, 0:58 for the last 0.17 miles): At this point in the race, I just stopped looking at my watch and focused on passing as many runners as I could.  I passed a few more people, and was now in 16th place.

With about half a mile left to go, Alex surged past me.  He put in a hard enough move that I could not respond to it.  Initially, I resigned myself to the possibility that he would beat me after all, but soon, I noticed I was catching back up to him.  As I chased him toward the finish line, I passed another runner, positioning myself back in 16th place.

After running across the bridge over the canal and around the roundabout on Rehoboth Avenue, I then gave it all I had left.  I passed Alex right back and started chasing the next runner in front of us.  I could not catch him, though, but Alex was unable to catch me.  I rounded that last turn and crossed the finish line, finishing four seconds in front of Alex.

Alex and I then talked a little after we received our medals and heat sheets.  We both were very happy to learn that we were in different age groups.  Even though I crossed the finish line before he did, he may have started far back enough that his net time, which would be the basis of age group awards, was faster than mine (his net time actually turned out to be a few seconds slower than mine).  After seeing Joey, Chris, and Jason finish their races, I returned to the hotel to get my wristband, which I forgot that morning but needed to get into the finisher's tent.  In my hotel room, I checked my phone; I selected the option of having my results texted to me after I finished, and there, I learned that I finished in 1:26:30, 15th overall, and third in my age group.

I returned to the finish line to watch some of the marathoners finish.  Eddie won the marathon, and I was very happy to have witnessed that.  Unfortunately, since the half-marathon awards ceremony would take place between about 10:00 and 10:30 am, about three to three and a half hours after the start of the marathon, I was unable to see Brian or Thorne finish.  But I was able to catch them afterwards, and we did all get to attend the marathon awards ceremony and see Eddie receive his life preserver and box of wine.

Next Steps

I plan to start training for the Rock and Roll DC Half-Marathon (March 14) soon.  I have begun sketching out a twelve-week training plan, in which I have been sure to also incorporate some intervals, hill sprints, and hill repeats.  But my training for that does not begin until December 22.  For the next two weeks or so, I do not really plan to do much running.

Finally, congratulations to Brian and Thorne for running marathon PRs in Rehoboth, and also congratulations to Eddie for winning the marathon.  

Thursday, October 23, 2014

Race Post-Mortem: Chicago Marathon

Brian, me, and Jeremy at Grant Park post-marathon, enjoying the gorgeous weather and basking in the glory of great performances.  Photo courtesy of Brian.

Sunday, October 12, 2014
Chicago, IL
Difficulty score: 1/10 (0 for weather, 1 for course profile, 0 for altitude)

I finished the Chicago Marathon in 3:03:48 (7:01/mile), a 59-second PR for me and 72 seconds below my 3:05:00 Boston qualifying standard.  This was a race where the start was a little rough but I pulled it together during the second half, and for that reason, I was pleased with my performance.  The early miles were noticeably slower, due to both feeling a little sluggish at the beginning for reasons I still do not know and lacking the experience in handling the large crowds of runners at the beginning; this race had more than twice as many participants as any other race I have run so far.  But around the half-marathon point, I was able to settle into a rhythm and maintain a steady 7:00/mile pace until the 30K mark.  After I reached the 30K mark, I accelerated, aiming for a more uncomfortable pace.  I managed a 6:40 to 6:50/mile pace for the remainder of the marathon, finishing with a four-minute negative split; whereas I ran the first half in 1:33:50, I finished the second half in 1:29:58.

I started this marathon without a specific time goal.  I would have been extremely happy if I broke three hours; under perfect conditions and with perfect race execution, I may have been able to accomplish this or get really close to doing so.  But my primary goal really was to run a PR and improve my chances of being able to actually run the Boston Marathon in 2016.  I had applied to Boston for 2015 after beating my qualifying standard by 13 seconds in the Shamrock Marathon; however, because the number of applicants to Boston exceeded the number of spaces available, no one who ran less than 62 seconds under their qualifying standard would be able to run in 2015.  Now that I have run 72 seconds under my qualifying standard, I believe my chances of being able to run Boston are indeed much better.  It might be close, but hopefully my time this past weekend would be enough to get me into Boston for 2016.

Training

I have given detailed descriptions of my training plan for this marathon here and here.  I wanted to increase my mileage this time around, hoping that would improve my endurance and my marathon time.  Whereas my weekly mileage was mostly in the high forties and low to mid-fifties during my training for Shamrock, this time, it was mostly in the high fifties and low to mid-sixties.

In order to be able to increase my mileage, I needed to sacrifice much of my more intense mileage during the week.  Every week during this training cycle, about 90 percent of my mileage was run at 7:40/mile pace or slower, a substantially slower pace than I knew I was capable of running the marathon.  The remaining ten percent was at tempo pace, where I targeted about 6:25 to 6:30/mile.  The structure of my training plan was simple:
  • Monday: five to six miles at 8:30/mile pace or slower to recover from my Sunday long run.
  • Tuesday: seven to ten miles with the inner four to seven miles at tempo pace.
  • Wednesday: rest.
  • Thursday: eight to fourteen miles with target pace of 7:40 to 8:20/mile.
  • Friday: five to six miles at 8:30/mile pace or slower to recover from my Thursday mini-long run.
  • Saturday: seven to ten miles with a target pace 7:40 to 8:20/mile.
  • Sunday: long run with target pace of 7:40 to 8:20/mile.
In previous training cycles, Thursdays were another higher-intensity day in the form of a hill workout, track workout, or a second tempo run.  I decided to eliminate that in favor of my Thursday mini-long run.  I could not imagine doing a second higher-intensity workout each week during this training cycle; the mileage was strenuous as it was.

I had little problem executing this training plan and adjusting to the high mileage.  Aside from an Achilles' tendon injury early in the cycle and a cold later on, both of which sidelined me for several days, I was able to complete the training plan pretty much as written.  Summer 2014 was relatively mild, which allowed me to actually hit my target tempo pace of 6:25 to 6:30/mile during some weeks.

The Days Leading Up to the Event

Three weeks before Chicago, I ran the Rock and Roll Philadelphia Half-Marathon as a tune-up race to get back into the racing mindset and to get a basis for a reasonable pace for the marathon.  The weather on the day of the half-marathon was certainly not ideal: 68 degrees and 88 percent humidity at the start, with the temperatures just getting warmer as the race progressed.  But even after a relatively slow first mile, I still managed to run 1:25:12, a thirteen-second half-marathon PR for me.

I probably would have been able to run a significantly better time under less unpleasant conditions.  But for the purposes of estimating a reasonable target pace for Chicago, I decided to use 1:25:12 as my basis.  In terms of planning a pacing strategy for the marathon, I believed it was better to err on the conservative side.  Besides, I had no idea exactly how much better my time would have been under better racing conditions; all I could reasonably conclude was that I was in 1:25:12 half-marathon shape or better.  I am aware that some online calculators can provide an adjusted race time for temperature, but frankly, I was a little hesitant to listen to them; I cannot imagine that any such temperature-adjusting race time calculators have actually been validated with real race results, and I have trouble figuring out a design of this type of study.  Thus, plugging my 1:25:12 half-marathon time into the Maclin calculator on the Moderate aggressiveness setting gave me a 3:02:04, or 6:57/mile pace.  I settled on the plan to target 6:55 to 7:00/mile during the first 30K, and then accelerate or try to hold that pace from that point forward depending on how I felt.

After the half-marathon, I started my taper.  I basically tried to replicate what I did during the three-week taper period preceding Shamrock.  The week following the half-marathon was mostly done at recovery pace.  That Sunday and the following Tuesday would be the last truly difficult workouts I would do before the marathon.  Sunday's long run was a 16-mile long run with six miles at target marathon pace.  The warm temperatures that day prohibited me from hitting my target pace, so I after three miles of trying to hold a 6:55 to 7:00/mile pace, I gave up and just ran the remainder of the run at my normal long run pace.  The following Tuesday's run was a six-mile run with the inner four miles at tempo pace.  I was able to successfully hit tempo pace, even in spite of the warmer temperatures.  After that, my workouts only consisted of easy runs and marathon-pace runs.  The week preceding the marathon, I focused on consuming carbs whenever I could and staying hydrated.

I arrived in Chicago on the Friday before the race.  After meeting Jeremy, with whom I trained for much of this cycle, at the airport, we took the train to our hotel, located only about four blocks from the start line.  We intentionally did not do much on Friday; aside from a trip to the Expo at McCormick Place, which took longer than anticipated because of the relative scarcity of shuttle buses going to and from the Roosevelt station, I did a four-mile shakeout run, and dinner.

The next day Jeremy and I did a bit of sightseeing, which we kept limited in order to stay off our feet and to save our energy for the race.  We did visit Willis Tower and the ledge on the 103rd floor.  We had intended to do an architectural boat tour this afternoon also, but they were booked completely.  I would have loved to get pictures of Willis Tower and the city of Chicago, but the camera on my phone inexplicably froze after I tried to take a picture and I could not get it to unfreeze.  But otherwise, a good portion of this day was spent at the hotel.

The Race

Conditions were nearly perfect on race day: moderate humidity with temperatures starting in the low fifties and never really increasing much more than that.  After waking up at four in the morning and being unable to fall asleep, I passed the time in my hotel room before going downstairs to meet Jeremy at around seven.  Even though our hotel was a relatively brief walk to the start line in Grant Park, we barely made it into our corral before the Wave 1 corrals closed.  According to event rules, Wave 1 corrals closed at 7:20 am, ten minutes before the official start of the race, and all runners in Corrals A through E needed to be in their corrals before then.  Those that were late were required to start at the back of Corral E.  The course officials were actually quite strict about this rule; the gates to the Wave 1 corrals closed promptly at 7:20 with an announcement to all of those not yet in the corrals to report to the back of Corral E.

The Chicago Marathon course is fast and very flat, aside from a relatively small hill on Roosevelt Avenue near the Mile 26 mark.  This course is great for a PR, provided that the weather cooperates, which, based on historical data, seems to be most of the time, despite many marathoners' warnings about the high variability of Chicago Marathon race day conditions.  The course is shaped like a cross with its right prong missing, or a four-leaf clover with a missing leaf.  For the first seven miles or so, runners head north toward Lincoln Park and Wrigleyville before coming back toward the Central Loop.  Near the half-marathon mark, runners then head west on Adams Street for about two miles toward Greektown before again coming back toward the Central Loop.  For Mile 17 through Mile 23, runners head south through Little Italy, University Village, and Chinatown toward Bridgeport, at which point, they return north toward Grant Park by way of Michigan Avenue for the finish.  The Chicago Marathon course has been advertised as one going through 29 neighborhoods of Chicago, and it was certainly a good running tour of the city.

One thing about this course is that GPS watches fail to work during the first 5K and near the half-marathon mark due to the surrounding buildings and the Columbus Drive tunnel near the start.  I have heard widely varying reports on exactly how the GPS screwed up during these segments; some people reported that their watches indicated the end of the first mile when they had in fact already covered two or even three, while others reported that their watches showed them going at unrealistically fast paces.  For the first 5K, I fell more in the former category; according to my Garmin, the distance between the start and the Mile 3 mark was 2.88 miles.  But near the half-marathon mark, I fell in the latter category; my split for Mile 13 was 6:35, which definitely was not correct.

Having known that GPS was unreliable during the first 5K, my plan was to line up about twenty feet behind the 3:05:00 pace group and spend the first three miles or so gradually catching up to them.  I knew I had to run this segment of the race largely by feel, and I felt having a pace group as a point of reference would be helpful in preventing me from accidentally going too fast in these early miles.  Jeremy and I lined up behind what we thought was the 3:05:00 pace group, on the left side of the corral, about halfway between the leftmost fence and the median, knowing that the first two turns would be left turns.  We did not want to line up all the way on the left since after these first two turns, the next three turns would be right turns; we wanted to be able to get toward the right side of the course after the second left turn.

It turns out that what we thought was the 3:05:00 pace group simply turned out to be a bunch of people wearing the 3:05:00 pace group signs on their backs doing their own thing.  Actually, during the race, I could not find any of the official pace groups.  Thus, I had to run the first 5K by feel.  As I entered the Columbus Drive tunnel, I just went with the flow, running a similar pace as the people around me.  I was a little unprepared for the crowd of runners around me at the beginning; this was my largest marathon by far, and I had never experienced having to deal with this many other runners at the start.  Nevertheless, I tried not to waste any energy weaving through people, although a few times, I did go around some people that I felt were running a little too slow.  The runners did begin to thin out a little by the time we headed north on LaSalle, but due to the congestion, those first few miles were considerably slower; I completed the first mile in 7:19 and I averaged 7:14/mile pace for the first 5K.

During this race, I diligently stuck to the fueling plan that I had also used for my previous marathons: water or Gatorade at every station before the 30K mark, and three Shot Blocks every three or four miles.  Again, I typically would not consume any fluids or Shot Blocks after the 30K mark; at that point in any marathon, a runner's body is so stressed that it would no longer be able to take in any additional nutrients as non-essential functions such as digestion would have been shut down.  I believe that it is the fluids and the Shot Blocks or gels taken in the earlier miles that will make the difference; since the body has not been stressed to the point of shutting down digestion at this point, it still will take in nutrients.

The next 5K was also quite a bit slower at 7:12/mile pace.  I simply felt sluggish during these miles for some reason.  As I noted my pace, I realized that my original target pace of 6:55 to 7:00/mile was not going to happen today; my body simply did not want to go that fast.  But after the 10K mark, I started to settle into a 7:00 to 7:05/mile pace; it still not my original target pace, but it would have brought me a Boston qualifying time if I held it.  I felt that if I had gone faster, it would have come back to haunt me later in the race.  Thus, I listened to my body and stayed at this pace until the 30K mark.

I have trouble remembering much of the race between the 10K mark and the halfway point.  Jeremy and I continued to run together through the halfway point; I focused on fueling, running the tangents, and maintaining my pace, which, for reasons unknown, started to drift back closer to 7:15/mile between the 15K and 20K mark.  I had been so focused on my race during this segment that I failed to notice when I entered Boystown at around Mile 8 or when another member of DC Front Runners also running Chicago flew past me and Jeremy at around the same point; I only knew after Jeremy pointed him out.  I also did not really pay much attention to the very loud throngs of spectators throughout the course.  The noise that they made was unlike anything I had heard in my other marathons; I had mentioned before that Chicago as a city was extremely enthusiastic about the marathon, and this enthusiasm certainly showed on race day.

After the halfway point, I did not feel exactly fresh, but I felt like I still had some more in me.  I did panic a little when I finished the first half in 1:33:50; even though this was the fastest I had ever completed the first half of a marathon, I still would have liked to have come through the halfway mark in faster than 1:33:00.  I continued onward, and my pace accelerated to my initial target of 6:55 to 7:00/mile.  I held this pace for the next several miles.

Jeremy and I continued running together until about the 30K mark.  When I saw that I finished the first 30K in around 2:12:30, I did some quick math and realized that if I ran the last 12K in 51 minutes, I would finish in 3:03:30 or faster, which should have given me a fighting chance of being able to actually run Boston in 2016.  That meant I had to average around a 6:50/mile pace for the rest of the race.  Realizing that I had enough energy left in me for a late-race surge, I decided to go for it.

Right after passing the 30K mark, I pushed the pace to about a 6:45/mile.  I actually could not remember much of the next few miles.  I did remember passing hordes of other runners, including one man running in a Minnie Mouse costume.  I did remember entering and leaving Chinatown near the Mile 21 mark, but other than that, Chinatown was a blur.  And I certainly remember people screaming what could very well be the most idiotic thing anyone can say at the Mile 22 mark of a marathon: "You're almost there!"  Four miles, although a relatively small proportion of the overall marathon distance, hardly qualifies as "almost there"; anyone who has run a marathon knows that those last four miles are often the most difficult.

I kept my 6:45 to 6:50/mile pace for next several miles, even though cramping in my legs that started shortly after the Mile 24 mark.  When I passed the Mile 25 mark and noticed that I was around 2:55:00 into the race, I pushed the pace a little.  As expected, Mt. Roosevelt, namely that last "little" hill right before the turn onto Columbus Drive to the finish, hurt.  That hill was not particularly long or steep, but at Mile 26 of the marathon, it most definitely was not trivial.  After I crested Mt. Roosevelt, I gave it everything I had, sprinting down Columbus Drive to the finish, overshooting the timing mats that would record my finish time; they were positioned right in front of the arches marking the finish, and I thought runners were done once they ran through those arches.

Splits at each 5K and halfway point, according to results.
I made my way to the reunion area and found Brian and his family.  Jeremy was also there, having slipped past me somewhere in the finisher's area.  After basking in the sun and the glory of our accomplishments that day (Jeremy and I had both run a PR and Brian had run a very strong 3:01:11), we returned to the hotel to freshen up and relax a little before exploring Chicago.

I was very glad that I got to stay those two extra days after the marathon.  After the marathon, I was able to do all the sightseeing that I wanted without having to worry about how being on my feet for so long would adversely affect my race.  Chicago has quite a bit to offer in terms of sights and experiences, and on marathon weekend, my marathon medal was able to get me into a number of places at a discounted price.  Notable highlights from the remainder of my trip included an architectural boat tour on the Chicago River, Sidetrack in Boystown, and the Art Institute, which had art from a wide range of time periods, much of which I was, unfortunately, unable to see due to time constraints.

And, of course, I visited the Cloud Gate.  Much to my annoyance, the camera on my phone was still having problems.  It was not until I returned to DC on Tuesday that my camera started inexplicably functioning again.

At the Cloud Gate the day after the marathon.  What trip to Chicago would be complete without a picture in front of the Cloud Gate?  Picture courtesy of Jeremy.

Thoughts About the Race


One thing I wish I did during this race was to soak up the atmosphere a little more.  As can be seen with my lack of florid descriptions of the race itself, I simply did not notice much of what was going on around me; I was so focused on getting a PR and qualifying for Boston again.  Personal bests and Boston qualifiers were important, but so was creating favorable memories; after all, my most fond racing memories were not necessarily races where I ran a PR, but ones where I made that additional effort to enjoy my surroundings, such as Baltimore in 2012 or Shamrock earlier this year.  Plus, this was my first World Major.

But also, this race emphasized the importance of paying attention to how I felt more than the pace on my Garmin.  Of course, the erratic behavior during the first 5K prevented me from relying on my Garmin for pace information.  But also, sometimes, your body just will not cooperate, and you will simply have no choice but to listen to it and adjust accordingly.  My body did not seem to want to run what I had initially planned during the early miles; like I had said before, I simply could not muster faster than a 7:05/mile pace for the first half of the race, and for much of the early miles, even 7:10 to 7:15/mile pace felt like an honest effort.  Sometimes, these stretches where you do not feel as fast and as strong as you would like just inexplicably go away; after the halfway mark, I began to speed up and was able to hit my initial target pace.  But if I had tried to force a pace during the first half of this race, I would have just kept digging myself deeper into a hole; had I pushed the pace in the early miles and actually tried to stay within my original targeted 6:55 to 7:00/mile range, I probably would have expended too much energy in the beginning and I would have suffered for it during the second half.

Finally, as I mentioned before, this was my first race of this size.  Such a large race comes with logistic issues not found in smaller marathons, and reading the rules and procedures carefully is very important.  For example, the Chicago Marathon has very strict rules about starting, such as needing to be in your corral at least ten minutes prior to the start of your wave; in order to accommodate over 40 thousand people starting a race within the space of 45 minutes, the rules do need to be strict.  Starting behind Corral E when I was originally assigned to Corral A just because I arrived at the gates of the corrals a minute late would have forced me to weave through huge crowds of people going almost two minutes per mile slower than I wanted to run; not an ideal start to a marathon.

Also, due to the congestion at the start, lining up in the correct location is very important.  The thick crowds in the early miles prevents you from running much faster than the pace of everyone else around you, unless you waste energy weaving in and out of other runners.  Thus, lining up too far at the front may force you to go at a much faster pace than you should, whereas lining up at too far toward the back may force you to run at too slow of a pace.  Also, lining up in the correct location will allow you to hug the turns a little more.  For Chicago, I feel the ideal location to line up is on the left side, about halfway between the far left fence and the median; the first two turns are left turns, and lining up on the left side would put you closer to those tangents.  But the following three turns are right turns; not lining up all the way on the left allows you to veer to the right much more easily to be able to get closer to the tangents for these turns.  As I have mentioned numerous times before, I am a strong advocate of running tangents; that can mean the difference between running just a little over 26.2 miles and running over 26.6 miles, which can translate to three minutes or more saved.

Next Steps

After recovering from this marathon, I will do several shorter races, including the Veteran's Day 10K in November and the Jingle All the Way 8K in December.  I may also even run my first 12K race, the .US National 12K in Arlington in the middle of November.  I cannot predict how I would do in these shorter distances after my last cycle of marathon training, but perhaps a small PR in the 10K or 8K may not be completely out of the question.

So then comes the question: when and what will my next marathon be?  Currently, I am thinking that my next marathon will be in Fall 2015, and I will focus on improving my times at the shorter distances in the spring.  I would do at least one half-marathon though, and most likely my first 10-Miler.  I think breaking the cycle of spring and fall marathons and focusing on speed for a bit may be good for my long-term development as a runner.

But then again, if I do run a spring marathon, I have a chance to improve my time even more and get an even better chance of being able to run Boston in 2016.  If I choose to run a spring marathon, then I would use Fall 2015 to focus on the shorter distances.  I may do the Spring 2015 marathon if I see any indication that the Boston cutoff time for 2016 will be more than 72 seconds. 

Wednesday, September 24, 2014

Race Post-Mortem: Rock and Roll Philadelphia Half-Marathon

Some of the DC Front Runners who ran the Philadelphia Half-Marathon.  Can you see the humidity in the air?  Photo courtesy of Marcel.

Sunday, September 21, 2014
Philadelphia, PA
Difficulty score: 1/10 (0 for weather, 1 for course profile, 0 for altitude)

This past Sunday, I ran the Rock and Roll Philadelphia Half-Marathon as a tune-up for the upcoming Chicago Marathon.  My intentions in running this race was not only to get back into the racing mindset as my last race was the Pike's Peek 10K this past April, but also to get a half-marathon time to serve as a basis for determining a realistic goal for Chicago.

I finished the half-marathon in 1:25:12 (6:29/mile), an improvement over my PR on the same course last year by 13 seconds.  This came as a pleasant surprise for me as race morning weather, 68 degrees and 88 percent humidity, was far from ideal for a PR.  I was prepared to finish this half-marathon one minute or two slower than my half-marathon PR.  Initially, I thought that was going to happen when I finished the first mile in 6:41.  But during the next few miles, I settled into a 6:30/mile pace and was able to maintain that pace until mile 10, at which point I accelerated to a 6:25/mile pace.  I cannot say exactly how well I would have done had race day weather been the ideal racing conditions of this race last year.  But my ability to run a half-marathon in this warmth and humidity faster than I did last year in temperatures in the low fifties gives me hope that I will be able to run a marathon PR in Chicago.

Training and the Days Leading Up to the Race

In preparation for Chicago, I had increased my mileage quite a bit.  During my training for Shamrock, my weekly mileage was in the high forties and low to mid fifties for most weeks.  But during this cycle, my weekly mileage was in the high to mid fifties and low to mid sixties for most weeks.  I had hoped the increase in mileage would help me improve my marathon time even more.  My weeks consisted of one tempo run on Tuesdays, a mini-long run of eight to fourteen miles on Thursdays, an easy run of six to ten miles on Saturday, a long run on Sunday, and recovery runs of five to six miles on Monday and Friday.  I had to sacrifice one tempo run each week in order to be able to achieve this kind of mileage; whereas during my training for Shamrock, I did two tempo runs per week, during this cycle, I only did one tempo run on Tuesdays.  The remainder of my miles for the week were easy or recovery runs, which meant that most of the time, more than 90 percent of my weekly mileage was run at 7:40/mile pace or slower.  The mileage itself was strenuous; I could not imagine running a second tempo run each week.

The Philadelphia Half-Marathon took place the week after a 61-mile week, my last truly high-mileage week for the entire cycle.  After a tempo run on the Tuesday before the race and a recovery run on Wednesday, I began a brief, four-day taper for the half-marathon consisting of an eight-mile run at around 8:00/mile pace on Thursday and a slow, four-mile shakeout run on Friday.

Before the half-marathon, I had been checking the race day weather obsessively.  The forecast at the beginning of the week indicated sub-optimal conditions; 62 degrees at the start of the race and relatively high humidity.  As the week passed, the forecast progressively got worse; by the day before the race, most weather sites predicted the temperature at the start of the race to be 68 degrees and the humidity to be in excess of 80 percent.  What was especially annoying was that the weather on the morning of that Saturday before and on the morning of that Monday after were both predicted to be much better; lower humidity and temperatures in the high fifties.  I adjusted my goal time for this half-marathon from running a PR to a time between 1:26:00 and 1:27:00.  This was somewhat annoying, but this was not my target race.

The Race

The morning of the race, I told myself that I should just power through the unpleasant racing conditions.  Warmth and humidity should not have had as drastic effect on my performance in a half-marathon as it did on my performance in a marathon.  Even if I was unable to run a PR this time, I should have been able to run a 1:27:00 or faster on this course.  Besides, the Frederick Half-Marathon in 2012 took place under similar weather conditions, yet I was still able to run a PR there.

Philadelphia is a fast course, and I knew that I at least could use that to my advantage on race day.  During the first four miles, we weave through Center City, down Broad, Market, and Arch Streets, before returning to the start near the Art Museum and heading north on Kelly Drive along the Schuylkill River.  We run along the Schuykill River for about four miles before crossing a bridge to the other side.  We the run south on Martin Luther King Drive along the other side of the river before the uphill finish near the Art Museum.  For the most part, this course is flat, aside from a gradual but long downhill segment between miles 5 and 6, a gradual and long uphill segment before the bridge crossing the river, and the relatively steep but short uphill finish.  Not only was more than half of this course adjacent to the Schuylkill, but much of it was also shaded and surrounded by trees; I anticipated the river and the trees to be very helpful in staving off overheating during this race.

Map of the Philadelphia Half-Marathon course with mile markers from the website.

Originally, I made a plan to take the first two miles a little slower and settle into a 6:35-6:40/mile pace, which I would sustain until after the bridge across the Schuylkill at around mile 9, at which point I would reassess and decide whether to accelerate or hold that pace for the remainder of the race.  My first mile was indeed my slowest at 6:41; many people flew by me during this first mile, but I ended up passing many of them back later in the race.  After training through the hot and humid DC summers for the past four years, one thing I had learned about my body was that in order to run my best on hot and humid days, I needed to start slow.

The second mile was somewhat faster at 6:36 and the third mile was significantly faster than my original target pace range at 6:28.  I finished the fourth mile, meanwhile, at 6:19, which would turn out to be my fastest mile during this race other than the last mile.  This was mostly an effect of adrenaline; as the runners starting in the earlier corrals return to the start during this mile, they get to see those in later corrals starting their races.  Many of the runners from the later corrals were quite enthusiastic, and this had an energizing effect; due to this, together with the flat and straight course in this segment, this mile has been fast for me all three times I ran this race.

Me at around the 5-mile marker.  Photo courtesy of Lavar.
As I headed toward the river, my pace slowed slightly to a 6:28/mile pace.  Lavar was on the side of the course near the mile 5 mark, watching the race; the photo to the right is of me at this point in the race.  Over the next three miles, I focused on maintaining about a 6:30/mile pace and on running the tangents.  Surprisingly, even in a race of more than 15 thousand participants, I had plenty of room around me throughout most of the race and I was able run most of the tangents.

Mile 9, not surprisingly, was the slowest mile aside from the first one.  This mile consists of a long, gradual uphill leading to the bridge across the Schuylkill, and many finishers of the Philadelphia Half-Marathon would agree that this one is one of the more difficult miles.  But having run this race twice before, I knew what to expect during this portion of the race, and told myself not to panic when my Garmin indicated a slower pace than the preceding miles and to conserve energy for the remainder of the race.  After all, the last four miles down Martin Luther King Drive were very fast and perfect for a late-race kick.

After I crossed the bridge, I began to accelerate, aiming for faster than a 6:27/mile pace.  However, this was where I began to really notice the effects of the humidity.  I felt like I was working; I was able to go a little faster, but I struggled to go much faster than 6:27/mile pace.  Miles 10 through 12 were all between 6:22 and 6:27.  Even though these miles felt difficult, I was happy to find that I was still passing plenty of people during this part of the race.

When I crossed the 12-mile marker, the clock read a little over 1:18:00.  I then realized that I actually had a chance at a PR during this race; I needed to run the thirteenth mile in about 6:15 to 6:20 and cover the last 0.1 miles in about 45 to 50 seconds.  After doing the math, and seeing Lavar again near the mile 12 mark, I picked up the pace, completing the thirteenth mile in 6:18.  At the hill leading up to the Art Museum and the finish line, I gave it everything I had.

I waited in the finish area for the other DC Front Runners to finish their race.  I was happy to report that even in spite of the warmth and humidity, several other members also got half-marathon PRs.  We all walked around the finisher's area before we returned to our hotels to shower.  Since Thorne and I were leaving at around 7:30 pm that evening, we decided to have lunch with some of the other DC Front Runners and explore Philadelphia a little.  We got to visit the Reading Terminal Market and the City Tavern, supposedly one of the most haunted places in the United States.  But otherwise, we really did not do much because we were so tired.  Note to self: if I want to explore a city, I should spend at least one more day there following the race, since I will not have the energy to explore the day of the race.

Next Steps: Chicago Marathon Time Prediction

As mentioned before, I had intended to use my time in this half-marathon as the basis of a prediction for an appropriate marathon pace in Chicago.  Since the weather was not ideal and hopefully was much warmer and more humid than the weather in Chicago would be on race day, my performance in this race may not have as much predictive power for my marathon.  I could adjust my race time for temperature and humidity and use the corrected half-marathon time, which would most likely be a minute or more faster, as the basis for my prediction, or I could be conservative and use the 1:25:12 as the basis.

I decided to do the latter.  Not only do I believe that being conservative in marathon pacing would hurt much less than being aggressive, but I do not know how reliable calculators to adjust for temperature such as Daniels Running Calculator are.  I cannot imagine anyone has actually validated these calculators; I actually am having trouble thinking of a study design that would be able to help assess whether the adjustments for temperature and humidity are anywhere near the true effect of these conditions.  The last thing I want is to believe a calculator that tells me I should have been able to run a 1:23:30, for example, in optimal racing conditions and pursue a goal based on that, only to have that adjusted time actually be an overestimate of my current fitness.

According to the Maclin calculator, a 1:25:12 on the Moderate setting of aggressiveness translates to a 3:02:04, or 6:57/mile.  I selected the Moderate setting given my mileage throughout this cycle.  If I did manage to run that time in Chicago, I would be very pleased.  I had qualified for Boston by 13 seconds during my last marathon, but due to the number of applicants exceeding the available number of slots in the Boston Marathon, only those who ran more than 62 seconds faster than their qualifying standards will be able to actually run Boston in 2015.  If I were to finish about three minutes faster than my 3:05:00 qualifying standard, then my chances of being able to run Boston in 2016 will be so much better.

So in Chicago, I will plan to target a 6:55 to 7:00/mile pace.  I will reassess at the 30K mark, and if I have the energy, I will accelerate at that point. 

Sunday, July 20, 2014

Amended Chicago Marathon 2014 Training Plan

Last week I suddenly developed pain in the Achilles tendon of my right foot.  I have no idea what caused it; perhaps it was because my running form was a little funny during this eight-mile run through the thunderstorms last Thursday, or perhaps it was a case of TMTS (too much too soon).  Before I even started my six-mile recovery run last Friday, I felt some pain in the Achilles tendon of my right foot.  The beginning of the run was fine, but about a mile in, I started to experience some flare-ups that would go away but return.  I managed to get through the run, but I could definitely feel my Achilles tendon acting up for the rest of the day.  Trying to write the alphabet with my right foot was uncomfortable, and I would feel like the Achilles tendon was pulling every time I sat down.

I decided to forego the workouts scheduled for the upcoming weekend, including an eight-mile run for Saturday and a 16-mile long run for Sunday, thinking that I would recover faster if I took the time off and let the tendon get better rather than trying to run through the pain.  Fortunately, whatever this injury was seemed to clear up very quickly; I had no flare-ups that Saturday or Sunday, so I decided to go on a very easy five-mile run on Monday to see if I was indeed better.

I successfully completed five miles on Monday, although at almost 9:00/mile pace, with no discomfort during or after the run.  Thus, I decided to try to see if I could increase the distance without my Achilles tendon acting up.  On Tuesday I ran 7.6 miles at 7:55/mile pace, and I still did not encounter problems.  On Thursday I ran 8.3 miles at a similar pace without any problems also.  For Friday, I did a six-mile recovery run, for Saturday, I did an 8.5-mile easy run at around 8:00/mile pace, and today (Sunday), I did a 15.2-mile long run starting at around 8:50/mile pace and working my way down to 7:40/mile pace by the end.  I still did not have any flare-ups during these runs, although my legs were quite tired.

I don't know how I will feel tomorrow morning, but considering the only soreness that I am feeling right now is the "I ran 51 miles last week for the first time in months" variety, I think it is quite safe to assume that whatever I had is gone.  I will have to adjust my training plan because of the weekend off from running last week, but I will still be able to hit the mileage that I originally wanted to hit for this training cycle.  Also, I am grateful that this injury happened early in the cycle rather than late.

Week 7: July 21-27, 2014 (55 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 10 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy

Sunday: 16 mile long run

Week 8: July 28-August 3, 2014 (59 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 10 mile mini-long run
Friday: 6 miles recovery
Saturday: 10 miles easy
Sunday: 18 mile long run


Week 9: August 4-10, 2014 (49 miles)
Monday: OFF
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 14 mile long run


Week 10: August 11-17, 2014 (62 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 18 mile long run


Week 11: August 18-24, 2014 (65 miles)
Monday: 8 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 21 mile long run


Week 12: August 25-31, 2014 (65 miles)
Monday: 6 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 18 mile long run


Week 13: September 1-7, 2014 (68 miles)
Monday: 8 miles recovery
Tuesday: 12 miles with 9 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 21 mile long run


Week 14: September 8-14, 2014 (63 miles)
Monday: 6 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 16 mile long run


Week 15: September 15-21, 2014 (37.1 miles -- tune-up race week)
Monday: 5 miles recovery
Tuesday: 7 miles with 4 miles at tempo pace
Wednesday: OFF
Thursday: 7 mile easy run
Friday: 5 miles recovery
Saturday: OFF
Sunday: Philadelphia Rock and Roll Half-Marathon


Week 16: September 22-28, 2014 (48 miles)
Monday: OFF
Tuesday: 6 miles recovery
Wednesday: 5 miles easy
Thursday: 8 mile mini-long run
Friday: 5 miles recovery
Saturday: 8 miles easy
Sunday: 16 mile long run with 12 at marathon pace


Week 17: September 29-October 5, 2014 (34 miles)
Monday: OFF
Tuesday: 6 miles at marathon pace
Wednesday: OFF
Thursday: 6 miles at marathon pace
Friday: 4 miles recovery
Saturday: 6 miles easy
Sunday: 12 mile long run


Week 19: October 6-12, 2014 (Race week)
Monday: OFF
Tuesday: 4 miles at marathon pace
Wednesday: OFF
Thursday: 3 miles easy
Friday: 3 miles easy
Saturday: OFF
Sunday: Chicago Marathon

Monday, June 16, 2014

Chicago 2014 Training Plan

During the last two training cycles, I finally listened to the advice of superior and more experienced marathoners about increasing my weekly mileage during training in order to improve.  I definitely did see the effects of higher mileage.  Even though the sauna-like weather in Corning, New York on the day of the Wineglass Marathon in 2013 on race day prevented me from really running my best, I chopped off a minute and a half off my half-marathon PR in the Philadelphia Rock and Roll Half-Marathon following a cycle of increased mileage.  For the Shamrock Marathon in Spring 2014, I increased my overall mileage a little more and ended up finally qualifying for Boston.

For Chicago, I am hoping to improve my time even more, so that I can increase my chances of being able to run Boston in 2016.  In Shamrock, I had beaten the qualifying standard for men 34 years old and younger by 13 seconds.  Since people who beat their qualifying times by larger margins get higher priority for entry into Boston, there may be a chance that the field will fill up before I am allowed in.  That happened for Boston 2014; only those who beat their qualifying times by 98 seconds or more were accepted.

Thus, for Chicago, my training will consist of significantly higher mileage than what I did for Wineglass and Shamrock.  Whereas for those two marathons, I was averaging in the high 40s in terms of miles per week during training and hitting mileage highs in the mid 50s, this time, I would be averaging in the high 50s per week, running 60 miles or more during several weeks of the cycle and hitting a maximum of 68 miles two weeks before my tune-up half-marathon, the Philadelphia Rock and Roll Half-Marathon on September 21.  I am keeping the structure of each week simple, borrowing elements from the Pfitzinger 18/70 training plan such as a mid-week mini-long run of between 10 and 14 miles.  Each week will consist of recovery runs on Mondays and Fridays, runs with tempo segments on Tuesdays, mini-long runs on Thursdays, easy runs on Saturdays, and long runs on Sundays.

But first, here are definitions of each of the types of runs in this training program:

Easy run: general putting-in-the-miles runs done at a very relaxed effort, which will typically translate to about 55 to 75 percent of 5K pace.  I usually do mine at about 8:00 to 8:20 per mile, which falls well within this range.  If you feel like you are pushing on these runs, you are running them too hard.

Tempo run: a run with a large portion of it done at a significantly harder effort than easy runs.  Tempo runs should be run at a pace that you could sustain for about an hour, which, on a day where the temperature is below 60 degrees Fahrenheit, is approximately 15 to 20 seconds slower than 10K race pace, which for me is about 6:25 to 6:30 per mile.  The purpose of tempo runs is to build speed and strength; these are not sprints, but rather, hard, controlled efforts; going much faster than the prescribed pace works a different physiological characteristic, one that is much less important to performance in the marathon than the one that tempo runs are supposed to work.

Long run: a run lasting 90 minutes to three hours to build endurance done at about 65 to 75 percent of 5K pace.  For me, this is between about 7:40 and 8:50 per mile.  Typically, I like to start at the slower end of that range and gradually progress toward the faster end by the end of the run.  In some of my long runs, particularly those later on in the cycle, I will progress right to marathon race pace.

Mini-long run: a scaled-down version of the long run, done during the middle of the week in addition to the long run in the later weeks of the cycle to help build endurance.  These are done similar to long runs, except they are shorter in distance.

Recovery run: a run following a hard workout such as a tempo run or a long run, done at a pace even slower than easy run pace.  My usual paces for these are between 8:30 and 9:00 per mile, with some of them being 10:00 per mile or slower, particularly following a race.  Similar to the easy run, if you are pushing on recovery runs, you are running them too hard.

Marathon pace run: a run done at target marathon race pace.  The marathon race pace runs in this cycle include a 16-mile long run with the central 12 miles done at marathon race pace, as well as a few shorter marathon pace runs ranging between 4 and 6 miles.  These occur only after the tune-up half-marathon, as the half-marathon will provide me with an idea of a pace that I could realistically run on race day.

Finally, although intervals (repeats) appear on many people's training regimens, I have decided to omit them during my training for Chicago.  The physiological characteristic that intervals work are less crucial to marathon performance, and I actually ran my best marathon without doing any intervals.  These types of workouts would indeed be very useful for shorter distances, but I am currently quite satisfied with my 5K and 10K times.  I will probably start those up again when I focus on improving in the shorter distances, but for now, I need to work on my endurance most of all.  Whereas my best recent half-marathon and marathon times are respectively 1:25:25 and 3:04:47, my best recent 5K time of 0:18:10 predicts that I should run the half-marathon in 1:24:07 and the marathon in 2:57:01 and my best recent 10K time of 0:38:10 predicts a half-marathon time of 1:25:05 but a marathon time of 2:59:04.

Week 1: June 9-15, 2014 (40 miles, including a Trail Ragnar Relay)
Monday: 5 miles easy
Tuesday: 8 mile mini-long run
Wednesday: OFF
Thursday: 5 miles easy
Friday: West Virginia Appalachian Trail Ragnar
Saturday: West Virginia Appalachian Trail Ragnar
Sunday: 4 miles recovery

Week 2: June 16-22, 2014 (44 miles)
Monday: OFF
Tuesday: 6 miles easy
Wednesday: 5 miles easy
Thursday: 8 miles with 5 miles at tempo pace
Friday: 6 miles recovery
Saturday: 7 miles easy
Sunday: 12 mile long run

Week 3: June 23-29, 2014 (48 miles)
Monday: 5 miles recovery
Tuesday: 8 miles with 5 miles at tempo pace
Wednesday: OFF
Thursday: 8 mile mini-long run
Friday: 6 miles recovery
Saturday: 7 miles easy
Sunday: 14 mile long run

Week 4: June 30-July 6, 2014 (40 miles)
Monday: OFF
Tuesday: 8 miles with 5 miles at tempo pace
Wednesday: OFF
Thursday: 8 mile mini-long run
Friday: 7 miles recovery
Saturday: 7 miles easy
Sunday: 10 mile long run

Week 5: July 7-13 2014 (53 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 8 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 16 mile long run

Week 6: July 14-20, 2014 (58 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 10 mile mini-long run
Friday: 7 miles recovery
Saturday: 8 miles easy

Sunday: 18 mile long run

Week 7: July 21-27, 2014 (60 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 5 miles at tempo pace
Wednesday: OFF
Thursday: 10 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 21 mile long run


Week 8: July 28-August 3, 2014 (50 miles)
Monday: OFF
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 10 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 14 mile long run


Week 9: August 4-10, 2014 (59 miles)
Monday: 8 miles recovery

Tuesday: 9 miles with 5 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 16 mile long run


Week 10: August 11-17, 2014 (62 miles)
Monday: 6 miles recovery
Tuesday: 9 miles with 6 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 18 mile long run


Week 11: August 18-24, 2014 (65 miles)
Monday: 8 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 12 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 21 mile long run


Week 12: August 25-31, 2014 (65 miles)
Monday: 6 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 18 mile long run


Week 13: September 1-7, 2014 (68 miles)
Monday: 8 miles recovery
Tuesday: 12 miles with 9 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 6 miles recovery
Saturday: 8 miles easy
Sunday: 21 mile long run


Week 14: September 8-14, 2014 (63 miles)
Monday: 6 miles recovery
Tuesday: 10 miles with 7 miles at tempo pace
Wednesday: OFF
Thursday: 14 mile mini-long run
Friday: 7 miles recovery
Saturday: 10 miles easy
Sunday: 16 mile long run


Week 15: September 15-21, 2014 (37.1 miles -- tune-up race week)
Monday: 5 miles recovery
Tuesday: 7 miles with 4 miles at tempo pace
Wednesday: OFF
Thursday: 7 mile easy run
Friday: 5 miles recovery
Saturday: OFF
Sunday: Philadelphia Rock and Roll Half-Marathon



Week 16: September 22-28, 2014 (48 miles)
Monday: OFF
Tuesday: 6 miles recovery
Wednesday: 5 miles easy
Thursday: 8 mile mini-long run
Friday: 5 miles recovery
Saturday: 8 miles easy
Sunday: 16 mile long run with 12 at marathon pace



Week 17: September 29-October 5, 2014 (34 miles)
Monday: OFF
Tuesday: 6 miles at marathon pace
Wednesday: OFF
Thursday: 6 miles at marathon pace
Friday: 4 miles recovery
Saturday: 6 miles easy
Sunday: 12 mile long run


Week 19: October 6-12, 2014 (Race week)
Monday: OFF
Tuesday: 4 miles at marathon pace
Wednesday: OFF
Thursday: 3 miles easy
Friday: 3 miles easy
Saturday: OFF
Sunday: Chicago Marathon

Sunday, March 30, 2014

Race Post-Mortem: Shamrock Marathon

The sign that Thorne made for all of us running the Shamrock Half-Marathon and Marathon.  Go Miss Pam!

Sunday, March 16, 2014
Virginia Beach, VA
Difficulty score: 2/10 (1 for weather, 1 for course profile, 0 for altitude)

I finished the Shamrock Marathon in 3:04:47 (7:03/mile).  This was the first time I had qualified for Boston.  Even though there is a good chance that I might not get to run the Boston Marathon in April 2015, as I had only run 13 seconds faster than the 3:05:00 qualifying standard for men aged 34 or younger and runners who beat their qualifying standards by larger margins get higher priority for entry, I still consider my first Boston Qualifier a significant achievement in and of itself.

I actually did not think that I would qualify during this race.  3:04:59 was my "if everything goes right" goal, but when I lined up at the start, I was expecting to finish between 3:06:00 and 3:07:00.  My plan was to take the first few miles to ease into a 7:05 to 7:10/mile pace, and then to hold that pace until the 30K mark, at which point I would assess how I was feeling.  If I was feeling strong, I would accelerate; otherwise, I would try to maintain a 7:05 to 7:10/mile pace.  Under this plan, "everything going right" would have meant that I stayed within that range for the first 30K, and then averaged 6:53/mile for the remainder.  While I had been able to average 6:53/mile or faster in the last 10K of previous marathons, whether or not the initial 7:05 to 7:10/mile pace in the earlier miles would be enough to exhaust me by the time I hit the 30K mark was unknown.  Plus, the headwinds that I was expecting for large segments of the race would certainly make execution of this plan more difficult.

But I was able to execute the "if everything goes right" scenario, even in spite of some relatively slow early miles.  I stayed within my target range for most of the first 30K as planned, finishing most of these miles near the slower end of that range and crossing the halfway point in 1:34:20.  I accelerated after the 30K mark, ultimately bringing my pace to faster than 6:40/mile from the mile 23 mark onward and finishing the second half of the marathon in 1:30:27.  Some may argue that had I been less conservative in the beginning and run more even splits, I would have finished with an even faster time, but looking back, I would not have executed this race any differently.

Training

I decided to use a training program similar to the one I used for the Wineglass Marathon, thinking that I did something right last time given my substantial PR in the Philadelphia Half-Marathon.  Like the previous training program, I would run six days a week, with Tuesdays being tempo runs of six miles or more, Wednesdays and Fridays being recovery runs of between four and six miles, Saturdays being easy runs of six or seven miles, and Sundays being long runs.  However, this time around, I decided to eliminate the track workouts and the hill workouts that would be my Thursday runs.  Realizing that the Shamrock Marathon course was extremely flat, I would not need hill workouts.  I wanted to focus on maximizing mileage during this training cycle; eliminating track workouts and hill workouts allowed me to do a second tempo run for the week on Thursdays, which allowed me to add another two or three miles to my weekly mileage.  Besides, during the winter, the DC Front Runners run up and down Massachusetts Avenue NW from P and 23rd Street every Thursday.  That route is essentially a hill workout for the first half and a track workout for the second; the first three miles out to Ward Circle consist largely of three steep and long hills, which we run down on the way back.  This segment of Massachusetts Avenue had fewer traffic lights than usual, which would allow me to attain a good speed for extended segments.

Thus, my mileage during this training cycle was slightly higher.  During my training for the Wineglass Marathon, I averaged 46 miles per week, excluding the initial four-week mileage buildup and the taper, with a maximum weekly mileage of 54 miles.  This time, I averaged 48 miles per week, again excluding the initial four-week mileage buildup and the taper, with a maximum weekly mileage of 57 miles.  I kept my training paces the same.  For tempo runs, I targeted between 6:20 and 6:30/mile; achieving this pace on my Tuesday night tempo runs, which took place on the National Mall, was definitely feasible, but the hills on Massachusetts Avenue often made hitting this pace difficult during the first half of my Thursday night tempo runs.  For the Saturday easy runs and Sunday long runs, I targeted around 7:55/mile.

Execution of this training plan went smoothly, aside from the initial heel discomfort at the beginning of the cycle that later inexplicably vanished, and the snow and the cold.  Washington, DC had one of its coldest and snowiest winters in several years, and this was definitely the most snow I had encountered in this city since I started running marathons in 2011.  The cold made some of the runs a little uncomfortable, but largely did not affect my training.  Due to the snow, I did, however, have to turn several of my tempo runs into easy runs; footing was treacherous, and running at my usual pace through several inches of snow was just not possible.  Running through snow definitely worked muscles that I had not worked in a long time.

The Days Leading Up to the Event

Three weeks prior to the marathon, I ran the Colonial Williamsburg Half-Marathon as a tune-up race, hoping to assess whether my marathon race plan was realistic and to get back into the racing mindset; this was, after all, to be my first race in over two months.  Race day was bright, sunny, and unseasonably warm; the temperature at the start of the race was 71 degrees.

I finished this half-marathon in 1:28:25, 21 seconds slower than when I ran it last year.  I knew at the start that I was not going to get anywhere near a half-marathon PR on this very hilly course.  But even in spite of the temperature, I would have at least have beaten my previous year's time.  I did know that a 1:28:25 in 71 degrees would have most likely translated into a time faster than 1:28:00 in the the mid-fifties that it was the previous year, but I could not shake the feeling that this may have been an indication that my race plan was unrealistic.

But unlike the previous two training cycles, I did not completely screw up my taper.  I had researched proper tapering, something that I had not done before, and obeyed two important recommendations: to refrain from too drastic a reduction in mileage and to never run much faster than target marathon pace.  Looking back, I certainly did not do the latter during the taper periods preceding my last two marathons, and that might have prevented me from doing my best.  Nine days before the USA Marathon in March 2013, I had turned what was supposed to be a marathon-pace tempo run into an all-out race between another member of DC Front Runners, where at the end we were going faster than 5:50/mile pace.  The twelve-mile marathon-pace run I did two days after that went disastrously; had that been race day, I would have walked off the course.  Five days before the Wineglass Marathon, I did a six-mile tempo run where I was running between 6:30 and 6:35/mile pace; given the 72 degree weather that afternoon, that kind of effort would have resulted in an even faster time in cooler temperatures.

This time, the very last truly difficult workout I would do before the marathon was a marathon-pace long run two weeks before the race; here, after a two-mile warm-up, I would run twelve miles at target marathon pace, after which I would finish with a two-mile cool-down.  After that, my workouts would only consist of easy runs and marathon-pace runs.  I strictly adhered to this plan.  Most of my marathon-pace runs did not turn out to be marathon pace, however.  During the first one, which took place two days after that marathon-pace long run, what felt like marathon effort actually turned out to be about 7:40/mile pace; even though my legs felt fine, that long run was having an effect on my running.  During a marathon-pace run the following Tuesday, the 70 degree weather forced me to go a little slower.  Regardless, I was glad I erred on the side of running too slowly during these final weeks.

The week preceding the marathon, I focused on consuming carbs whenever I could and staying hydrated.  I also tried to stay off my feet as much as possible during the few days leading up to the race.

The Race

Race morning was cold and windy; 44 degrees with 57% humidity and a 13 mile-per-hour wind coming from the northeast due to the approaching cold front.  The temperature and humidity were great for a marathon, but I would be running into a strong headwind between much of miles 6 through 16.

Fortunately, the course was very flat.  This course consisted of two loops, the first of which would go south toward Fort Pendleton and back to the start along the boardwalk and Atlantic Avenue, and the second of which would go north along Atlantic Avenue and U. S. Route 60 toward Fort Story, past the Cape Henry Lighthouse, and back by way of Atlantic Avenue and the boardwalk.  This course only had three hills: the overpass at mile 3 leading us south, which we would run again at mile 9, and the slight but significantly longer uphill at mile 20 in Fort Story.  All of these were mere speed bumps compared to the hills in the Baltimore or USA Marathons.

Overall, I liked the course very much, even if much of it was not particularly aesthetically pleasing.  The stretches along Atlantic Avenue were lined mostly with hotels and stores.  The wooded segment between miles 16 and 19 down U. S. Route 60 toward Fort Story and the areas along the beach near the lighthouse were actually quite visually attractive.  But what I did like about this course was the crowd; I do not think I ever went even one quarter of a mile without a group of spectators cheering for us.  Most notably, the Air Force men and women in Fort Pendleton provided a much-appreciated cheering section between miles 8 and 9, and the stretch down Atlantic Avenue between miles 13 and 16 and between miles 23 and 26 was lined with people.  The latter were certainly helpful in motivating me during those middle miles and at the end of the race.

I ran the first mile rather conservatively, finishing it in 7:14.  Over the next ten miles, my pace stayed between 7:09 and 7:11/mile.  During this segment of the race, I kept thinking to myself that I would have liked to run at a faster pace, but this was the pace that my body was telling me to run: a comfortable pace, yet an honest effort.  At this point in the race, I was not even thinking of qualifying for Boston.  But it was okay; if I kept this pace throughout, I still would have gotten a PR, and I would have been happy with that.

I fueled exactly as I planned, taking water or Gatorade at every water station before mile 18 and consuming three Shot Blocks every three to four miles until mile 18.  A little past mile 4, a member of the Capital Area Runners caught up with me.  I did not get his name, but he asked me what pace I was targeting; when I told him that I was aiming for between 7:05 and 7:10/mile, he said that was similar to what he wanted to run that day.  We talked about the course and previous marathons in short spurts of conversation.  Between miles 6 and 7, he pulled ahead and I relaxed a little, noticing that the first half of that mile was a little fast.  I was actually grateful we parted ways here; he was a talker, and I wanted to concentrate on my race.

Several more people passed me on the way to Fort Pendleton, and I just let them, knowing that my pace was fine and that at this point, I needed to just run my own race.  I got a burst of energy thanks to the Air Force men and women along the course in Fort Pendleton, but I did my best to keep my pace under control.

After we left Fort Pendleton, we were to go back across the overpass, through the Rudee Inlet, and along the boardwalk back to Atlantic Avenue.  I faced constant and powerful headwinds along the boardwalk.  My first instinct was to run behind somebody; I got in the back of a line of runners who were thinking the same thing.  I ran with them for a little while, and passed them when I wanted to go faster.  I continued running into the headwinds, being careful to stay relaxed and not charge ahead.  Surprisingly, my pace stayed constant throughout this segment of the race.  

But the segment along Atlantic Avenue after we left the boardwalk was even worse in terms of headwinds. This was a wind tunnel where my pace did actually slow; I ran mile 12 in 7:14, my slowest in this race since the first mile. Several times here, I felt like the wind was going to blow the visor off my head.

The headwinds were noticeably less severe for the next several miles down Atlantic Avenue, but they were still strong and constant. My thoughts during these miles were just to get through them; I knew that once I reached that wooded segment along U. S. Route 60, I would have some respite from the headwinds. On this stretch, my pace stayed constant, I felt fresh at the halfway mark, and I was actually able to run my fastest mile so far: 7:06 for mile 13. I drafted behind other runners; I was able to tell some of them were getting a little annoyed with me, but I did not really care. I was there to run a PR, not make new friends.

As expected, the segment along U. S. Route 60 was much easier with the trees around me blocking almost all of the headwinds. I continued to feel strong and my pace started to veer toward the faster end of the 7:05 to 7:10/mile range that I was hoping to run for the first 30K. Thus, at the 30K mark, I started speeding up in accordance with my original plan. I averaged 6:53/mile for miles 19 and 20, encountering Rich, a friend from DC now living in Williamsburg, watching the race from the side of the road near the mile 19 mark.

Miles 21 and 22 through Fort Story and past the Cape Henry Lighthouse were quite difficult. The headwinds were back and even stronger than before. At times, I felt like the wind would rip the race bib right off my shirt; my race bib rippled and vibrated with the wind. Plus, I had to deal with a slight but long uphill toward the lighthouse. Unlike that stretch up Atlantic Avenue, I could not find anyone that I could run behind to hide from the headwinds; runners were quite sparse at this point. I just focused on getting through this part, knowing that the direction of the wind meant that once I got back onto Atlantic Avenue at around mile 23, this headwind would become a tailwind. My paces for these two miles were 7:01 and 7:02; a little slower than those for miles 19 and 20.

The remainder of the race was much easier since the headwinds, for most of the return trip to the boardwalk down Atlantic Avenue, were not nearly as strong. At this point, given the previous four miles, I adjusted my goal finishing time from 3:06:00 to 3:07:00 to 3:05:00 to faster than 3:06:00. I was perfectly aware that, given my pace, that I would finish with a time so infuriatingly close to yet short of my Boston Qualifying standard like 3:05:20, but that would have still been a PR and a success for this race. I pushed the pace, not really looking at my watch for the next three miles, but running mile 23 in 6:40 and mile 24 in 6:33. It was not until I crossed the mile 25 marker in 2:56:40 that I realized finishing faster than 3:05:00 was now a possibility.

But I had no room for error if I was going to try to qualify for Boston in this marathon. Running mile 26 in 6:35 and the remainder of the race in 1:45 would have done it. The possibility of qualifying for Boston evidently motivated me to run even faster as I covered mile 26 in 6:19. Turning the corner back onto the boardwalk, I could see the finish line. However, the headwinds had returned, just as powerful as before. This time, I charged through the headwinds, breaking into a full-out sprint for the last hundred meters or so before the finish line.

I collected my medal, something to drink, and a beach towel that all finishers received, and waited for Grace to finish, after which we walked around the finisher's tent on the beach and then boarded a taxi to return to the hotel.

Lessons Learned

This race certainly gave me reason to believe that higher mileage pays off in the marathon. In March 2013, while training for the USA Marathon, I averaged 38 miles per week, excluding the initial mileage buildup and the taper, with a maximum weekly mileage of 45 miles. This time, I averaged 48 miles per week, again excluding the initial mileage buildup and the taper, with a maximum weekly mileage of 57 miles, and it coincided with a three and a half minute PR. Some other marathoners with whom I discussed this race at the hotel later that day believed that I may have gotten an even better time had the headwinds not been so strong.

This entire cycle made me realize that what I do the two weeks preceding the marathon are also extremely important. As many online sources on tapering for a marathon had said, there was nothing I could do during these two weeks could improve my fitness before the race, but there was plenty I could do to screw up my race. After a much better-executed taper this time, I felt fresh and energetic at the start line and I felt strong throughout. The weather during the Wineglass Marathon probably would have obscured any adverse effects of an improper taper, but I would imagine that even if the temperatures were cooler, I still would not have performed my best. After all, a too-intense workout too close to the race would probably have affected my performance during the marathon in the way that the 16-mile marathon pace run significantly slowed my pace during the marathon pace the following Tuesday.

Next Steps

After I finish recovering from this marathon, I will run a few shorter races, one of which will definitely be the Pike's Peek 10K in Rockville, MD at the end of April. Between the fitness gain from this training cycle and the net downhill point-to-point course, I am hoping for a 10K PR. If I am feeling ready, perhaps I will also do the George Washington Parkway 10-Miler on April 13. I have never done a 10-Miler before. I will not run any races in May, but I will be running my first trail race: the West Virginia Appalachian Trail Ragnar in the middle of June.

My next marathon will be the Chicago Marathon on October 12. Training for this will begin after the Trail Ragnar. For this upcoming training cycle, I am hoping to increase my mileage, hitting a maximum weekly mileage of 65 to 70 miles, in order to improve my marathon time even more. A sub-three-hour marathon in Chicago would be great, but I will even be happy with an improvement of two or three minutes. After all, the faster my time in Chicago, the better my chances for being able to run the Boston Marathon in 2016.

I will apply to run the Boston Marathon in April 2015 anyway, even though there is a chance my time may not be fast enough for me to get accepted. For the 2014 Boston Marathon, only people who beat their qualifying standard by 98 seconds or more were accepted. But I suppose it could not hurt to try.