This is really Lance's first experience with snow. He liked it!
Thursday, October 27, 2011
Thursday, September 08, 2011
2011 Ironman Louisville Race Report
 |
| How to pronounce this city's name? |
http://www.asiorders.com/view_user_event_video.asp?EVENTID=75726&BIB=2863&S=230&PWD=
What follows are my thoughts about my very first full Ironman race. On August 28, 2011, I successfully completed the Ironman Louisville triathlon. My overall time was 14:11:17. The full breakout of my times is below.
This was a well-run race on many levels. The race management
spared no detail. There were an abundance of aid stations on both the bike and
run courses, and they were well-staffed with helpful folks. There were a number
of port-a-johns available on the course (a lack of which I have taken issue
with in previous races, such as the 2010 Ironman 70.3 Taiwan).
 |
| The mighty Ohio, as seen from the official race hotel (transition area is at center, in the green grass field, and if you look very closely out in the river, you can see some of the buoys marking the swim course) |
The race course
Swim
There was certainly an “uphill” and a ”downhill” portion of
the swim. The uphill was going upriver against the current. Once we made the
turn past Towson Island and headed downstream, things got decidedly easier.
Nonetheless, this 2.4 mile swim was the longest I had ever done. Note to self:
train better for the swim next time.
Bike
 |
| IM Louisville bike course went northeast out of Louisville and made two laps before heading back into the city |
The 112 mile bike course consisted mostly of rolling hills
and flats. There was a variety of scenery, including horse pastures,
suburban-type dwellings, small towns, and rural highways.
Run
The marathon was on a very flat course running through downtown Louisville, past
the University of Louisville, Churchill Downs, and almost out to the airport
before heading back from whence it came. The course passed through one area
near downtown filled with historic homes and another ethnic area nearby. We had to make two loops of the course to make the total mileage of 26.2 miles.
 |
| Transition area, the day before the race |
Weather and Race Day Conditions
We were fully blessed this year with conditions far milder
than years past. People on the course were saying that last year it was 98
degrees with high humidity on race day. This year it got up into the mid-80’s
and the humidity seemed pretty comfortable to me, someone who lives in the dry
climate of Denver. We were lucky this year! There was a little bit of wind on
the bike course, but not enough to significantly degrade riding performance. We
may have Hurricane Irene to thank for the milder weather this year.
Race execution
I ran what I would consider to be an almost perfect race in
terms of my execution. I stayed within my abilities, remained patient, and kept
the long view necessary to complete the race. Before the race, I sketched out
what I thought my times would be:
0740 swim start (actual 0743)*
0940 swim complete (actual ~0922)
1000 begin bike (actual ~0930)
1800 bike complete (actual ~1650)
1815 begin run (actual ~1700)
~2315 race complete (actual ~2200)
Obviously, in making my estimates and having never run this
distance a race before, I consciously tried to err on the side of allowing a
little bit more time than I though each piece would actually take. I was almost
dead-on with my estimate for the marathon (5 hours predicted vs. 4 hrs 58 min actual).
Issues:
My GPS only lasted about 5 hours into the bike ride. I guess
if I were a faster cyclist, this wouldn’t have been a problem – just complete
the ride before the battery dies! But I knew that if I went faster than about
15 mph average on the bike, my chances of not blowing up on the run would be
significantly decreased. So, keeping within my abilities, I went slower than I
figured I really could. I have a hard time doing this unless I can located
another rider to pace off of. Note – this does not mean draft off of, I keep my
interval in keeping with the rules of the sport. I found a few “pacers” out
there – athlete 2620 during the first couple hours, a different chap toward the
end of the race. The only time I ran into an issue with keeping my pace
conservative was when I was on the part of the course where riders have to do
two laps of the same section. Here, there were faster riders already on their
second lap mixed in with folks like me who were taking it a bit easier on their
first lap. When I am surrounded by riders going faster, I just want to push
myself harder, too. It was hard to resist that urge, but thankfully once I
started my second lap, the faster riders were on their way to the finish and
the riders left on the course were by and large not as aggressive. This helped
me keep my pace. But back to the GPS: I made the mistake of staging it at the
transition area the day before the race. I should have known better than to do
this, for having used it quite a lot since acquiring it in 2007, I know that
best results are obtained when taking it directly off its charger immediately
before use. As it was, the device started to give me low battery warnings only
2.5 hours into the ride, though I was able to coax it on for another couple
hours before it gave up the goat.
 |
| IM Louisville bike graph |
The early demise of the GPS had implications for my ride and
for my run. Essentially, thereafter I had little means to determine how fast I
was going and the time of day. This is why it was doubly important for me to
find a “pacer” who I could use to keep my from going too fast towards the end
of the bike portion.
I think the lack of a GPS worked out well for me on the run.
This allowed me to just go by feel and not worry about what kind of pace I was
keeping mile by mile. Instead, from very early on in the run, I adopted a
run-walk strategy that entailed running several blocks (usually between 3-5,
but sometimes more), then walking a block or two, and repeating this over the
entire 26.2 mile course. As much as practical, I incorporated walking through
the aid stations into this regimen. I figure this ended up having me take
between two and three walk breaks per mile.
This run-walk strategy was also conducive towards favorable
gut conditions. In past long-course triathlons, I think I have tried to consume
too much on the run, and the sloshing effect made me have issues with cramping,
sideaches, and general gastrointestinal (GI) tract distress that is not
conducive towards timely event completion or an enjoyable race experience. This
time, I decided to only consume liquids and to sip them slowly while walking
through the aid stations. This would ensure that the nutrients made it into my
stomach and by not eating solids, I would avoid the associated delays in
gastric emptying that I think have caused me problems in the past on the run
segments of half Ironman races.
 |
| For those who made it to the end |
My go-to drinks were cola and chicken broth (the latter of
which I began to think of as a “liquid pretzel” from the yummy saltiness it
provided) alternated at aid stations along with a cup of water. I completely
avoided the sports drink offering on the run and ate no gels throughout the
entire race. In fact, the only solid foods I ate during the entire race were
one (1) powerbar (split into two halves), several bananas, and a few pretzels.
I drank a lot of sports drink on the bike portion (hence why I did not want to
drink any more of it once I got to the run, plus I think that the non-diluted
strength of the drink slows gastric emptying as well, which is not as much of a
problem on the bike as it is on the run), along with quite a bit of water. I also
dumped quite a few bottles of water over my head and on my jersey and shorts to
help keep cool on the bike.
To combat heat on the run, sponges soaked in ice water and
ice cubes were available. A few times I dumped some ice into my hat and put it
back on my head, but most of the time that ended up being too cold for my
scalp. I liked better to grab 2-3 sponges and put one in my hat and use the
others to squeeze cold water onto my shirt.
 |
| Public art in Louisville |
The bike ride twice passed through the town of LaGrange.
Riding down the main road lined with spectators yelling and cheering was cool –
it felt like I was in the Tour de France! Naturally, I was
hammering through this portion of the ride both times.
On the swim, I had a hard time sighting the buoys used to
mark the swim course. This was due to two problems: fogged up goggles and
scratched up lenses on said goggles. (Not to mention that I am nearsighted.) I
had to stop numerous times to get my bearings, slowing my time.
What would I change about the race? I would have prepared
better. The race program from the Ironman lists various stats associated with
the “average” Ironman athlete. Age-wise, I am pretty much dead on (average age:
37), but with respect to the average training distances claimed, I am lacking.
For instance, according to the race program, the average Ironman athlete swims
7 miles each week, bikes 225, and runs 48. My averages are way, way below all
of those. So certainly I could benefit from greater training volume.
I would also like to have at least one “support human” at
the race. It would have been nice to have someone I knew at the finish line
(though I was well-taken care of by the volunteers there). It was also a bit of
a hassle to have to go get my bike and gear from the transition area after
finishing the race (a support human could have done that for me).
What’s next? I know that I certainly want to continue to run
triathlons, though it is possible that I may stick to the half Ironman and
below level. I’ll have to wait a couple weeks to see what I think for sure. I
definitely want to take advantage of the various events offered out in
Colorado.
 |
| These are made in Louisville |
All in all, Ironman Louisville 2011 was a fantastic
experience and I commend the race organizers and all the volunteers who made it
happen! I am also happy that my first Ironman experience ended up taking place
in the U.S. – while the novelty of running Ironman China would be great (as I
had planned to do in May of this year before the race was cancelled), I have a
feeling that the race organization would have been lacking and it would have
been a much less fulfilling experience. Ironman Louisville was the culmination
of 10 years of racing and training for me and I look forward to seeing where I
go in the future.
 |
| One of Louisville's sister cities is Jiujiang, People's Republic of China |
*IM Louisville's swim is unique as that it is a time-trial start, as opposed to mass or wave starts at virtually all other races. What this means is that instead of having all members of an age group (for instance, males aged 35-39 yrs) start the swim together (a wave start), as is fairly standard at many triathlons worldwide, at IM Louisville each athlete jumped into the river singly in succession (OK, actually there were two lines to make it go a bit faster), which explains why even though the race actually began at 7:00 AM, I did not enter the water until nearly 45 minutes later. Luckily, the 2 hour 20 minute swim cut-off did not start until the last athlete entered the muddy waters of the Ohio River (which was much more pleasant to swim in than I had feared it might be. It was a comfortable temperature and it did not smell of sewage, unlike the previous triathlon which I swam in a river for.).
Thursday, July 14, 2011
Colorado Hike #1: Stanley Mountain
Inspiration hit me yesterday when I saw a post on Facebook by Visit Denver, the official travel and visitor bureau for the city (the Facebook post is at http://www.facebook.com/media/set/?set=a.10150243642020777.321503.178754795776, or you can swing by their website at http://www.denver.org/) talking about Stanley Peak being an easy hike only a little over an hour away from the city. I didn't have to go into work today - I was going for a hike!
After stopping off for a power breakfast at my favorite place for donuts, I was off. The directions posted on Facebook were right on and I was happy to see the overcast skies over Denver melt away to scattered puffy white clouds by the time I was heading up into the Rockies on Interstate 70.
The trailhead was located adjacent to the Henderson Mine, which is the world's largest primary producer of molybdenum. Molybdenum is essential for the production of high-strength steel alloys.
According to internet resources, there is a 15-mile elevated conveyor belt that carries the molybdenum ore from the Henderson mine to the ore processing site. The conveyor is both underground (passing beneath the Continental Divide through an old train tunnel) and above ground, though I did not see it today.
Just above is a view of the mine from near the summit of Stanley Peak. The mining operation's noise was audible during virtually the entirety of the hike I did today.
The trailhead was at an elevation of about 10,500 feet. I knew that the summit of Stanley Mountain was in excess of 12,000 feet, so a fair amount of climbing lay ahead of me.
The area still has a fair amount of snow in it for mid-July. Snowmelt runoff creeks were a common feature that I had to traverse from time to time as I made my way up the easily-followed trail. There were several points below the timber line where I had to make my way across snow drifts that covered the trail. (below)
The sounds of wildlife were all around, but I saw only a few animals - a squirrel and several birds. And bugs. I saw deer hoof prints and also what I thought appeared to be a pawprint of a dog or perhaps a mountain lion. (I didn't get a photo of this latter item, since I saw it soon after I started up the trail and didn't want to stop so soon to snap a pic. I figured I would be able to find it again when I was on the way down to take a picture of it - fat chance!)
About 1.25 miles into the hike there was a fork in the trail. (Pictured above - also note the audio clip I recorded at this point.) Luckily I was pre-briefed on which way I needed to go. I have to take issue with the "1 mile" distance to the peak from this point. My GPS begs to differ - it was probably at least double that. Perhaps 1 mile is as the crow flies, not counting the switchbacks and so forth that are part of the trail. I took a short break here. There were rushing streams of cold snowmelt not far away that provided a nice backdrop.
After that, I only made brief stops for photos or to make gear changes (add/remove clothing as the temperature dropped or climbed)
While termed "easy" by the Denver tourism folks, I was working quite hard at points to make the ascent. I don't think I would bring my kids out here to go up this trail - too steep and too long for them. It's not a technical climb at any point, but it does require a decent amount of conditioning to make it up (altitude acclimatization also helps - still a work in progress for me).
I was really happy with the hike. I wasn't sure how long it was when I started, and the approximately 7 mile round-trip was enough for me today. Look for more hikes in the near future.
Monday, July 11, 2011
Saturday, July 02, 2011
Thursday, June 30, 2011
Wednesday, June 29, 2011
Denver
I first was able to see the Rocky Mountains about 60 miles from Denver. When I got into town the evening rush traffic was just starting to pile up.
Monday, June 27, 2011
Sunday, June 26, 2011
Friday, June 24, 2011
Thursday, June 23, 2011
Tuesday, June 21, 2011
Friday, June 17, 2011
Thursday, June 09, 2011
For those of you who are really bored on Saturday (or Friday)...
...you can watch my graduation live on the internet. Here's the link:
http://weblive.nsysu.edu.tw/graduation.htm
The shindig goes at 1:30PM Taiwan time on Saturday, June 11. You will have to do the time conversion yourself for wherever you are reading this at, but for folks in the central United States, that's pretty much in the middle of the night. So, if you find yourself with a case of insomnia on Friday night, tune in to the above, it will probably put you right out!
Oddly, I am doing this graduation thing on Saturday even though a big piece of the puzzle is still missing - my thesis defense will take place on Monday afternoon. Here's to hoping that goes well!
GJS
http://weblive.nsysu.edu.tw/graduation.htm
The shindig goes at 1:30PM Taiwan time on Saturday, June 11. You will have to do the time conversion yourself for wherever you are reading this at, but for folks in the central United States, that's pretty much in the middle of the night. So, if you find yourself with a case of insomnia on Friday night, tune in to the above, it will probably put you right out!
Oddly, I am doing this graduation thing on Saturday even though a big piece of the puzzle is still missing - my thesis defense will take place on Monday afternoon. Here's to hoping that goes well!
GJS
Thursday, June 02, 2011
Things our 14-month old can say
 |
| Leafy green! |
air poop
up
all done
more
Mama
Dada
milk (hand sign)
brother
open
thank you
again
poop
diaper
謝謝 (xiexie; thank you)
ball
yes
go
爸爸 (baba; Daddy)
on
魚 (yu; fish)
hello
ding!
yuck
peepee
apple
baby
hot
幫忙 (bangmang; help)
let's play
armpit
did it!
I wonder what he will come up with next?
GJS
Coming out of "The Desert"
 |
| Whoah - get down! Be careful if you see this guy in the area waving assault rifles around. (Psst! He's not qualified with that weapon!) |
Lack of posting over the past few months can be attributed to a few things. First, my thesis, which I completed about 2 weeks ago, consumed most of my time from April onward. Plus, now that we are so close to heading home, the motivation to post waned. It will probably wax again sometime in the future - stay tuned.
GJS
Subscribe to:
Posts (Atom)