Showing posts with label results. Show all posts
Showing posts with label results. Show all posts

Saturday, December 13, 2014

Race report: 2014 Jingle All the Way 5K

Post-race coffee club (L to R: ER, TPP, SIOR)
Today's run (Jingle All the Way 5K): 3.1 miles - Time: 28:20 (9:08 pace)

After many months of resisting the call of competition, I returned to racing at the Jingle All the Way 5K in Seaford today. Joining me on this chilly morning were fellow Runsketeers SIOR and TPP, both of whom finished first in their age groups. The early results showed TPP at #1 and SIOR in the top three, but later she was bumped up to first as well. I'm sure there was no bribery involved in that decision. Well, pretty sure.

I didn't podium, but I had my best race performance in a year, finishing 5th in my division. This meant something to me, because my performance has suffered since January and I'd lost confidence in my ability to attain a credible pace (even on a 5K). There's still room for improvement compared to past years, but I did beat my expected time by over a minute.

I arrived at Cedar Creek Park in Seaford around 8:00 AM and missed the registration area as I drove through the park. I ended up parking about a quarter mile away because I saw a group of people, some of them running, and figured that was it. That turned out to be a soccer game, but I was quickly redirected by some kind spectators and made my way to check-in.

I dropped off my toy (the event is sponsored by the John Theissen Children's Foundation), got my number and found SIOR. She and I headed back to my car so I could store my jacket and affix my bib number. Unfortunately, the package contained no pins, so I ended up back at registration to get some. Along the way, we ran into TPP who was doing a warm-up jog and the reunited Runsketeers all headed toward the start.

This race is fairly small, with only 222 people participating, but they did a nice job, including placing wood burning stoves where you could toast marshmallows (and keep warm in the 30° temps). The downside of that was the possibility of smoke inhalation. After they played the national anthem, we were ushered toward the road for the start. I got a fairly forward position because there was no timing pad at the starting line and I wanted my net and gun time to be as close as possible.

That position probably helped me overall today, because I kept up with many people for the first mile, which turned out to be my fastest. The course itself is not that interesting. It's a lollipop-shaped route with a turnaround at the bottom of the "stick." Heading toward the turnaround, I first spotted SIOR among the leaders. Not long after that I saw TPP and soon rounded the bend to start my way back to the top.

My biggest concern about this race was being able to hold a brisk pace for the duration. Even though it's not a long distance, I've done very little to prepare for prolonged running intensity. Last weekend I played a bit with speed, but suffered some glute, hamstring or sciatica pain afterward. I decided to push harder than I normally would on a training run and see how it turned out. The course was relatively flat, but there were some elevated sections, including one that had us running directly into the wind.

Once I got to the circular part of the route I knew I had only about a mile to go. I maintained my speed, but didn't overdo it. Had I looked at the Garmin, I may have upped the effort enough to make up the 25 seconds I needed to average in the 8 minute range. As I got closer to the finish, I saw TPP's boyfriend JC who was on his bike, cheering us on. JC shouted some words of encouragement as I passed by and I soon entered the finish chute where I saw TPP and SIOR watching and cheering me in.

JC left to do a two hour bike ride (he's a hardcore triathlete) and SIOR and TPP located a Starbucks for our traditional post-run coffee break. SIOR was taking her daughter and her friends into NYC for an important birthday (13) so she needed to leave first. TPP and I hung out and caught up for a while before we headed off to start the non-race portion of our day.

I'm very pleased with today's result and proud of my buddies who led their age groups. I checked to see what I needed to pace to have podium-ed today and saw that there was a lot of distance between my finish time and the third place runner. I'm going to have a low mileage week but that's okay. I wanted to give my "injury" time to heal. I did feel soreness during the race, but it was minor.

Tomorrow I'll do some easy miles. The weather is supposed to be warmer and I'm looking forward to a nice recovery run. I'm not sure if I'll race again before January, but at least I'm back in the game.

Friday, May 30, 2014

Stress testing in sixteen steps

Not as fun as it looks
Today's run (street): 3.4 miles

Despite my resistance to the idea of taking a stress test, I finally acquiesced and went through it this week. My experience at the end of the Brooklyn Half provided the impetus to do it. Actually, it was strong encouragement from my wife, the Runsketeers and my friend KWL that made me go through with it.

If you've never gone through a stress test (this was my third), you should know that it's not particularly stressful. But it sure takes a long time. I don't know if the process is universal, but at my doctor, the process goes like this:

1. Arrive at doctor's office at your scheduled time.
2. Wait an hour to be called in.
3. Wait for the doctor in the exam room. You can pass the time by reading your chart on the computer display (at least that's what I did).
4. Have a conversation with the doctor about how you ended up in the medical tent after running a half marathon. Hint: his response will always be, "I want you to run a stress test today."
5. Have an EKG.
6. Have blood taken.
7. Have an heart ECHO sonogram.
8. Go to stress test lab and wait.
9. Get your first injection of thallium, a radioactive isotope that's used as a trace agent during the imaging process. Very reassuring.
10. Go into the imaging room and get scanned for 12 minutes.
11. Go into another sonogram lab and have carotid arteries checked.
12. Go into the room with the medical treadmill, where the technician attaches electrodes all over your body attached to a belt unit that you wear during the process.
13. Start at walking pace, with the goal of getting heart rate over 140. She ended up putting the incline to 16% and the speed to over 5 MPH to get me there.
14. Get your second injection of thallium and wait.
15. Get your second imaging to compare to the first after exercise.
16. Go home six hours after you arrive.

The good news is that you do get feedback throughout the process. My doctor said my EKG and ECHO were fine, the sonogram tech said the same about the carotid check and the treadmill technician said I didn't have a single missed beat during my session. I needed my doctor to review the imaging results. If there were concerns, I would have got a call yesterday. All of that, and no issues.

So why am I running so slow?

My doctor's office should now deliver my clearance form so I can use my company's fitness center. I can then do workouts in the morning when I get into the office. Without that, my options are either to go back to 4 AM runs, or work out when I get home from work. I worked from home today and got in a few miles before I started what turned out to be a busy day. It's the weekend now, and I hope to give those Cascadia's their first experience on the trails either tomorrow or Sunday.

Sunday, December 15, 2013

2013 running goal scorecard


Today's workout (elliptical): 35 minutes

Every January I like to post my running goals for the year and review the results in December. This has been an interesting year, starting with a big lifestyle change in February that affected my ability to hit a couple of my goals. Here's my assessment of 2013.

1. More weekday running diversity.
Goal: Run outdoors at least once a week before work. Establish at least one alternate route to take every other week.
Result: Not having a regular morning commute has meant more options during the week. Most of my weekday running still happens in my neighborhood, but the route often differs and my average distance has increased 20% this year.

2. More NYC running.
Goal: Monthly runs in Central Park, with or without a partner.
Result: While I regularly travel into the city, there are few opportunities to run there and there is no "home base" to change between business and running gear. No NYC runs happened in 2013. Perhaps this should be a 2014 goal tied to a specific event.

3. Break the neighborhood running habit on weekends.
Goal: One run outside of my neighborhood every weekend (weather permitting).
Result: I'll consider this goal met, with one and often two runs away from the neighborhood every weekend. 2013 has seen many more runs at Bethpage and Stillwell, along with local runs that expand outside my immediate neighborhood.

4. Return to racing.
Goal: Run at least one race prior to April's event. Bonus: Run a different half marathon than the RXR LI.
Result: Success, but no half marathon bonus. Race date changes and disruptions from Hurricane Sandy led to a diminished race schedule in late 2012. I participated in the 2013 Hangover run, and the February Snowflake race before the Marcie race that was rescheduled to June. A full race schedule followed for the remainder of the year.

5. Participate in a group run (club organized or otherwise). 
Goal: find a an open meet-up, local club run or organize one myself.
Result: Success. Participated in Hangover run in January and started an informal running group with two great people. Ran the GLIRC Clubhouse run and will probably join GLIRC in 2014.

Sunday, October 20, 2013

Comparing race times is easy but results are confusing.

A tale of three races
Today's run (street): 5.25 miles

This morning I downloaded my recent runs to Garmin Connect. I noticed a feature that compares selected runs, allowing users to see performance data by split (click above picture to read). The difference between this year and the last two year's times are easy to see. One thing that puzzles me is that the times on split 4 are really inconsistent. This year I covered .11 miles in 50 seconds at 7:55 pace, Last year it took me one second less but the pace was 7:18. In 2011, it took one second more to cover that distance, yet the pace showed 23 seconds per mile faster than this year. Very strange.

Today my thoughts were on recovery rather than performance. Due to my tapering, I covered far less than my normal 18-20 weekly miles since last Sunday. I took it easy and aimed for five miles. Although the temperature was a moderate 54°, it felt colder. I wore a light running shirt with 3/4 length sleeves and shorts, along with a pair of light running gloves. It was a good combination to start, although by the end I was wishing for shorter sleeves and no gloves.

I ended up running faster than I planned, but not all that fast. Recovery runs are a strategy to facilitate muscle repair and eliminate the built up lactic acid that causes soreness. I wish I'd taken it just a little easier. I'm looking ahead to November 10, when I'll be running the Hope for Warriors 10K. It's a great event (although the course itself is only so-so). My prep for this weekend's 5K fell short, and I want to do better. 10K means more base runs as well. Better get started soon.

Saturday, February 23, 2013

Race report: Long Beach Snowflake 4 Miler

The finish line
Today's run (Long Beach Snowflake race): 4 miles - 35:00 (8:45 pace)

This morning I ran the Long Beach Snowflake 4 mile race for the third consecutive year. After the devastating effects of hurricane Sandy, I was sure the race would be postponed this year. But the spirit of the city was evident today and the race went on. The course was different than prior years, but the experience felt similar. Weather conditions were far from ideal, but it could have been much worse.

The view beyond the finish line
The race was staged at the Lindell Elementary School, nine blocks north of last year's location. I arrived at 7:45 AM, hoping to beat the crowd in case parking was an issue. The school actually had plenty of parking and I found a spot close to the building. There were 129 less participants this year than last year and I was especially glad that I'd signed up. Although I live 30 minutes from Long Beach, I felt an obligation to participate and support this city that has been through so much.

Pre-race crowd keeping warm
 After picking up my race bib and shirt, I took in the sights and sounds of the growing crowd as we moved closer to start time. Every race is different, but the pre-race energy always feels the same. The school gym kept everyone warm and comfortable until a member of the race crew ushered us to the line ten minutes before the start. I was glad that it was almost race time, but the cold winds made me wish I was back in the gym.

The crowd assembled behind the starting line as the race director organized people so that the faster pacers could start at the front. I stood a few rows behind them, because I like to be swept along by the speediest runners for the first mile. After some inspiring statements about Long Beach's recovery from the storm, and a quick review of the new course, we counted down to the start.

The course went directly south for half a mile, turning east on Broadway for the next 1.5 miles before the turnaround. I didn't realize that Broadway was so close to the old boardwalk. I'd expected to turn left after passing a couple of blocks, not ten. I was being passed left and right, despite my attempts to keep up with the faster crowd. I felt some relief to make the turn at Broadway, but I knew I still had three and a half miles to go.

There's a point in every race when I feel that I failed to train properly for that event. It usually comes after the first couple of miles, when I begin to question my ability to sustain my race pace. Today was no different. I came through the first mile in 8:06. A good pace, but it was almost 15 seconds off last year's mile one split time. I hoped to stay below 9:00 for the remaining splits and I managed to do that, although mile three recorded at 8:59 on my Garmin.

It's always a fast crowd in Long Beach and getting passed can be disheartening. It wasn't until I made the turn at mile two, heading west, that I saw the large number of people behind me, still running east. Instead of feeling happy, I worried that they would all eventually overtake me. This race felt hard, probably because I haven't gone all out in race mode for months. Still, I felt that I could handle the pace I was running, and I ended up finishing in the top 35%.

I settled into my stride at three miles, coming through a few seconds under 26 minutes. It seemed to take forever to reach Lindell where we took a right, heading north for for the last half mile. By 9:30 AM, cars were trying to cross the course at some intersections. Traffic control did their best, but I actually saw a couple of cars impatiently cutting through with runners still crossing the box. I had no incidents, but a couple of cars made me nervous.

I finally saw the finish chute when I had a block and a half to go. I tried to muster more speed, but I was at my physical limit. It would have been nice to cross the line earlier, but I left nothing on the course today and ran the best pace I could maintain. I was very happy to cross over the line. I felt all four hard miles at that point, yet I also felt strong.

Why am I smiling? The race is over
After the race, I watched some runners come in before downing a Gatorade and taking a few pictures. I was disappointed that my friend Steve, who ran this race with me the last two years, couldn't participate today. I'll tell him what he missed. For me, it was a validation of my fitness and a pretty good effort. I may not have loved every minute of the run, but I sure loved the feeling when I finished.

Saturday, February 11, 2012

Race report: Long Beach Snowflake Run

Pouring it on for the finish (center, in black)
Today's race (Long Beach Snowflake 4 Mile Run): 33:50 (8:28 pace)

For the second year in row, the snow has forced Snowflake Run participants off of the boardwalk. Last year it was an issue of volume, there was so much snow and ice on the boardwalk that it became both dangerous and impassible. This year it was a steady but light snowfall that would have been too slippery for fast running. So, once again, we found ourselves lining up on Broadway for this four mile race.

Last weekend I ran intervals on the treadmill in the hope of being ready to go out hard this weekend. That must have helped because I achieved a new 4 mile PR this morning and beat my prior PR by over a minute. Team Emerging Runner accompanied me this year and, aside from some difficulties finding a parking spot, the event went very well.

We arrived about 30 minutes from start time and when I walked into the gym to pick up my race number, I was surprised to see so many people milling around. The room smelled strongly of perspiration and adrenaline and against one wall was a slide show accompanied by blaring music. I headed to the rest room after visiting registration and saw a long line of of women waiting patiently. The men's room line went quickly and soon I was back to my family in the gym.

My fuel of choice for the race was GU Roctane and as it got closer to race time, I had some Ghiradelli 72% cocoa dark chocolate to top me off. I'd just run into my friend Steve who was running with me and I gave him some chocolate for a pre-race boost. Steve had his wife and their two little ones at the race and everyone was in good spirits despite the cold, wet weather.

We lined up fairly close to the start line to get a good take-off position. Steve and I learned a lesson last year when we were forced into a narrow path between the snow and parked cars. That situation produced so much crowding that we could barely exceed a trot for the first couple of minutes.


A fast start as the snow came down
Before too long, we were off and running. My Garmin had gone into energy saver mode so I wasn't able to start my timing until I'd run a few hundred feet. Once that was resolved, I focused on staying with a fast crowd of front runners who I'd hoped would sweep me up and carry me along.

My friend Steve disappeared into the crowd almost immediately and I figured I'd see him at the turnaround or at the finish line. The group surrounding me was running at a faster pace than I could sustain, but I did my best and hoped to pass the first mile one under 8:20. When I saw the timing clock I was amazed to see that I'd actually clocked 7:54 for mile one.

I must have passed Steve just before that point because he told me later that he came through around 8:05. My goal was to preserve as much of that first mile pace as I could, and I settled into a rhythm that I thought I could maintain throughout the race. My splits were 7:54, 8:43, 8:34 and 8:39. I bounced around a little, but I didn't suffer from progressively positive splits as I've done in the past.

It's a nice crowd of runners who participate in these Long Beach races. None of that obnoxious posturing I've seen other places. That isn't to say this crowd is any less competitive. If anything, I think this race fields a deeper pool of speedy runners than I've seen elsewhere.

Having run this course last year, I knew what to expect in terms of progress and effort. I ran hard but I probably could have pushed more into the middle miles. I wanted to make sure I had enough energy to finish strongly and I'm pleased with the way things turned out.

Once I passed two miles, I reminded myself that I had less than half the distance to go. The rate of people who passed me had slowed down to the point where I was running mostly with those who ran about my pace. I used the guy in front of me as a pacer through most of the last mile. Once I saw the finish chute, about three blocks in the distance, I dropped a gear and gave it my best of the day.

As I approached the finish line I could see my wife and kids cheering me on, but the clock atop the chute was reading 16:00, so I feared that the timing system wasn't working. My Garmin showed that I'd come in under 34 minutes, so I knew I'd done well. It turned out that the actual race clock was positioned low and to the left, so I'd missed it.

I assumed Steve had already finished, but discovered that he hadn't yet come through. He came crossed the line about a minute later - an impressive effort for someone who hadn't really run much over the prior few months. We went back to the gym to see our results posted and I saw that I'd crossed the line in 33:50, for a pace of 8:28 and a new PR.

Steve and I went back out and watched the runners streaming across the line while the snow continued to fall. I had been concerned that the wet surface would be too slippery for my Hattori's, but that wasn't an issue. However, the shoe's lack of insulation was a big issue and I couldn't feel my toes for most of the race. I'll have to remember that the next time I wear them in cold, wet conditions.

So, my first race of 2012 went very well and I'm enjoying the great feeling that comes from a sustained effort like a race. I'll probably go out for a very easy run tomorrow and start thinking about my strategy for my next two races, one short (5K) and the other long (13.1 miles). In the meantime, I'll enjoy all the moments from today's events.

Saturday, December 17, 2011

Race report:Bethpage Ho Ho Ho Holiday 5K

32° at start time, I was tempted to wear the race sweatshirt
Today's run (Ho Ho Ho Holiday 5K): 3.1 miles - 26:06 (8:24 pace)

I wanted to finish up the year with a December race because I've never competed in this month. Not counting the Nissequoge Turkey Trot that I ran for fun on Thanksgiving, today's race was my tenth of the year. I had no idea of the scale of the Bethpage Ho Ho Ho Holiday Run, but there were well over a thousand people milling around when I got there.

Our weekends can be busy and today my daughter was hosting a holiday party for her friends. Due to that, I went solo, but I did see some people I knew once I got there. I received my sweatshirt after picking up my race number and dropped off some toy donations. After that I walked back to my car to attach my bib and store the race shirt.

It was 32 degrees when we assembled on Broadway and waited for the start. I tried to get closer to the front, but the masses of people prevented any further progress. Santa is the theme of this race and at least half the runners wore seasonal clothes with Santas and elves being the costumes of choice. I had no idea that Under Armor sold running tights in red and vivid green.

As expected, it took about three minutes before I could get up to my planned speed. There were so many people on the road I was afraid of tripping. In fact, I almost stumbled over an elf who cut in front of me just as I was about to zip by two runners.

With no chip sensor at the start, I thought my first mile split time would suffer because I didn't get to full speed until I'd covered a quarter mile. When we reached the first mile I could see the split clock, but with the crowd in front of me I could only see the two numbers to the right of the colon.The numbers were just rolling past :00 and I figured that meant 9:00, but in fact it was 8:00. That was a happy surprise.

Race course: twice around with a loop in the middle
I figured I'd keep the hammer down as long as I could and the flat course helped. Our route was basically a rectangle of wide streets with one small loop that diverted us through a neighborhood. We ran the rectangle two times and passed the Middle School twice. I would have liked a more scenic route but the lack of distraction helped me focus on my speed and form.

Since we did two laps around the course, I knew where we were when we reached the final section that diverted from Broadway into the school driveway. I sprinted the last tenth and crossed the line a few ticks past the 26 minute mark for an overall pace of 8:24. It wasn't a PR but it was my fastest 5K this year and I ended up in the top third rather than my usual middle pack position.

I congratulated a colleague from the office who crossed the line a couple of minutes after me, but I couldn't find a couple of other people who I'd hoped to see. I headed home soon after, rather than wait for the awards ceremony.

Later in the day, while the party was raging at home, my son and I went to Dick's sporting goods to get a requested item. While we were there I saw that they had the Kinvara 2's on sale for $59.00, an incredible bargain. I asked for a pair in my size and tried them on to confirm the fit and was disappointed with the feel. I ran around the show department "track" a few times and decided, bargain or not, the shoe didn't work for me. Oh well, the search continues.

Tomorrow I plan to do a longer run, very slow, to help me recover from today's intense race. This was a great event and I'll plan to run it again next year.

Saturday, November 26, 2011

Training slower but racing faster

Today's run (street) 3.55 miles

One thing that I've learned this year is that the speed I usually run isn't the same as how fast I can run. This year I've observed two things that don't seem to correlate. First, my average training pace (by observation, not by studying my running logs) has slowed down about 10 seconds per mile. The other observation is that my race paces have improved noticeably in almost every race this year compared to previous years.

I'm not sure what this means but it may have something to do with the quality of my training runs that may be a bit slower, but have more focus. The legendary running coach Jack Daniels said "Every run should have a purpose" and I try to follow that philosophy with my daily workouts. If I need to prepare for a hilly race I try to run hills. If I ran hard the day before, I look to run my next session easy to speed up recovery.

The true explanation for my slower training - faster race pace may be far more simple. Since I started using my Garmin FR210 GPS watch, my mileage is usually under-recorded between 2-5% which makes my pace look slower. When I bother to map my true distance using Gmaps, I see that variance. If I don't, I tend to accept and believe that I'm running slower than I actually am.

I got out around 8:30 this morning after debating whether I should run or do a core workout and (possibly) an elliptical session later. My legs were tired so I considered the lower impact option. But the weather was cool and the skies were clear so I headed out the door thinking I'd take it easy and not worry about my pace.

The run was easy, in fact I slipped into a few periods where I was so lost in thought that I felt like I was sleep-running. I focused on opening my stride but I didn't think much about my speed. When I finished my run I was surprised to see that I'd averaged slightly more than 9:00 a mile. That's not particularly fast, but the pace was about :40 per mile faster than it felt. Perhaps all the racing I've done of late has helped in my daily training. That almost 9:00 minute pace was a nice surprise. Sometimes a slow run feels fast, and a fast run feels slow.

Sunday, June 5, 2011

Race report: 2011 New Hyde Park 8K

An 8K PR for the ER
Today's run (New Hyde Park 8K): 5 miles at 8:40/mile

As they say, the third time's the charm and that was the case for me after today's race. I had hopes of beating my prior finish time of 44:42 that I ran in both 2009 and 2010 and I certainly did that. Last year I went out much slower than the prior year and picked up my pace later in the race. That resulted in a better experience than 2009 (when I went into energy debt by mile 4) but my time ended up exactly the same. But that's ancient history -- the better story is today's race.

TEAM EMERGING RUNNER
Form doesn't always follow fashion
Although my wife and kids try to join me at every race, for some reason they could not attend prior to this year. It was a great psychological bonus to have them with me today. We arrived early and were able to park at the school, unlike last year when I needed to park some blocks away. I saw many familiar faces, this is very much a running club race, and I knew that it would be a fast field. The scene was familiar and, per tradition, the race tee was, umm, aesthetically interesting. But it is 100% polyester so I can run in it.

Registration was well organized, as usual
PRE-RACE PREP
We watched the mini run for kids and then made our way towards the starting line. I was feeling good and my Hattori's felt light on my feet and ready to race. What had started out as a cool and cloudy morning had turned sunny. Thankfully, it still wasn't all that hot. I took a GU Roctane gel 30 minutes before the start. I also carried a small bottle of water in case I needed to refuel near the end of the race and wanted some hydration along with the gel.

Off and running
START
We started on time with a field of almost 300 runners. I hit start on the Garmin 210 and took off quickly, happy to see my family on the sidelines. I felt good knowing that I'd see them again in about 45 minutes. I had prepared well for this race -- two day's prior rest, a reasonable taper, core exercises the day before, my favorite gel in my system and adequate hydration before the start. Plus my excellent Craft running shirt and those Hattori's.

THE RACE
When my Garmin chirped at mile one it took me by surprise. Interestingly, the FR 210 indicated that mile a few 100ths sooner than the official mile station. I've been a little suspicious of the measurement of this course because my Garmin FR 50 and 60 always over counted and my prior mapping of the course on Google Earth put it a tick longer than 5 miles. Since the GPS never over counts it makes me wonder a bit.

More importantly, I felt great after mile one and that continued as we headed north on New Hyde Park Road. Mile two comes along the service road on the LIE and I found myself passing people instead of being passed (as was my experience last year). I was still feeling strong at the third mile and decided that I didn't need an additional gel to get me through the duration. By mile four I knew I was on track to beat my prior time but knew I still had another mile to cover. I went against instinct and surged on the uphills, surprised to find I still had energy when I got to the top.

When we turned into the neighborhood that backs the school I knew I just needed to maintain a decent pace to finish under nine minutes a mile. I was feeling good until a race volunteer yelled "Just over half a mile to the finish!" For some reason that made it seem like I had more distance to run than was in my head but I knew that soon it would be less than a half a mile.

THE FINISH
I finally saw the yellow street sign and green lawn of the school a few hundred feet ahead. At that point a young woman pulled beside me and said "This is it" before dropping into gear and leaving me in the dust. I kept up my charge and when I hit the lawn I sprinted toward the finish line. I noticed my son and daughter running on the sidelines in my direction and I looked for my wife who was getting ready to photograph me crossing the line. It was the first time I ever got a picture of me finishing that race (top photo).

My Garmin recorded the race as 5.05 miles and I'll take a look at the route it captured when I upload it on Garmin Connect. I knew I beat my prior time and was really happy to see that I achieved a pace that I'd even consider good for a 5K. After grabbing some water and walking off some post race energy I checked the posted times and verified that I had a new PR.


EMERGING RUNNER COMMUNITY
I was very happy to meet another runner, Paul (below right), who told me that he's an Emerging Runner reader. Paul was running in Saucony Mirages and they worked for him, helping him to a sub 7:00/mile finish. Amazingly, Paul had raced the previous day and he told me that he races about once a week. No wonder he's so fast! I was really glad he stopped to talk and I'll look for him at other races, but I know I won't be able to keep up with him once the gun goes off.

Two runners: one fast, one emerging
I'm very pleased with today's race for so many reasons. It was my best race performance this year and it reinforced to me that my training and preparation are on track. I loved the Hattori's and I don't want to run in anything else now. I don't have any more races on the calendar until the Dirty Sock in August but I'm tempted to find a 5K to run in July.

Monday, April 12, 2010

Does race pace matter?

Posted results from yesterday's race

Today's workout: Post race rest day

I know I sometimes get too caught up in the metrics of running and miss seeing the forest for the trees. However, I know that capturing, aggregating and analyzing performance data helps motivate me to run every chance that I get. Yesterday I was prepared to end up with a middling overall race pace once I passed the mile 1 checkpoint at 9:29. That was disappointing because I always look forward to races providing a 20-30 second per mile improvement over training paces. When I passed mile 2 I heard the race official calling out times in the 17:00's and knew I was making my way back to goal pace. When I heard "25 minutes!"  shortly before the race-ending hill I was convinced I'd end up well below expectations. Ultimately, I did fine. Compared to the paces I've run recently, 8:41 is darn good. But it didn't seem so at the time.

I know running is about health, community, experience and fun. How fast you go depends upon your physical abilities and your conditioning. But a race is really about speed and competition. Some people take a different approach and view races as an opportunity for a shared experience. Their pace and finish times don't matter. For them, it's about the journey, not the destination. I sometimes wish it didn't matter whether I broke 8:30 or if I ended up in the 9:00 minute range. I know myself well enough that if it weren't for goals, targets and PR hopes I wouldn't work as hard to prepare for races. The health benefits I get from running come from all that work. All the same, I still enjoy a long, easy, slow run on a cool Sunday morning as much as anyone. But on race day, for me, it's all about the numbers.

Saturday, November 28, 2009

Bridie Goldstein 5K - an Emerging Runner PR



RACE RESULT: Bridie Goldstein/MercyFirst 5K - 25:50 (PR)

The weather report said temperatures would be in the high 40's with winds gusting up to 50 MPH at the start of today's race. I was curious to see how that would translate in terms of running conditions. The weatherman said it could feel like freezing temperatures when the wind was that high. My wife surprised me on Wednesday with a gift of a Nike long sleeved running shirt and a pair of high quality compression running pants. I am no fan of Nike's shoes but I think their apparel is top notch. On Wednesday I was thinking that these clothes would be perfect for December's cold but this morning's weather made me think that today would be a good day to put them to use. I wore my Zoot short sleeve jersey over the new long sleeved shirt to ward of the sharp chill from the wind.

The race was was so close to home it only took us 5 minutes to get there. The winds were strong and it felt cold. Fortunately registration and the exhibits were set up inside the school so me, my wife and kids were able to stay warm up until a few minutes before the start. This year they had a category that included runners and their dogs so there were many woofs heard among the runners. Smartly, they had the dog participants leave two minutes after the two-legged start. It was chilly at 10 AM and we got off fast because the course starts downhill. I was careful to maintain a moderate-to-brisk pace as I had learned a lesson in previous races that a fast start can lead to a painful finish. The length of a 5K gave me some latitude for pushing hard compared with a 5 miler or 10K and I did make my way by a number of people over the first mile. Unlike other races, I didn't get the feeling that what lay ahead would be painful. However, I was concerned that so many cars were driving on the main roads while we ran alongside. Happily there were no close calls.

The course had a few hills that I thought might prove difficult but I came through them comfortably and even passed a few people during those segments. At one point, when I was a mile from the end, I started wishing the race was longer because I was enjoying the experience so much. I did get passed by a few people including some very fit runners who had dogs on a tether. After starting mid-pack I finished in the top 20% so for once I enjoyed the experience of passing more people than passed me. At the end I sprinted the last 100 yards to beat out two runners to the finish, one of whom had overtaken me right before that. As I ran past the finish line I saw my family waiting and cheering loudly: my payoff for that extra effort.

So November Emerging Runner beat May Emerging Runner by a decisive margin today. I'm pleased by that and proud of the six races that I've run this year. Next year I will likely race at some distances I ran in 2009 and I'll have a chance to beat myself at 4 miles, 8K and 10K. But today I'll enjoy the 5K 'victory' and will revel in the fact that my performance is going in the right direction.

Sunday, June 7, 2009

The race is run: 8K - 53 yards = 9:00/mi


I'm happy to report that this morning I completed my third race in as many months. The race distance was 8K (53 yards short of 5 miles) and it really pushed the limits of my stamina. I've regularly run 5 or more miles over the last six months but usually at a comfortable (non-competitive) pace. I did well through most of the race but I did find myself questioning this whole running thing at one point. I'll get to that further below.

Now that I've experienced racing a few times I know better what to expect. I arrived early to ensure a good parking spot and to allow enough time between check in and the start of the race. Despite my concerns about the planning (online registration was not enabled until the week of the race) the event was well organized and check in was orderly and efficient. I got my number, timing chip and t-shirt and got myself set up. I was alone so I stowed the non-essential items in my car and then did some stretching and warm up exercises. There were a number of people doing warm up runs but with the sun and the 65+ degree heat a warm up did not seem necessary. Most participants belonged to running clubs and there were many of those. Each club seemed to establish a base camp where they stood around and talked as we waited for the start. I was one of the odd men (and women) out but I chatted with a few people. I even showed another runner how to attach his timing chip and that made me realize that I'm no longer a complete newbie.

We began lining up about ten minutes prior to the start. I stayed on the sidelines where there was some shade as the sun was already bearing down at 9:05 AM. When I did get into place I was behind 30 or 40 other runners. Once the starting horn sounded we were off and, with the crowd ahead, it took me at least 15 seconds to pass the starting line. My plan was to start fast so I had to maneuver around some slower runners to get a clear area for running. I was pleased with my pace and very happy when I passed the display at mile 1 which showed 8:25. The course was balanced between hills and downhill stretches. I'd guess that overall it was balanced neutral to downhill. There were no killer hills but there were a few stretches where I had to put my head down and just push on for a distance. I was still tracking below 9:00/mi after mile 2 and, like the 5K in May, the time between miles two and three seemed to go very fast. I must have started to lose speed after the third mile because I had managed to hold off from being passed until then. I even passed a number of other runners after the second mile but as I headed toward mile four I got passed by at least five runners. I tried to maintain some speed on the downhill sections but I wasn't feeling all that strong and started "borrowing" those stretches for recovery from the hill segments.

The last mile was the hardest and I seriously felt like I couldn't maintain my pace too much longer. It felt a lot more like suffering than fun at that point. There were many people cheering as I got close to the finish and all the volunteers who were passing out water along the route were very gracious and encouraging. I felt slightly more energized once I saw the green field ahead that told me the finish line was close. Once I reached the grass I gave it everything I had and sprinted the final few hundred feet and noted that I had finished at 44:42 which meant that I beat 9:00 per mile.

Except I didn't...

When I looked at the posted results near the finish line I was disappointed to see that I ran a 9:00 overall pace and it hit me that the 8K course was 53 yards shy of 5 miles! I started thinking about the crowded start and the fact that I probably would have beaten 9:00 if my starting position was closer to the line. But that's an excuse, if I'd maintained the same pace for the last mile that I'd run for the first 4 I would have made my goal. It was my conditioning that prevented that and now I know that I have to train better for longer distances. I can only be grateful that it wasn't a 10K!

Despite not beating 9:00/mi I'm happy that I came as close as I did. The post race experience was a blur. I remember having a banana, an orange slice and a bottle of water and I tried to keep moving to allow my heart rate to drop slowly. I was happy with the race I ran but I know where I need to improve. I've emerged a little more. So what's next?
 

blogger templates | Webtalks