Watch Greg Run
Watch Greg Run began as an online journal of my effort to run a marathon each month during 2009. With the marathon a month challenge successfully behind me, I'm still running and still posting with notes on training runs, travel and other thoughts.
Wednesday, May 26, 2010
My Achilles Heel
Achilles also has the attributes of being the most handsome of the heroes assembled against Troy (not Troy, Alabama for purposes of this story).
Later legends (beginning with a poem by Statius in the first century AD) state that Achilles was invulnerable in all of his body except for his heel. Since he died due to an arrow shot into his heel, the "Achilles' heel" has come to mean a person's principal weakness.
Leaving the story of Ancient Greece, in modern day life the risk of being felled by an arrow to the heel is minimal. The absence of an archer with an accurate shot does not mean modern medicine has eliminated the occurrence of heel pain.
Last November my Achilles started to ache. After a few weeks, the ache progressed to hurt. Eventually, the ache and hurt, became pretty much constant pain and stiffness in my heel. I had to just deal with the pain at the end of my "One a Month" effort, but it wasn't any fun. During marathons this January and February, I just dealt with it by hoping it would not hurt too much. A bit of rest in March did nothing to resolve the problem. Five weeks of rest from running after the Boston Marathon still has not solved the problem.
So, it's off to the orthopedist's office I go. I'm still trying to run, but at a reduced distance and intensity. Ice, stretching, new shoes, and The Stick have all failed to solve the problem.
The good news is I have started to search for a fall marathon event. If I wait until November for my next race, my training plan does force me to add significant mileage until late July. Hopefully between now and then I can access some relief to my personal vulnerability.
Sunday, May 16, 2010
A Couple Days Off
Wednesday, April 28, 2010
A Green Light Run
I spent a few days this week in downtown Indianapolis, which includes plenty of stop lights, cross walks, side walks, construction projects, and some quality running trails just outside of downtown. Tuesday, rather than settle for the starting and stopping, or heading out on a trail, I opted for a "green light run."
In the interest of full disclosure, I'm not exactly certain the term "green light run" originated with me. But, I honestly cannot point to a time, place or magazine where I either heard or read about someone completing a green light run. It was during a trip to San Jose in mid-March on a day when I needed at least an 8 mile run when, after the previous day of stops and starts during a run in downtown San Jose, I had the thought to just follow the green lights...and "green light runs" were created, at least for me.
The concept is not very complicated. Head out of the hotel (or your downtown apartment)...take a left (or a right, whichever you prefer)...head toward the corner. When you reach the corner, if the stop light is green you keep running straight. If the stop light is red, you take a left...or a right (for me on Tuesday, the light was red and I turned left). Head down the block to the next intersection, where the stop light on Tuesday was red and I took another left.
There are a couple of tricks to this concept. If you catch every red light, and you keep turning left...the result is you just keep running around the block. Back in San Jose, I ran around the same block four consecutive times before reaching a corner where the green light allowed me to cross the street. The "around the block" syndrome can happen at any point in a green light run, if you keep turning the same direction you just keep running around the block...and you get a little dizzy if it is a small block.
Through good timing, a left turn, a right turn and the decision to wait for a green light rather than make a turn, you can actually find a good run in a downtown setting. In fact, if you need to complete a long run on a day when you end up in a new city, green light runs keep you moving and draw your attention away from just running since you have to watch those lights and cross walk signals.
As beneficial as they may be, you do have to pay attention to your direction during a green light run. Otherwise you run the risk of ending up ten blocks over and 14 blocks down from where you started, with no real idea how to make it back.
Monday, April 26, 2010
What's Next?
When I (finally) crossed the finish line last Monday in Boston, it was the first time in a little over three years that I was not entered to run a marathon. In reality, that's not a big deal. Not at all.
But, as it relates to running, it is a bit of a deal. I don't have a training program. My running partner is my iPod or, recently, my iPhone. My iPhone has yet to say, "Hey, I'll meet you at 5:30 in the morning for a run," although I'm certain it would say that if properly programmed. The net of all that is I won't disappoint my neighboorhood running if I choose to sleep in rather than go for a run.
Today finds me in Indianapolis. My morning run was in the drizzle. Not because I had to run, just because I wanted to run.
Of all the good things I enjoyed during the "marathon a month" effort, at some point I lost the notion of just running because I wanted to go for a run. I spent a year thinking about the need to run each day or, at least, most days to prepare for the next marathon. I missed the simple enjoyment of just going for a run.
Today, drizzle or no drizzle, my morning run was fun. All 3.84 miles of it. Around a downtown block, toward Lucas Oil Stadium (site of this year's Final Four), down the street to Eli Lily's corporate headquarters, back toward downtown, a left hand turn to the memorial plaza followed by another left hand turn to Monument Circle. I didn't have to run for an hour. I didn't have to run a certain number of miles. I wasn't following some training plan. Today, I just ran because I felt like it, and I stopped when I felt like stopping.
After last week, I decided to slow it down a bit. Run regularly, just a little less. And to find a fall marathon that would come after I complete an actual training program.
Friday, April 23, 2010
More Data
While reading Watch Greg Run I began to wonder how many other marathons I might be able to find with information on my progress through each 5 kilometers. In other words, I started thinking about other marathons that might include a timing system similar to Boston. My "Aha" moment came when I thought about New York City, which proved to be right.
Based on my results in New York, I have compiled a new listing of marathon times broken out in 5 kilometer segments. You may not find this very interesting, but it is helping me consider how to alter my preparation plan for the next marathon I run.
Distance 5K (3.1 Miles)
NYC 2007 41min, 35sec (clearly, the big crowd results in a very slow start)
BOS 2008 28min, 16sec
BOS 2009 28min, 41sec
NYC 2009 26min, 01sec (I started up front)
BOS 2010 28min, 26 sec
Distance 10K (6.2 Miles)
NYC 2007 1hr, 09min, 53sec
BOS 2008 57min, 25sec
BOS 2009 57min, 58sec
NYC 2009 53min, 28sec
BOS 2010 57min, 05 sec
Distance 15K (9.3 Miles)
NYC 2007 1hr, 38min, 20sec
BOS 2008 1hr, 26min, 28sec
BOS 2009 1hr, 28min, 32sec
NYC 2009 1hr, 21min, 38sec
BOS 2010 1hr, 26min, 14sec
Distance 20K (12.4 Miles)
NYC 2007 2hrs, 08min, 33sec
BOS 2008 1hr, 58min, 01sec
BOS 2009 1hr, 58min, 20sec
NYC 2009 1hr, 50min, 31sec
BOS 2010 1hr, 56min, 10sec
Distance (13.1 Miles)
NYC 2007 2hrs, 14min, 37sec
BOS 2008 2 hrs, 4min, 15sec
BOS 2009 2hrs, 4min, 57sec
NYC 2009 1hr, 56min, 49sec
BOS 2010 2hrs, 3min, 04sec
NOTE: The 2010 Boston winner, Robert Kiprono Cheruiyot from Kenya, completed the ENTIRE course in 2hrs, 5min, 52 sec.
Distance 25K (15.5 Miles)
NYC 2007 2hrs, 38min, 39sec
BOS 2008 2hrs, 27min, 54sec
BOS 2009 2hrs, 28min, 02sec
NYC 2009 2hrs, 20min, 26sec
BOS 2010 2hrs, 28min, 53sec
Distance 30K (18.6 Miles)
NYC 2007 3hrs, 08min, 57sec
BOS 2008 3hrs, 0min, 29sec
BOS 2009 3hrs, 0min, 22sec
NYC 2009 2hrs, 51min, 53sec
BOS 2010 3hrs, 1min, 32sec
Distance 35K (21.7 Miles)
NYC 2007 3hrs, 39min, 19sec
BOS 2008 3hrs, 32min, 5sec
BOS 2009 3hrs, 34min, 7sec
NYC 2009 3hrs, 22min, 22sec
BOS 2010 3 hrs, 37min, 08sec
Distance 40K (24.8 Miles)
NYC 2007 4hrs, 10min, 27sec
BOS 2008 4hrs, 7min, 10sec
BOS 2009 4hrs, 9min, 29sec
NYC 2009 4hrs, 0min, 48sec
BOS 2010 4hrs, 20min, 25sec
Finish (26.2 Miles)
NYC 2007 4hrs, 11min, 47sec
BOS 2008 4hrs, 21min, 34sec
BOS 2009 4hrs, 25min, 27sec
NYC 2009 4hrs, 17min, 27sec
BOS 2010 4hrs, 35min, 52sec
It's interesting for me to evaluate the times in these five marathons.
My first thought is the wave starting system in Boston really helps the runners move along. Yes, the course is packed with people, but the comparison of times shows how slow the starting time was during my 2007 run in New York. In contrast, starting up front in New York shaved 15 minutes off my first 5 kilometers and, when you look at Boston, there is a consistency in time during the first 5 kilometers that actually looks much more like the race when I started at the very front of the New York City Marathon.
The second thought is my times bear out the challenge of the Boston course and its hills. In contrast, the New York course is generally flat and easier on a runner's legs.
Third, as slow as I started the 2007 New York City Marathon, the fast times at the end of the day show that starting slow pays dividends at the end of a marathon. I don't quite understand the quick time between the 40k mark and the finish line. My guess is the 40k time is actually a bit slower than the actual time due to a timing problem. Since I had timed my run that day with a watch, I know the finishing time is correct.
Like I said, it's not that interesting...but it is interesting to me.
Tuesday, April 20, 2010
Comparing Boston Results
Explanations for my performance? Best one I can figure out after running well in February (finished Mercedes Marathon in 3hrs, 59min) is that my schedule in March makes training difficult...most notably as it relates to finding time and a location for a quality long run. Training rule #1: Don't neglect the long run...which I did.
Distance 5K (3.1 Miles)
2008 28min, 16sec
2009 28min, 41sec
2010 28min, 26 sec
Distance 10K (6.2 Miles)
2008 57min, 25sec
2009 57min, 58sec
2010 57min, 05 sec
Distance 15K (9.3 Miles)
2008 1hr, 26min, 28sec
2009 1hr, 28min, 32sec
2010 1hr, 26min, 14sec
Distance 20K (12.4 Miles)
2008 1hr, 58min, 01sec
2009 1hr, 58min, 20sec
2010 1hr, 56min, 10sec
Distance (13.1 Miles)
2008 2 hrs, 4min, 15sec
2009 2hrs, 4min, 57sec
2010 2hrs, 3min, 04sec
NOTE: The 2010 winner, Robert Kiprono Cheruiyot from Kenya, completed the ENTIRE course in 2hrs, 5min, 52 sec.
Distance 25K (15.5 Miles)
2008 2hrs, 27min, 54sec
2009 2hrs, 28min, 02sec
2010 2hrs, 28min, 53sec
Distance 30K (18.6 Miles)
2008 3hrs, 0min, 29sec
2009 3hrs, 0min, 22sec
2010 3hrs, 1min, 32sec
Distance 35K (21.7 Miles)
2008 3hrs, 32min, 5sec
2009 3hrs, 34min, 7sec
2010 3 hrs, 37min, 08sec
Distance 40K (24.8 Miles)
2008 4hrs, 7min, 10sec
2009 4hrs, 9min, 29sec
2010 4hrs, 20min, 25sec
Finish (26.2 Miles)
2008 4hrs, 21min, 34sec
2009 4hrs, 25min, 27sec
2010 4hrs, 35min, 52sec
Boston Post-Race
After finishing, I heard any number of conversations among runners and their family members about problems with the AT&T Athlete Alert system. Apparently, it was not very alert during the day. For the curious, I received this email last night:
The Boston Marathon would like to apologize to all who signed up for this year's Athlete Alert Program. The BAA experienced an internal technical problem which prevented accurate athlete information from being sent to the proper email addresses and mobile phone numbers. This issue was not related to any services provided by the program's sponsor, AT&T, nor was it the result of failures of any of the Boston Marathon's technology partners. Beginning at 12:52 p.m., the system was fixed.
I'm still waiting to receive my first update.
Here are a few notes about the marathon from the perspective of runner 23849 (that would be me):
- I placed 19995 out of 22540 runners. Officially, there were 26,970 entrants in the Boston Marathon, with 2,849 "no shows" who failed to pick up their race bib.
- The Boston Globe reported that 1,325 runners required medical attention along the course, with 33 of those requiring a visit to the hospital.
- Various news outlets have reported on a 60 year old runner who collapsed from cardiac arrest while running with his son, and had to be revived by EMS staff and bystanders using CPR and an automated external defibrillator. According to news reports, he was admitted to the hospital and was listed as being in stable condition last night.
- I was not terribly fast yesterday, but I did finish ahead of Valerie Bertinelli. So, I got that going for me, which is nice.
- No complaints about the weather from me. It started sunny, clouded up when I made it to the 9-mile mark, and alternated between sunny and cloudy the last 8 miles.
- This was my third consecutive running of the Boston Marathon. It is the first time I've been able to enjoy the downtown atmosphere after finishing the race. In 2008, I had a flight scheduled on Monday evening. On that day, I finished running, headed directly to the subway, took the subway to the hotel, showered, packed and made it to the airport about 45 minutes before my flight. In 2009, I was quite simply freezing after finishing. I could think of nothing but getting inside and, due to nausea, drinking a Pepsi to settle my stomach. Yesterday, I finished, grabbed my gear from the gear check area, walked a bit, and then sat down by a Brooks Brothers store in downtown Boston. I spent about 90 minutes just enjoying the day, rubbing my sore feet, changing my shirt, and watching Boston walk by that store.
- Speaking of Pepsi, at mile 23 yesterday I stepped off the course to enter a 7-11, where I bought a Pepsi. My stomach was a bit upside down at that point in the race, but after a few sips of Pepsi, followed by a few burps, I felt much better.
- Speaking of my third Boston effort, in 2008 and 2009 when I turned on to Boylston for the last stretch to the finish line, the band started playing "Sweet Home Alabama." This year, it didn't happen for me. I am quite certain the band likely played its Skynyrd tune about 30 minutes prior to my arrival. They held up their end of the bargain, I just showed up late.
- The best part of the run for me was encountering two Army soldiers, dressed in full uniform, carrying 40-pound packs. I ran with and then passed the two soldiers while running up Heartbreak Hill. I learned later the soldiers were running to raise funds for the Wounded Warrior Project. I had a hard enough time running with my iPhone, much less the thought of carrying a 40-pound backpack.
- I mentioned in an earlier post that a number of runners traveling from Europe had their plans interrupted due to flight restrictions resulting from the volcano erupting in Iceland. While in the Boston airport Friday, I also overheard stories from several travelers about their efforts to return from trips to Europe. One man was describing how he drove the car he rented in The Netherlands to an airport in Spain, where he handed the keys to the rental agent and headed for a flight home. Another talked of a colleague who, "Was going to be there for a while."
- There is currently a finisher's medal from the 2010 Boston Marathon listed for sale on Ebay. While I don't endorse securing a medal in this manner, you can get in on the bidding for $17.50 at the present time. One catch, at least for the moment, is that only finishers of the race are permitted to bid.
- After a marathon, there are two "moments of truth," at least for me. The first arrives in the post-race shower when hot water and soap reveal any chafing, skin loss or missing body pieces. I passed yesterday's test with no extra pain or stinging. I use a product called SportShield, which has worked perfectly for me. The pre-packaged towelettes are easiest to use. The second moment of truth arrives when the alarm goes off the morning after the race, when I place my feet on the floor to step out of bed. I learn, at that moment, just how sore my legs, back, shoulders and neck will be for the next two days. I'm sore, but not too bad, given that the legs, back, shoulders and neck did not feel all that great last night.
Finally, some of you received an email from me last week, which included a statement that I had completed 42 marathons. I need to correct that statement. I had entered 42 marathons, completing 40. In the other two, I subscribed to Plan B. For the 2007 Country Music Marathon in Nashville, I stepped off at mile 20. It was hot, and while I was moving fine, the race course passed right by the VIP tent (which I was able to access), and I did not have the mental commitment to put the in the effort that day. There was an additional factor that guided my thinking that day. I was entered in a marathon in Denver three weeks later and, with Colorado being a new state for me to run a marathon, I did not want to mess up that opportunity by forcing my way to the Nashville finish. The other Plan B for a marathon finish also occurred in 2007 at the Space Coast Marathon. I had a some stomach issues prior to the start of that race, along with an early flight time and made the decision before starting to only run the half marathon course that day. It was a good decision, but I'll spare you the details.
So, my total number of marathons completed is now 41. Hopefully, that's not too disappointing for anyone.