Monday, June 30, 2014

[RACE BRIEF] Chasing PR's: The Stars & Stripes 5k

I want to start somewhat a new format for my race reports (and race briefs, as it were). For those also competing in the race, this should give opportunity to become familiar with previewing the course (and in some instances, the registration process). As I get around to each section, I will post updates until the complete race report is finished.

So, for example, for this first post, I've checked out the route maps and previewed the elevation profile, wrote up my course preview bit, and went ahead and posted it. Once the race is finished, I'll turn this post in to a full race report.

With that said, let's check out the Stars and Stripes 5k...
____________

Stars and Stripes 5k Home Page HERE

I'm still shooting for my 6:30 PR, not to mention the ever-elusive sub-20-minute 5k.

This year's route, with final climb highlighted
(Image courtesy of Google Earth)
(TrainingPeaks course profile HERE)
The 2014 route starts and finishes at Summit Fair Shopping Center in Lee's Summit, Missouri. It includes three major climbs and one mini-climb.The one mini-climb starts right off the line, though is quickly followed by a long descent (that we will climb back up nearing the finish line). The first real climb comes right after the long drop, about 1k in to the race, running about 500 meters at 2.6%. Climb 2 hits at just after the halfway point, with a quarter-mile uphill at 2.7%. The biggest climb of the day will come right at the finish, though, as runners are rounding the north side of the shopping center, and lasts nearly a half-mile, but only at 3% average.

The packet pick-up was at the race site, at the Summit Fair Shopping Center. Given the distance from my hometown, and the busy-ness of July 3rd, I had a friend pick up the packets for me, so I didn't get a chance to check out the conditions of packet pick-up. Weather reports forecast gorgeous conditions for race morning: upper 60's and middle-humidity with a light breeze, so no concerns there.

The quiet start line, about one hour before the start.
The crowds quickly grew to a reported 1,000 participants, not including the spectators and the kids readying themselves for the Lil' Firecracker Fun Run that would follow the 5k. Easily-noticed was the number of individuals that appeared to be here to really compete. Of course, I still wanted to place, but my focus would be on chasing my 6:33 PR. Lining up at the start line, I made sure to stay back from the front of the pack, so as not to get trampled.

We were off just after 7:30am. The first half-mile was incredibly quick, with all runners jockeying for an aggressive position. Four immediately pushed off the front, a smaller group on their heels. I wasn't in that group. I posted a 5:52/mi first half-mile pace, rounding out the first full mile at 6:11. I was where I wanted to be pace-wise, so despite hanging around at 30 back from the front, I would just sit in and push my own pace. No placing today, it would seem.

Of note, on my course preview, I noticed a nasty looking hill that gave a steep descent at the start, and painful-looking ascent near the finish. On-course, this hill was nonexistent -- maybe a fault in the mapping elevations? Where the effort really existed was midway, just around the 2-mile mark (and where I start to fade). Either way, the course was much flatter than expected -- a nice surprise.

Line crossed. (Photo courtesy of KC Running Company)
My watch rang "behind virtual partner" just after the 2-mile marker. I pushed as often as I could and as hard as I could (which wasn't often or hard). I ran around the back side of the shopping center, ticking off the 3-mile mark, just under 6:40/mi average. I rounded the corner on to the finishing straight, and saw sub-20-minute time up on the clock. If only I were that much closer, but I was still nearly a full tenth of a mile away. Pushing the final straight, 20 minutes came and went. I crossed at 20:34. A 6:38/mi, just off PR. Good enough for 7th in age-group, and 36th overall out of nearly 1,000 participants. The hunt for 6:33/mi (and the hunt for sub-20) continues.

Finishing goodies.

Race Metrics
Distance: 3.10mi                    Time: 20:34
Avg Pace: 6:38/mi                  Max Pace: 5:52/mi
Avg Cad.: 168spm                  Max Cad.: 190spm
Avg VO: 11.4cm                     Avg GCT: 238ms
Avg Stride Length: 1.44m
Avg HR: 178bpm                    Max HR: 188bpm
Kcal: 366kcal                         Tot Climb: +105ft
Splits (mi): 6:11, 6:49, 6:59, [0:34]
Placing: 7th of 38 in age-group, 36th of 964 overall
Weather: 69F/67%hum/Sunny/SE5
Training Peaks Race Profile: HERE

Monday, June 23, 2014

[RACE REPORT] Tour of Kansas City New Longview Criterium


LONGVIEW FARMS, Missouri -- Though I'm still terrified enough to miss my former favorite Tour of Lawrence this year, I at least want to earn as many KBAT points for my cycling team this year (and some KBAR points as well). After having a half-decent result for the Jesse Blancarte 10k TT in Gardner, Kansas a few weeks back, I decided to register for at least the KBAR/KBAT-points-earning Tour of KC New Longview Criterium. This would be my very first criterium race since The Accident last year. While I was at it, I figured I'd grab the night before's New Longview Street Sprints as well. Though not a points-earning event, it still should prove some fun (and safe) experience. I would skip the non-KBAR/KBAT-points-earning third day of the Tour of KC, the Cliff Drive Circuit Race. I wasn't familiar with the course, and wanted to eliminate any and all risk from an already-busy race calendar.

About the Tour of KC


Screen shot of this year's race flyer (click HERE for
full race flyer in PDF form).
The Tour of KC has been in commission for a while, although over the past decade, it's had its fair share of trials and tribulations. The Tour of KC was actually one of my first criterium experiences, and two of the three days used to be held at a police academy in Raytown on their driving practice course. On the outside, it seemed like the Tour of KC was in jeopardy: registration seemed thin, as did sponsors (although, I cannot surmise as to the actual state of the Tour of KC). The last two years have seen a resurgence of the Tour, though. Registrations are back, sponsorship is up, and the format has found its style.

Similar to the Tour of Lawrence, the Tour of KC now hosts a Friday night street sprints competition at New Longview (just east of Longview Lake) in Missouri (formerly, "Race A" of the Police Academy race was held on Friday night, and "Race B" of the Police Academy race was Saturday morning). Saturday is the New Longview criterium, a criterium that has been in the Tour of KC lineup it seems since always. Finally, Sunday is the Cliff Drive Circuit Race, which, last year, was actually held on Friday night, and only to Cat. 4 riders and above. Formerly there was a downtown Lee's Summit criterium on Sunday, which has been stripped from the schedule.

In addition to the three races, the Tour of KC now features Kansas City's first true Grand Fondo, which for the unfamiliar, is a timed long-distance ride. It's generally considered non-competitive, but given formal timing, it attracts riders from all levels. Also held in conjunction to the Tour of KC is the Kansas City Real Ale Festival, which will no doubt attract additional spectators of all events. Lots of change over the years, but the Tour is back and (again, it seems) stronger than ever.

About Criteriums...

I may have explained in a past post, but in case it's missed, there are several different types of races in cycling. Here's a quick run-through...

*Road Race: What you typically think of when you think of bike racing. A-to-B (or long, one-lap loops) racing of long distances, usually more than 40-50 miles, though the pros often see 100-150 miles. Team tactics are key. Usually you have multiple teammates riding together to help take one teammate to the finish line. There are often a mix of road race types, such as the Mountain Stage, which is best suited for climbers, and the Sprinter's Stage, which is best suited for last-minute sprints to the line. Energy savings is also a big key in this one, which is why you'll often see huge pelotons (or large groups of cyclists riding together), whereby riders draft off of each other to avoid losing energy to the wind.
*Individual Time Trial (or "ITT" or simply "TT"): My favorite. This is a long solo effort. No teammates around you. Just you against the clock. Generally A-to-B or out-and-back courses, though that isn't necessarily always true. You must race a specific distance, and are given a time as you cross the line. You are ranked by your time against your rivals. Everyone starts and finishes alone.
*Circuit Race: Similar to the criterium (see below), but the course is generally longer in length (about 3 or more miles). At least, that's about all the difference I can figure out. But even then longer courses of 20 or so miles will be referred to criteriums in the pro rankings. So I suppose I have no clue what the difference is.
*Stage Race: Any combination of any (or all) of the above, strung together in to a few consecutive days (such as a weekend, like the Sunflower State Games, Tour of Lawrence, or Tour of KC), or 7/8 consecutive days (over a whole week, such as the Tour of California), or even 21 days (called a "Grand Tour," such as the Tour de France -- usually has two or three rest days sprinked throughout). For shorter distance stage races, points are sometimes given depending on finishing place (for ex., 8 points to first place in the first race, and 7 points for 2nd place, and so on), and the winner of the stage race has the most points. For longer races, this format is replaced by finishing time.

Finally, you have this report's race: the criterium. Criteriums are by far the most intense of all cycling events. This involves multiple laps around a short (usually 1-mile or so) course. Criteriums are always classified by how long the race will go time-wise, plus a few additional "finishing laps." During higher-category criteriums, "primes" (pronounced preems) are established on specific laps during the race. So, for example, the first rider to cross the line on lap three will "win the prime," which usually comes in the form of a cash prize. Some riders will shoot for winning a prime, then move back and help out a better-endurance teammate to take the overall win.

As noted, the length of a criterium race is time-plus-distance-based. So, for example, the Tour of KC New Longview Category 4 criterium (the one I registered for) is a 50min criterium. That means the race will go for 50 minutes of racing (no matter how many laps). At the start of the race, race organizers will determine the number of finishing laps (usually 2 or 3), and once the pre-determined 50 minutes is up, racers will then race the final 2 or 3 laps. Sometimes these races are referred to by their time and distance, such as "50+3," or "50 minutes plus 3 laps." Sometime criteriums will just be classified by just the number of laps, but the "time+laps" format is most common. For my registered race, we would race 50 minutes. Once 50 minutes has passed, we would then start our finishing laps (again, likely an additional 2 or 3 laps).

The majority of the 50 minutes of my race would likely involve just staying with the lead pack and staying out of trouble (wrecks are really common during criteriums). Some riders would likely "attack" (or sprint ahead of the group and try to win on their own), but more often then not (especially during a long 50 minute race), the larger group would catch all attacking riders. Approaching the end of the 50 minutes, teams will start to organize together, with teammates "leading out" (or just leading) one or two of their fellow riders that are good last-minute sprinters.

Once racers start their finishing laps, the real race is on. Speed is ridiculously high, and you almost always see a crash due to the tight course and high speeds. Attacks happen often as riders try to take the finish line on their own. On the last lap just short of the finish, many riders will sprint to the line. You'll often see more sprinters for criteriums than you will for road races, which also ups the danger factor.

New Longview Criterium Course Preview

Again, I decided against the third-day Cliff Drive Circuit Race: it doesn't provide any KBAR/KBAT points opportunities, and other than running it during the KC Track Club's Cliff Drive 8k, I had no experience racing the course. Given that this would be my first criterium in almost a year (in fact, coming up on the year anniversary of my nasty accident at the Tour of Lawrence last year), I stuck with just the New Longview Criterium -- a course I had raced several times in the past.
The Tour of KC New Longview Criterium course, with the first of two significant climbs highlighted.
(Image courtesy of Google Earth; see TrainingPeaks course profile HERE)
If history repeats itself, this specific criterium would splinter the pack (break the larger group up in to many smaller groups and solo efforts). Though the distance of the course isn't much longer than the typical criterium, the amount of elevation change is definitely remarkable. The start line begins at the highest point of the course and heads north downhill on SW Longview Road. The descent is significant enough that forces some strong breaking in to the first left turn on SW Longview (road changes direction, name stays). Wrecks at this intersection are common. Three quick right-hand turns through the small neighborhoods of New Longview shoot you back on to the northern trek towards the start line.

This is where the first major climb comes in, and after only a few laps, starts to break up the pack in to tiny pieces. The first of two climbs is a quarter mile up a 2.7% grade that shreds the legs. At the top of the hill, a left-hand turn at Kessler takes riders back down in to a Metropolitan Community College perimeter road. At the end of this road is the second very-short-very-steep climb (about 6% grade) back on on to SW Longview Road headed for the finish line.

The course overall is about 1 and a quarter miles. Though it's never easy to predict speeds for criteriums, my guess would be a 23mph average over the 50+3 (or +2) race would result in about 18 or 19 laps. Previous years, racing Category 5 was 30+2, and I remember being absolutely shot afterward. This year would, in a faster and longer category, be very interesting.

Pre-Race

Weather forecast would be similar to it was in 2013: hot and humid, with temperatures around 91, and heat indexes in the upper 90's. On the roads, this would likely be closer to mid- to upper-90's for the actual, and above 100 for the heat index (blacktop does that). This would mean dehydration, sticky brakes and slippery road tar.

Besides the weather, I was pulling double-duty on race day, with a 5k slated for early morning, and then the criterium start time at 3:15am. That gave me about 4 hours worth of rest before it was time to start warming up for the Tour of KC. Not the most ideal situation. Post-5k, my quads were pretty trashed. Not only from the 5k, but from the hard training I had that week. I did all I could to intake fluids, including electrolytes, protein and, of course, cherry juice. Then, I slept as much as possible (which wasn't much) between the 5k finish line and the Tour of KC start line.

I arrived at New Longview about 90 minutes ahead of start time. My legs felt reasonably well. An hour short of start time, I grabbed a quick 6-mile warmup around the area. What few climbs there were, that's where my legs started to show their fatigue -- in spades. My lactate threshold was significantly lower on efforts. And, given the elevation challenges of the course, a lower threshold spelled death. I grabbed my bib number, and sat in the car a few moments in the A/C before it was time for course-recon. With any luck, the toxins would clear after my warmup, and I'd be better-suited for the course come start time.

Fifteen minutes before start and the Category 5's were finished. Time for a few laps of course recon. It didn't
The packed start line for the Cat. 4 race.
take long before I started remembering the course specifics: every street fissure, every uneven pavement, every pothole. Two laps, and we were called for staging.

Race Day

I was one of the first to approach the line for Category 4 staging. Riders poured in around me. I took a small step back from the start line -- I didn't want to be pressured against the front of the pack on my first criterium back in almost a whole year. The riders kept coming...one by one...five by five... This was by far the largest group of the day. And on a course as narrow as this, that meant a fair amount of risk. My anxiety spiked. In the past, I've been able to hang on to the back of the pack and finish with the group. Maybe I could do that this time. At this point, KBAR/KBAT points aside, all I wanted to do was finish and have fun doing it. Roll call, all 42 riders accounted for, and it was time to go.

Bombing in to corner one, teammate on my
wheel. (Photo courtesy of Dan Reuttimann)
The horn sounded, and riders immediately sprinted out in front of the group. A break of four ended up staying away, while the rest of the group charged hard out off the line. Speed was extremely high -- almost 27mph average and above. It wasn't even a full lap before two riders ahead of me began to slow. Was the pack slowing too? No. I was getting caught out behind a select few riders that were already losing ground. I sprinted around them, one-by-one, until I latched on to the last of the main group, just in time for the end of lap 1.

Down the hill in to turn one, the group was already charging ahead. Another dropped back, and I sprinted around him, attempting to latch on again. It wasn't until the first real climb that I was able to attach back on. Up climb two, another fell back. On to the main straight, finishing lap 2, I was back on the group. The whole back was stretched out in single-file; the pace was ridiculously high, and everyone was struggling to find some semblance.

Still in somewhat a group on Climb 1, but
already the group was falling apart (Photo
courtesy of Dan Reuttimann)
A few more dropped on lap 3, and I was just back from the group. Finishing lap 3, I looked ahead: I was no longer in the lead group. The race had broken into two main packs, and I was in the trailing pack -- and was struggling to even keep up with them. I was caught out on my own in the wind. I had to somehow figure out how to get back up there. My heart rate was maxed out, and my legs seared with pain.

Two riders dropped back a bit from the second group. They seemed to be working well together, trading time in to the wind. If I could encourage them on, perhaps we could ride back up to the pack. I grabbed hold, took a few breaths, then took my turn riding in the wind. A quarter mile of leading them out, I pulled off to let the next rider through, but no one came. They both fell back, each now on their own -- including myself.

Several laps in, still attempting to grab
a few riders on my way back to the
second group (Photo courtesy of Dan
Reuttimann)
As I started lap 4 -- alone -- the second group was at least 200m ahead. I tried my best to keep my head down and my my body as small as possible. I kept my eyes focused on the road beneath my wheels, looking up only 50m ahead of me. I had to push. Each pedal stroke up climbs 1 and 2 were absolute agony. Cresting the hill on to the front straight, I looked ahead past the start banner. I hadn't gained any ground, despite passing two more that had detached from the group. This was a war of attrition, and I was losing.

I tried again for the first half of lap 5. Upping the first hill, I could no longer see the group. I was done. I had zero energy left in me. The heat was causing me to lose focus, and my legs were running on fumes. I went in to time trial mode. Now it was no longer a matter of how I should finish; now it was a matter of when I was going to get lapped -- and subsequently pulled from the race.

I'm calling it here. Lap 7. Done.
My speeds began to plummet for lap six. I thought about dropping out as I crossed the start/finish line.
Looking up at the time clock, only 21 minutes had passed. 21 MINUTES!!! I wasn't even halfway finished with the race -- I still had to suffer an additional half hour, plus two laps before the race was over. I felt so defeated. Halfway up Climb 1, I could see the lead group behind me. I would soon be passed -- if not on the next climb, at least on the next lap. I didn't want to get called out by the officials -- this would be it for me. I suffered the second climb on to the front straight, pulled off, and signaled to the race officials: three swipes with my hand across the throat. The universal sign for "stick a fork in me, I'm done."

Completely. And totally. Cashed.
(Photo courtesy of Dan Reuttimann)
So what is there to learn from such an experience? For one, I hadn't trained specifically for criteriums since May of 2013. In 2012 and 2013, both March and July both marked pinnacles for area criterium racing season. On my race calendar, I attended all of the major events, training very specifically for each. Criteriums require a very specific type of training regimen -- one I had not followed at all this year. For 2014, this would (likely)
be my only criterium. March was half-marathon season, and the summer included a string of 5k's, time trials, and multisport events, which were essentially 5k's with time trials combined. Nowhere did I have space for criteriums, neither in training nor in racing.

Lining up for the Jazz in the Woods 5k, only
6 hours before I would toe the line at the Tour of KC.
(Photo courtesy of Artistic Expressions)
The second thing I learned? Though two-a-days are a great training plan, they don't translate well in to racing. Two 5k's or a 5k and a 10k or a 5k and a time trial are possible, for sure. But a 5k and a criterium are not at all compatible with each other. Never again would I try such a feat.

I will in all likeliness be back for 2015 for the Tour of KC. I love the event, am comfortable (relatively) with the course and format, and it is a great way to get my criterium fix, not to mention hopefully earn my team some points in the process. I'll just make sure to not run a 5k the same day...

Race Metrics
Distance: 8.58mi (7laps)           Time: 24:57
Avg. Speed: 20.6mph                Max. Speed: 29.5mph
Tot.Climb.: 340ft                      Kcal: 378kcal
Avg. HR: 170bpm                     Max. HR: 181bpm
Avg. Cad.: 93rpm                     Max. Cad.: 125rpm
Weather: 91F(HI96)/64%/Sunny/S10
Placing: DNF (0 points KBAR/KBAT)
TrainingPeaks Event Profile: HERE

Keep R/B/S-ing. -tds
~~__o
  _-/<,_
@/   @

Friday, June 20, 2014

[ARTICLE] The 3 Basic Run Workout Types for Mid-Distance Training

Every runner hits a plateau (or, more accurate, multiple plateaus). Be it with their 5k speed, losing weight, building endurance...whatever. It happens. Hitting a plateau requires a shake-up in training; your body has simply become too "used" to your current training regimen.

I have hit a plateau. My mid-distance times have stopped improving, and I'm consistently running just below PR-pace (6:30 PR for a 5k, 7:23 for a 10k). Though I recently came close to breaking my 10k PR, I need a shake-up in my running routine. This comes in the form of implementing (or changing) the types of running workouts you do each week. So, for example, when I first started running races, I hit my 8:30 PR plateau (which, apparently, is a common first-plateau for newbie runners). In training, all I was ever really doing is running often, and once or twice a week running as fast as I could over a 5k or 10k distance -- whatever I was training for at the time.

Then I read about interval training. I incorporated it in to my weekly regimen, and BAM! [insert Emril impression here] 5k Times plummeted all the way to 7:30, 7:15, sub-7 (which is another common plateau), and finally resting at 6:30. 10k's continuously improved as well, to the point where I ran 6 straight 10k's setting a PR, until finally hitting 7:23. Training for my half-marathon (aka adding Sunday long runs) also helped, I'd presume. This is where I stand now.

Time for another shake-up. In the coming weeks, I would be changing my regular intervals, adding fartleks, and focusing on tempo runs -- the three most common types of running workouts. So, to add to the running training section of my Interesting Articles page, I figured I'd run through each of these simple types of running workouts, explaining what each is, and how it helps with running form and fitness.

Intervals
     What it is...
The first real structured workout I implemented, the interval workout is exactly how it sounds. Pick an interval. It can be an interval of any type and length: 1/2-mile intervals, 4-minute intervals, 1-mile intervals...etc etc. The goal, however, is to pick a length, and run it above threshold pace. As in...bomb the shit out of that interval (the "max effort interval"). Then, once the interval is up, you run the same length (time or distance) at recovery pace or lower (the "rest period" or "rest interval"). Sometimes the rest interval is longer than the maximum effort interval, but I like to keep it the same. Then, simply string a number of these intervals (with rests) together.

ALWAYS start and end an intervals workout at recovery pace. The opening recovery pace interval serves as a warm-up for your first hard effort, and the closing recovery pace interval serves as a cool-down to avoid muscles tightening and improving recovery. If any, the only intervals that will differ in distance from the hard efforts will be my warm-up and cool-down periods. One of my favorite intervals looks like this...

>5mi Intervals Session (1mi WU + 4x.5mi Interval w. .5 Rest bw + CD)
*1mi warm-up building from recovery pace to half-marathon pace
*1/2 mile Interval at over 5k pace
*1/2 mile Rest at recovery pace
*1/2 mile Interval at over 5k pace
*1/2 mile Rest at recovery pace
*1/2 mile Interval at over 5k pace
*1/2 mile Rest at recovery pace
*1/2 mile Interval at over 5k pace
*1/2 mile (sometimes more) cool-down at recovery pace

If my Intervals only cover 5k instead of 5mi, I'll shorten the warm-up to only a half-mile. Sometimes, if I'm feeling crazy enough, I'll increase the hard efforts to 1 mile long, leaving the rest periods at still 1/2-mile (which you're not really supposed to do, but oh well). As you improve your paces during the hard effort intervals, increase the distance.

     How it helps...
Intervals are great for building what are called "fast-twitch muscles." These are the muscles primarily used during short- and middle-distance races. Not only does it help build these muscles' strength, but their endurance as well -- so you are both improving your speed as well as improving how long you can hold that speed. Beyond muscular gains, aerobic gains are a primary focus of interval sessions. Again, similar to your leg and core muscles (and without getting in to aerobic/anaerobic thresholds and what-not), you are improving the amount of oxygen that is transported to you muscles, as well as the length of time that you can hold this sustained maximum aerobic effort.

Finally, and often overlooked, the psychological gains. Anyone who has ever done interval training -- regardless of the sport -- knows that your body screams at you midway through each hard effort. Your mind wants to comply with these body signals, to the point where you are counting ever second or ever hundredth of a mile until the interval is over. Thus, regularly doing intervals in your running regimen trains your brain to toughen your way through these periods of intense physical discomfort. Where a better place to have an edge in a race than to be able to deal with physical misery of the later miles?

Fartlek
     What it is...
When I first heard the name, I figured it was a joke for "a small flatulence release that adds thrust, thereby increasing pace." Then I read in to it further, and as it turns out, it's just a foreign (Swedish) word meaning "speed play."

Fartlek workouts are similar to intervals with one main distinction: there are no set intervals. Instead of picking 1/2 miles, you basically pick a landmark to use as your "finish line" for the interval. So, say, if you have a favorite route that runs about 5k, you're likely familiar with all the various landmarks that pock the route (a street lamp, a tree, a crosswalk sign, etc). Run at below threshold pace, and when you feel you have the edge, start a hard effort. As your legs fatigue mid-effort, find a landmark up the road, and sustain the best you can to the landmark. Then rest, and repeat. Again, start and end on easy efforts for warm-up and cool-downs.

     How it helps...
Again, also like interval workouts, the physical benefits of fartlek sessions are essentially the same, with one exception: muscle confusion. I know it's a phrase that's often misused and misunderstood, but without a larger debate... By constantly mixing up the distances and/or times of your hard efforts, you are avoiding training your muscles for only 1/2- or 1-mile hard efforts, and avoiding training your muscles to expect recovery efforts. Basically, you're training your muscles to "be ready for anything."

Psychologically, I've always found that -- especially in the late-mile intervals during a fartlek session -- running towards a landmark helps in visualizing the finish line. Running any distance race always comes with those final moments of absolute agony as you eye the finish line off in the distance. Fartlek sessions will make those closing meters not feel so miserable (or, at least, help you toughen them out better).

Tempo
     What it is...
I'm going to borrow from the Runner's World magazine article I first learned about tempo runs: Imagine an Oreo cookie. You have you two thin cookies, and sandwiched between you have the oh-so-sinful creme filling. A tempo run is like the Oreo, with the cookies being warm-up/cool-down runs, and the creme filling being a pace just at or above threshold (so you should be huffing and puffing, but still able to hold the pace for almost an hour if forced). I more imagine it like a race at somewhere between my 10k and 15k paces, but with no break between the warm-up and cool-down. The distance you run during tempo runs will up as your endurance improves, but you can pretty much choose any distance, so long as you don't over-do it (most tempos should be kept to under an hour for the "creme," and about 15-20 minute for the "cookies"). It's really the pace that is the focus of this run, though. So, for example, a common tempo run for me is my 7-mile (and I added my current paces for each):

7-mile Tempo Run
*1 mile recovery pace (9:30-8:30)
*1 mile half-marathon pace (8:30-8:00)
*4 miles 10-15k Pace (7:15-8:00)
*1 mile half-marathon pace
*1 mile recovery pace

Honestly, sometimes I'll lengthen my 2nd half-marathon pace mile to about 1.5mi, and only do a half mile at recovery pace during my 7-miler. And if I increase distance (a 15k tempo run is another favorite of mine -- about 9 miles), I increase the distances of the 1st and 2nd half-marathon pace intervals (because, technically, I'm coming out of 10k-15k pace zone for mileage anyways, and approaching half-marathon paces). I will never go beyond 15k for a tempo run. Beyond that (at least for me, for now) is a long run.

     How it helps...
Improved aerobic capacity and increased lactate threshold (lactate threshold is the effort/pace at which your legs start to get that burning feeling). This is great for training in all distances, but that increased lactate threshold is especially helpful during middle-distance races. You will find the pace at which you hit lactate threshold will slowly start to fall with more tempo workouts, which means your overall finishing times for those middle-distance races will improve as well. And the final recovery-pace mile(s) will help stave off any painful muscles post-run and improve recovery times.


So that's how I best-understand these three types of running workouts. These are the ones best suited if you're looking to beat any plateau, and especially if you're looking to boost your 5k, 8k, 10k and 15k times. Now get out and run!

-tds

Monday, June 16, 2014

[RACE BRIEF] Chasing PR's: Village Shalom Father's Day 10k

Every once and a while I do a race that doesn't necessarily require a full-on race report. These are usually non-targeted races or "tune-up" races on my schedule. However, they're still worth a solid mention, especially for anyone interested in signing up and wanting more information. This will be my first of many "Race Brief" reports, this one for Village Shalom's Father's Day 10k

Note: All in-race photography was generously provided by Mile90 Photography. Check'em out!

OVERLAND PARK, Kansas -- I came off the Hospital Hill 10k quite disappointed. For 2013, I posted five straight PR's on 10k races (including Hospital Hill). My first 10k race of 2014 I narrowly missed a PR. Despite half-marathon training and intervals training since, this year's Hospital Hill was far behind my hoped- and expected-upon pace. That said, Hospital Hill is no easy feat. And with this year's weather conditions, I wanted to give myself a "tester race" to see if I truly am working backwards (which would likely require a solid off-period from running). As a supporter of Village Shalom in Overland Park anyways, their annual father's day run was offering a 10k. I figured it the perfect opportunity and signed up two days after HH.

The Father's Day 10k is a double-loop of the 5k route option. I've done several 5k's in the immediate area, so was going in to this one familiar with the profile. There are a surprising number of steep climbs around there.

The 10k course, with elevation profile.
(Image courtesy of TrainingPeaks)

Seems like this week's 10k would be the perfect follow-up to hospital hill. Approaching race day, we had a nearly 70% chance of thundershowers. I woke up at 4am of race day to loud thunder and crazy winds.

Forecast two days before race day. Rain again.
(Image courtesy of NOAA)
I decided to bring along a kitchen tall trash bag with holes cut for my arms and head. I would no doubt have to stand in the rain, and I'd rather get soaked only while running instead of shivering at the start line. It rained the entire way to the event site. And windy, too.
The radar 90min before start time.
Almost on cue, the moment the start horn was blown, the winds slowed and the rained stopped. Looks like puddles would be the only threat on the day.
Awaiting the start, ground soaked.
(Photo courtesy of Mile90 Photography)
I had a great place off the start line, holding a solid 4th place position, through mile 3.
Opening miles. The guy looking back on me actually was a 5k'er that
started with the 10k'ers (which, given different start lines, shaved about
.12 miles off his route -- cheater). He was trying to wave me through
to pass him, too. I wouldn't do it, so he zoomed ahead. He cracked later. Karma.
(Photo courtesy of Mile90 Photography)
Then I started to feel it: every mile that I'd seared in to my quads the day before at the Kansas Time Trial Championships. Mile 4 I fell apart, posting an 8:00+ minute mile. The hills that pocked the course, along with their descents, were shredding my legs. Just beyond the 4-mile marker, I lost one place in to fifth. I checked out my watch, and realized I was holding just off PR pace. I tried to push it over the last 2km.

Toughing it over the closing miles. (Cool photo, too)
(Photo courtesy of Mile90 Photography)
Though I was able to knock off another 1 second from my average pace, my legs were just too cashed -- I had zero energy left in them after yesterday. I finished at 46:23, a 7:26/mi pace, mere seconds (3 on the mile, to be exact) away from a PR.
The finish. (Photo courtesy of Mile90 Photography)
I still grabbed YR, technically, and had a great run after last week's Hospital Hill. I ended up taking first in-category, and holding fifth overall. Despite missing PR, I'd found a 10k rhythm. I was happy. My whole purpose for registering was accomplished.

Awards time. First in-age-group.
(Photo courtesy of Mile90 Photography)

Race Metrics
Distance: 6.24mi           Time: 46:23
Avg. Pace: 7:26/mi        Max. Pace: 6:04/mi
Climbing: 423ft             Kcal: 758kcal
Avg. HR: 169bpm          Max. HR: 178bpm
Avg. Cad.: 166spm        Max. Cad.: 184spm
Avg. VO: 11.2m             Avg. GCT: 239ms
Avg. Stride Length: 1.30m
1mi Splits: 6:43, 7:15, 7:18, 7:30, 8:10, 7:46, [1:48]
Weather: 64F/Showers in Area/SSE22-8
Placing: 1st/7 in age-group, 5th/76 overall
TrainingPeaks Analysis: HERE

[RACE REPORT] The Kansas Time Trial Championships


This event was graciously supported by Tailwind Cyclists of Pittsburg, Kansas. You can visit their website HERE.

WALNUT, Kansas -- As race seasons have progressed, it always seems that time trial races (or races that include time-trial-like legs, such as a triathlon or duathlon) get longer, expanding out to 40 kilometers, until finally contracting back to the standard 10km for Octoginta in October. This year, though the former 40km crescendo still remains in Des Moines in September at the Hy-Vee Triathlon, another 40km effort has emerged -- one that I had hoped to target over the last two years, but never did. Finally, for the first time, I would be attending the Kansas Time Trial Championships in Walnut, Kansas.

Previously just the Walnut Time Trials, this race has in the last few years become the state-wide championships, and has most recently usually -- including this year -- been held in mid-June. I signed up immediately following the Jesse Blancarte Time Trials via USA Cycling's registration portal. I was fresh off a solid 11 points earned, hoping to grab even more individual and team points in the KBAR/KBAT standings. This would also serve as a great check-in on my middle-distance time trialing skills ahead of late-August's Hy-Vee Triathlon, not to mention the Prairie Punisher Duathlon in just five weeks (5k run, 30k bike, 5k run). With a heavy cycling schedule ahead, followed quickly by a busy multisport season, it was time to hunker down [in to aero position].

The Route

With registration out of the way and "packet pick-up" on race day (I've never done a bike race that had packet pick-up ahead of time), it was time to map out and analyze the race route.

The start and finish would take place in Walnut, Kansas, about 25 miles northwest of Pittsburg, Kansas, home for Tailwind Cyclists (our event host). Walnut itself is small, a town occupying just one square mile of land along Kansas Highway 146 in Crawford County. Towns like these are the perfect backdrop for time trials and road races: wide state highway roads with very little traffic and beautiful open horizons.

The 2014 Kansas TT Championships race route, with elevation profile.
(Image courtesy of TrainingPeaks)

The route itself would start in "downtown" Walnut at the intersection of KS-146 and Maple. The course runs straight east until the highway turns south, becoming state highway 3. At 12.43 miles (20k), and just short of intersecting with KS-47, the course turns around and heads back to Walnut the way it came. Getting lost on the route would certainly be impressive.

The elevation profile is about what Kansans would expect for Kansas open country lands (and likely what most outsiders wouldn't expect): frequent undulations. The course is mostly uphill for the first 10 miles before diving down 2 miles and change to the turnaround, then uphill until 10 miles go, and a net downhill back in to Walnut. Though there are no official significant climbs, many mini-climbs adorn the first and last 10 miles of the overall course. Those climbs, along with the distance, should present enough of a challenge. The overall climbing on the course would equal just over 700ft along the 24.86 miles.

Then there's the potential for weather. What Kansas may lack in overall elevation change compared to other areas of the nation, it makes up for in weather. Forecast a week before for 84 and sunny, many things can change. In wide open country such as this, along with the arrow-straight nature of the course, wind is likely to be the biggest factor. Winds as little as 10mph from any direction will provide challenge, as participants will hit every point on the compass at least once during the route, each at equal distance. How hard and at what distance the wind is blowing will have to be very closely monitored.

Race Day

The weather would end up providing a bit of a challenge. Winds out of the south at 10-15mph with gusts as strong as 25 would essentially cut the course in to four equal parts: The eastern trek would have a stiff crosswind and just a touch of headwind; just beyond the 10k mark, the route turns south straight in to a nasty headwind, along with some of the more difficult ascents of the entire route; the large relief would come after the turnaround; even the final 10k would be a great opportunity to push, though still with the stiff crosswinds.

Arriving at 8:45, I noted all of the extra-aero frames, tailed time trial helmets and full disk rear wheels -- gear extras I'm always jealous of at time trials and triathlons. Arriving from a short warmup and getting a taste of the route conditions, I was less jealous. Trying to keep a bike upright with a full disk rear wheel surely would require a fair amount of extra effort. A tailed time trial helmet would shove in a crosswind, and limit any ability to turn your head once in a headwind. Even the extra-aero bikes would definitely be tough to fight against today with nasty crosswinds. With my semi-aero road frame, semi-aero road wheels and tail-less aero road helmet, I had a near-ideal setup, it seemed.

Five minutes before my start time, I slid in to the starting house ready to go. It wasn't long before I was off. I sprinted quickly to a pace I felt I could hold for the short haul east to the turn southward in to the wind. My legs felt fresh and comfortable through the first 10k. I had a great aero position on the bike I felt like I could hold for hours (save for the saddle that was not meant for aero positioning - I need to rid myself of that thing). The crosswinds pushed and pulled the bike, but I felt in full control.

Preparing on the approach for the turnaround.
(Photo courtesy of Roger Harrison)
Then, like a steel wall, the turn south. My average speeds went from 22 to 17 in a matter of seconds. This would be a painfully long six miles. My legs started to burn. I made sure to get as low on the bike as possible and just hold out for as long as I could; the turnaround would offer me wonderful respite from the conditions on the road. I felt the need to reach out of the saddle on each small ascent, but any standing on the bike was short-lived, as even the slightest of added surface area to the wind added to the workload exponentially. I started counting the miles off: 8...9...10... only 2 to go. 11...12... and the turnaround was just up ahead.

Given the two-way highway, the turnaround was only manageable at single-digit speeds. But with
Rounding the turnaround at 20k, heading back north.
(Photo courtesy of Roger Harrison)
wind at my back just after the apex, I was quickly up to speed back north. 25, 26...30mph speeds on flat roads. The turn west came in what seemed a matter of seconds, and even then, I had an oh-so-slight wind at my back, the rest of them crosswinds. I was faster on the final 10k than the first 10k, which made my bike dance around in the crosswinds even more. Still in control, "Walnut City Limits" read just ahead of me, 2 miles to go. 1 mile to go... 200 meters, I launched out of the saddle and sprinted across the line. 1:07:14. 22.2mph average speeds. Even with impressive Hy-Vee Triathlon bike legs on my résumé, this 40k effort would be a personal best.

The wait began for placing, knowing very well the massive competition in my category. Once all had crossed the finish line -- after about an additional hour and change's wait -- the results went up. 10th, just after halfway down on the 15 in my category. That was good enough for 12 points in the KBAR/KBAT standings (being a championship, riders earn double the points, meaning I earned double what would normally be 6 points for 10th place). No, I hadn't earned a podium spot. No I hadn't earned a cash-out spot. But I earned points and a PR to boot. With several time trial efforts in the form of duathlons and triathlons scheduled for July and August (not to mention next week's Tour of KC criterium), I was happy with my result.

Race Metrics Analysis

Distance: 24.86mi            Time: 1:07:14
Avg. Speed: 22.2mph        Max. Speed: 33.8mph
Climbing: 787ft                Kcal: 988kcal
Avg. HR: 157bpm             Max. HR: 172bpm
Avg. Cadence: 95rpm       Max. Cadence: 115rpm
Weather: 78F(HI80)/62%/PCloudy/S15(G24)
Placing: 10th of 15 in-category (12 KBAR/KBAT points)
TrainingPeaks Analysis: HERE

Wednesday, June 11, 2014

[RACE REPORT] Rain On the Hill: Hospital Hill Re-Run 5k & 10k


Hospital Hill official website: HERE

KANSAS CITY, Missouri -- The 10k is likely my favorite run distance: it's short enough for serious speed, but long enough to be insanely challenging. A lot can happen (and go wrong) over the course of 6.24 miles, so it still requires a fair amount of forward planning. I've already written a little bit about Hospital Hill (see my post about 2013), but I'll be re-covering one of my favorite races of the entire year here.

Format Changes: The Hospital Hill Re-Run

This year came with some welcome (for me, at least) changes. The 5k was moved to Friday night, leaving the 10k and half-marathon options on their own on Saturday morning. Additionally, organizers offered a "Re-Run" option for participants, which included the Friday night 5k in addition to either the 10k or half-marathon on Saturday morning. A fan of challenges, and of the 10k course, I took them up on the 5k/10k Re-Run option (I'd gotten my fill of half-marathons for a while, and actually was forced to miss the Dam-to-Dam Half-Marathon in Des Moines, Iowa due to hip problems).

The forecast weather for Friday (5k) and Saturday (10k).
(Image courtesy of NOAA)
Weather...Injury...

The weeks prior to Hospital Hill, the weather, as if often the case in Kansas, had been tumultuous. Thunderstorms had been forecast for nearly every day, some with severe conditions such as wind, hail, thunder/lightning, and flooding (even some tornadoes up north). Though I'm not completed objecting to running in the rain, I'd gotten my fill of raining in downpours, hail and thunder/lightning at the Garmin Half-Marathon, so I kept a tight eye on the forecast for race week. What I found, unwavering, was high chances of thunderstorms on Friday night, and likely chances (possibly even severe) for Saturday morning. The days surrounding Friday night/Saturday morning were nearly clear...it seemed the weather would be in town just for Hospital Hill. This should be interesting.

Making things even more interesting: three days before race day, I had my last quick run leading up to Hospital Hill. It was just a fast 5k at 5k-effort ("5kP," i sometimes refer it to, or "5k-pace"). One mile in, I noticed tightness in my right calf. Two miles in, it got worse. I knew I was pushing the pace (sub-7), but I was legitimately having some pain. I slowed only a bit for the final mile -- I was overheating anyways. Post-run, my calf was in extreme pain. Hours later the pain would be matched with a feeling of extreme tightness. My left calf was tight as well, but nothing beyond "normal" (rare do I suffer calf pain, but it happens from time to time, and is usually just from tight muscles after a hard workout). The next day, I did a short, sub-2-mile run at recovery pace (9:30-10:00) in an attempt to loose it up. 9:30 pace actually felt difficult, and though the pain didn't get worse, it stuck around. Any improvement post-run was minimal. The next day, the day before race day, my left calf would be fine; my right, not so much. This should be really interesting.
Start/finish/expo location: Crown
Center, Kansas City, MO.

Packet Pick-Up and Health & Fitness Expo

Like last year, packet pick-up is held in conjunction with a health and fitness expo (free stuff!) at Crown Center in downtown Kansas City, Missouri. Specifically, in one of the Crown Center exhibit halls. Organizers provided two offerings to stop in and pick up all necessaries: the Thursday and Friday afternoons before race day(s). Also, like last year, organizers had things running very smooth. All volunteers are always so nice and helpful. It's no wonder this event has become so popular and has achieved such a long and storied history. Well done.

The packet pick-up area for Re-Run participants.
Just like last year, volunteers are quick and super friendly.
Hospital Hill actually features a legitimate expo, with several vendors from across the area (and nationally) showcasing their product lines (and freebies!). Foot traffic was light-ish, although I dropped in on Friday afternoon during normal workday hours. Parking in any of the adjacent garages was also free with validation stamp -- always a plus.

Last year, for the 40th anniversary of the run, 10k and half-marathon participants picked up a snazzy track jacket with the Hospital Hill logo embroidered on the back. Not a bad substitute for a t-shirt, if you ask me (although, mine ran awfully small, and the material was fairly thin -- still a nice sub). This year registration came with a sports backpack, offered to all registrants, including the 5k'ers. Hospital Hill Re-Runners (5k/10k OR 5k/HM) got an additional Re-Run cotton t-shirt in addition to the backpack. Additional packet stuffs included an official Hospital Hill program, including maps and race day info (which I sorta like -- almost like a souvenir program), and of course the number bibs, complete with stickered timing chip, as opposed to shoe-mounted chip timing. Apparently a "golden ticket" randomly was placed in to one of the reported 8,000 backpacks, eligible for exchange for a free Garmin Forerunner. I know I already have the Fenix 2, but I was hopeful. No such luck for me.
The take-home goodies for Re-Run participants.

With packet, free goodies, and a new pocket waist band (I refuse to call the new designs fanny packs) purchased from the Fitletic tent in-hand, I was out the door. Packet pick-up itself took MAYBE 5 minutes, including parking validation. Additional hoofing around the expo varies depending on how much time you want to spend. Either way it's quick and easy. Again, well-done.

Route Review: The UMKC School of Medicine Hospital Hill 5k

This would actually be my first year with the 5k route, with last year's first-time experience being with the 10k. The only common link between the 5k and 10k is the emergence of Hospital Hill. Both routes start and finish in the heart of Crown Center Plaza in downtown Kansas City, Missouri. For the 5k, the route cuts short at Pershing road, and continues immediately east and south up Hospital Hill, all within tenths of a mile from the start.

The UMKC School of Medicine 5k course, with
Hospital Hill highlighted.
(Image courtesy of Google Earth)
Hospital Hill itself technically begins just beyond the Gillham Rd bridge at 22nd street. On the 5k iteration of the course, runners pick up Hospital Hill at Pershing Road towards Gillham, finally picking up Gillham almost halfway up the full Hospital Hill -- a bit of a shortcut relative to the 10k and half-marathon courses. Either way, Hospital Hill still proves treacherous, with an average grade (on the 5k course) of just under 5%, and grades maxing out at near 9% before easing up. For 5k'ers, climbing up Hospital Hill takes about half a mile.

Technically Hospital Hill ends at 26th street, at almost a half a mil in length, although a quick false flat after 26th, and runner immediately begin a second climb up Union Hill, a "short" quarter-mile 5%-average grade that tops out at 12% in some spots, and a climb that is often confused for a second section of Hospital Hill.

The first-half climbing finally finishes around the 1-mile mark, after turning east on to 29th Street. A half-mile downhill respite on 29th and turning north on to The Paseo allows for a quick gaining of composure before another quick uptick after turning on 27th Street. Flat roads comprise the rest of 27th until the last of any positive elevation change hits turning back north, about 1 mile short of the finish. The descent back down Hospital Hill along 25th Street, then Pershing again, makes for a quick finish, but still pounds on the quads.

Route Review: Hospital Hill 10k

A climb that 5k runners don't get to appreciate is the first climb north away from Crown Center Plaza along Grand, a three-quarters-of-a-mile stretch of road that boasts an impressive 85 feet of climbing, and grades averaging 2% and maxing out at just over 5% -- just long enough and steep enough to punish cold legs.

The Hospital Hill 10k course, with the often-take-for-
granted Rockhill Hill highlighted.
(Image courtesy of Google Earth)
Both the 10k and the half-marathon courses get the full brunt of Hospital Hill, all 0.66 miles of it. In the opening meters of Hospital Hill before Pershing Road (a stretch that doesn't appear on the 5k route), grades approach maximum at just over 13%, boosting average grades to 5%. Passing 27th, where the 5k route again diverts from the 10k/HM routes, 10k'ers get a smoother, but still significant, climb up Union Hill (+42ft, 4.2% max grade, 2.7% avg grade).

Other route features 5k'ers also don't get is Rockhill Hill, a sudden hairpin turn from Gillham Road to 39th Street that averages 3% and max's out at almost 11%. This is the hill that took me by complete surprise in 2013, and shot my impressive first-half pace to hell. Two final climbs, including Broadway Hill, make an appearance in the final mile and a half of the course before finally descending down Hospital Hill -- very quickly -- from just under 1 mile to go towards the finish back in Crown Center.

Regardless of your poison of choice, all routes require significant experience and prowess hill climbing in order to be even remotely competitive. Either way, you always crawl across the finish line having had likely the most bizarre fun you've ever had, alongside
an immense sense of accomplishment.

Race Day: Friday Night UMKC School of Medicine 5k
Selfies before the start. I'm off to the right, attempting
to avoid the twitter-ness (I failed).
(Photos courtesy of The Hospital Hill Run)

Though my right calf wasn't 100%, things had improved dramatically over the following days up to race day. My biggest concern was pushing the 5k to the point where I re-aggrivated it for the 10k which was a mere 12 hours after the 5k start time. I was stuck between taking the chance and pushing the pace, or playing it safe and placing all my eggs in the 10k basket.

I would choose the former. I lined up in the first lines of runners just ahead of the 6:45 pacers -- probably a bit hopeful given the course's difficulty. I was ready for the start with about 10 minutes to spare, a long time to wait in-corral. It was warm: Just short of 80 degrees and 65% humidity. Almost no breeze. A far cry from the scattered showers forecast earlier in the week for the evening. Despite the humidity, I didn't mind one bit.
Quick start by all.

The air horn sounded promptly at 7:00pm. From the start line in the middle of Crown Center, south on grand, a out-of-the-gate downhill gave me a quick jump-off. Then, not more than 300 meters later, we took an immediate right on to Pershing Road, and up the dreaded Hospital Hill. Given the course's shorter length, and my decision last year during the 10k to attack Hospital Hill, I decided to attack it doubly-so this year, especially considering the 5k route's shorter trek up the Hill compared to the 10k and HM'ers. I reached the top having only lost a few steps to the top 10 guys.

Then the immediate turn left on to 27th, and Union Hill (or is it technically still Hospital Hill? I can never tell). This one was shorter, but much steeper. It completely took the wind out of my gut. Undulations through the neighborhoods of Hospital Hill/Union Hill degraded me further. My
Cresting Hospital Hill (I believe --
if so I was hurting bad at this point).
breathing came out of control, meaning my HR was already maxing out. By 1.5 miles, I was already toasted, and decided to just sit in until the descent back down Hospital Hill in to Crown Center and the finish.

Each time another hill popped up, no matter how small, my pace plummeted. An alert stating I had fallen behind my Virtual Partner buzzed me -- my Virtual Partner was still set at 6:59/mi for last week's Amy Thompson 8k. This was not good. Another climb, another plummet. My right calf tightened up with just under a mile to go. The descents back toward Crown Center, though welcome, pinged my legs even more. I started to worry about my starting tomorrow.

The finish. Completely zonked.
The descent back towards Hospital Hill. Finally. I took as much advantage of gravity as my legs would allow. My second mile was a staggering 7:20. Mile three was shaping up to be the same, so I gunned it the best I could. Nearing the bottom, I remembered the blazing-fast start, all thanks to the descent from the start line. This meant a quick burst back UP towards the start line. Less than a quarter mile to go, I came off of Pershing and back on to Grand from the south side of Crown Center. I gave my best push, salving what left of an aggressive pace I had (if any).

Approaching the finish line, I saw 22:00 flash up on the clock. It has been a long time since I'd been above 22 minutes. That was nearly 7-minute mile average -- a pace I hadn't collected since summer of last year. I crossed at 22:24, a 7:06. Bummer. That may have been the most difficult 5k I'd done. Yes, I still had fun, but my pace faltered, I fell apart. The "What if" game started playing in my head. My leg ached. 11 hours until I line up again.
The radar, a mere 45 minutes
before start time.

Race Day: Saturday Morning's Hospital Hill 10k

I woke up with the sound of rain drops pattering against my windows. I had been expecting this. I immediately checked the radar: surrounded by green and yellow, and much more on the way. A bolt of lightning, a crash of thunder. Hopefully we would still be allowed to run. My leg felt better than last night (cherry juice!!). I was excited to see the start line.

View of the finish (and start -- in the
distance) line pre-race.
It rained the whole way downtown, with a few bolts of lightning here and there. We wouldn't be running in lightning. I had a feeling we would at the least be delayed. I arrived at 5:45am, a full hour and fifteen minutes before start time. I took full advantage of the adjacent parking garage -- I would no-doubt need to change out of soaking-wet clothes post-race. Better to do that under cover than in the rain. I checked the radar again: Less yellow, just as much green. And it didn't seem to have any chance of clearing up anytime soon. I broke out my rainy race-day secret weapon: triathlon running shoes. With drainage holes in the bottom, and sock liners designed to get wet, these would be perfect running in a deluge. Whilst others' shoes became weighted and water-logged, mine would simply feel damp. I decided to go sockless as well; socks would only soak up more water.
The anxious waiting during rain-delay.

Race-readying myself, it was about 6:15 when I was good for a small warmup. Walking from the parking garage, "take cover until we can give further update" blared across the loudspeaker. Delayed. At least to 7:30, according to organizers. I went back, grabbed a jacket, and waited it out. For another 45 minutes.

At 7:00am, the rain slowed, eventually stopping at 7:15. Organizers stated 7:30 would be the start time. All participants hustled to the start line at 7:20am. At 7:35, the wheelchair athletes were off. At almost 7:40, 10k'ers and half-marathoners were, too.

Just after the start, heading north on Grand.
Presumably pent-up from the 30-minute delay, the start was quick, with a small downhill and small uphill towards the Power & Lights District. Just short of the Sprint Center, we turned east, then back south towards Hospital Hill. My breathing felt sluggish. Mile marker #1 passed at 6:50. Decent start, but my side started to ache...side stitches.

Right at the Oak Street bridge, mere meters before Hospital Hill, the side stitches reached full-blow proportions. My pace plummeted. No doubt Hospital Hill wouldn't help. And it didn't. My second mile, the whole of Hospital Hill, clocked in at 8:00. Like last night, I hadn't hit paces like this so quickly during a 10k in nearly a year.

Cresting The Hill (again, I think).
Nearing the top of Hospital Hill, it started to sprinkle. Then the false flat, then Union Hill. My side stitches worsened. 7:45 3rd mile. I'd reached mid-course, knowing full well that the nasty Rockhill Turnaround was just up ahead. I decided to slow my pace, try to catch my break on the downhill in preparation for the turnaround. The weather turned from sprinkle to light rain.

The final descent towards the 10k turnaround at Rockhill. Last year, this climb had taken me by surprise and completely shattered me. I remembered a running article once that said "run ascents by feel, not by pace." I normally ignored such advice, but with pains like this, I'd take whatever help I could get. I sped through the hairpin on to Rockhill Hill. Amazingly, my side stitch started to let up. At the summit, it was nearly gone. Bizarre. On que, the rain picked up again. Would this be a repeat of Garmin?

The rain begins to fall.
Turning on to Broadway meant slow and steady descents, almost all the way until the approach back in to Crown Center. At the 4-mile marker, my left heel started to burn -- my sockless shoes. Not thinking ahead...moister + shoes + no socks = blisters. And all with over two miles to go.

The rain picks up.
My focus was fixed on the pain developing at my feet, which may actually have helped. I had lost sight of my breathing problems, forgotten about my calves (they had felt fine earlier in the run, anyways), and didn't think at all about the pouring rain all around me. Making sure to hold a conservative pace, miles 4 and 5 nearly disappeared.

By mile 6, I actually had a fair amount of energy left, likely from my upper-7-minute miles. Ready to get the hell out of my shoes, I picked up the pace, topping Broadway Hill, then the hill approaching Liberty Memorial. The rest was downhill. Broadway and Liberty put my sixth mile above 8:00 so far. I wouldn't let that happen.

I blasted down Wyandotte, then Memorial, then back on to Grand for the final stretch. My watch rang Lap 6, the end of my sixth mile: 7:50. Only a quarter mile to go. I picked up the pace even more. Descending in to Crown Center, finally, I saw the clock ahead of me: 48:00. Just like last night, I felt somewhat defeated. Last year I finished in 49:00. I at least had to beat that. I opened up my strides as wide as I could, finally passing under the finish banner at 48:39. 7:40 per mile.

Re-Run take-homes: from left, the 5k bib, 5k medal,
Re-Run medal (it spins!), 10k medal, and 10k bib.
The finish. Drenched.
Though I'd hoped, and even expected, pushing PR pace like I did a year ago, I started remembering all of the obstacles faced with during this year's run: calf problems, a 5k the night before, side stitches for 2 miles, and pouring rain. Assuredly anyone would be slowed a bit as well. Though 7:40 per mile was still well over my 7:25 PR, I had plenty of time to train up to a 10k PR this year, and plenty of opportunities to show for it (I had registered for the Heartland 30k series, a new series comprised of 3 different 10k races on consecutive weekends).

And anyways, Hospital Hill, despite the immense inevitable challenge it always brings, was still one of my favorite running races of the entire year. I had conquered [rain on] The Hill.

Hospital Hill 5k Race Metrics
Distance: 3.15mi                       Time: 22:24
Avg. Pace: 7:06/mi                    Max. Pace: 6:14/mi
Avg. Cad.: 166spm                    Max. Cad.: 196spm
Avg. Vert. Ocill.: 11.4cm           Avg. GCT: 242s
Avg. Stride Length: 1.37m
Avg. HR: 180bpm                      Max. HR: 188bpm
Kcal: 395kcal                            Tot. Climb: 236ft
Splits (1mi): 6:52, 7:20, 7:03, [1:01]
Placing: 8th place of 63 in age-group, 64th of 1893 overall
TrainingPeaks Metrics Profile: HERE
Garmin Connect Metrics Profile: HERE

Hospital Hill 10k Race Metrics
Distance: 6.33mi                       Time: 48:39
Avg. Pace: 7:41/mi                    Max. Pace: 6:16/mi
Avg. Cad.: 166spm                    Max. Cad.: 0spm
Avg. Vert. Ocill.: 11.2cm           Avg. GCT: 253ms
Avg. Stride Length: 1.26m
Avg. HR: 170bpm                      Max. HR: 183bpm
Kcal: 787kcal                            Tot. Climb: 712ft
Splits: 6:50, 7:59, 7:45, 8:01, 8:03, 7:52, [2:05]
Placing: 14th place of 71 in age-group, 83th of 1022 overall
Training Peaks Metrics Profile: HERE
Garmin Connect Metrics Profile: HERE