Race report: Cow Harbor 2012

Crossing the line (in white, directly right of tree)

Today's run (Great Cow Harbor 10K): 6.2 miles

58:32 (9:26 pace)

Despite concerns about a rain-soaked start to the 35th running of the Cow Harbor 10K, we ended up having near perfect weather for the race. At the start it was overcast, and by the end it was sunny, but temperatures and humidity remained moderate. I didn't achieve a PR or even a PB for the race, but I was happy with my results that fell right in the middle of my prior two Cow Harbor efforts.

Team Emerging Runner arrived at Northport high school about ten minutes before 7:00 AM and we caught one of the shuttle buses that take runners and their crew to the Laurel Avenue school. This school is ground zero for the race and I made my way to numbers pickup before the lines got too long. I saw that I was assigned a 9000 series number, based on my predicted finish time.

The trick to managing 5,000+ runners is to put them into corrals with a staggered start every minute to spread out the field. It works extremely well but you need to do a little math every time they call a mile split, backing out the number of minutes based on your bib number. So if your bib starts with a 4, and the first mile split is called at 11 minutes, you'd subtract 4 minutes to get your pace of 7 minutes per mile. Easy right?

Dave 2.0, on left

We saw a lot of friends while we waited for the race to begin, including Dave who had suffered a heart attack at a race in February. He has recovered impressively well and it looks like he had a great race this morning, beating my time by over a minute. We had a mini reunion with a group of teachers from our kid's elementary school, and I saw my my work colleague Bill, who was running Cow Harbor for the first time. He was concerned about the James Street hill, but he ended up running a great race.

I didn't train intensely for the race this year and my only goal was to finish under an hour (mission accomplished). I was caught by surprise when it came time to release my start group. Due to the number of people in front of me, I thought there was still another flight in front of ours. That worked out well because I didn't experience the countdown jitters that I normally get.

Off to a good start on Laurel Ave.

I took an Accel Gel 2nd Surge twenty minutes before the start, and I felt good coming off the line. I was concerned that I'd have a repeat of the New Hyde Park 8K start, when I found it difficult to keep up with the crowd. Unlike that race, I wasn't fighting a cold, and I moved along well through the up and down (and then mostly downhill) Scudder Avenue. The crowds were out in force to cheer us on.

A little after the first mile, we turned onto Woodbine and ran near the water where the crowds were even larger. Between the noise, the people, and a large group of bagpipers, it felt surreal to be part of the entertainment. We quickly passed Main Street and reached Bayview Ave with a rise that only hints at what's to come 3/4 of a mile later. And by that I mean James Street - AKA, "Widow Hill."

Starting point of the dreaded "Widow Hill"

There are many ways to approach James Street in this race and I watched that play out once again as I began to take on the hill. Some runners attacked it and others chose to walk it. Like I did the previous two times, I accepted the challenge and adopted a steady pace that I felt I could sustain throughout the half mile of steep road.

I refused to look ahead lest I'd be discouraged by the amount of hill that was left to climb. When the road became even steeper I knew I was near the top. When it leveled out I felt great relief, but tried to increase my pace. The post hill section doesn't provide much recovery time as the road rises once again before leading to a lengthy downhill span between the 2.8 and 3.75 mile points.

Just after the 5K mark I spotted a work colleague who told me she'd be standing on the corner of Eaton's Neck Rd. and Ocean Ave. We tried to coordinate last year but I just missed her. It was great to see her and her dog at the halfway point of the race.

I felt remarkably good at that point, with the trauma of Widow Hill behind me and a stretch of downhill road in front of me. I wasn't monitoring my pace, but my heart rate was holding steady in zone 4, as I'd planned. I felt good but I knew I'd soon need to switch gears and take on the long climb up Waterside Ave.

Waterside Ave goes on for over a mile and it's mostly uphill. Some say this section is worse than James Street, but I disagree. Both require patience and an acceptance of the elevation, but Waterside's grade is far more subtle. I kept a pace that made sense and allowed me to stay with the crowd. I began to fatigue around the five mile point but I never had concerns about bonking. I'd filled my gel flask with two Accel Gels with the 4:1 formulation (carbs/protein) and I sampled it through the last few miles.

Pumpernickel Hill isn't as bad as James Street, but it comes near the end, after 1+ miles of fun on Waterside. I was up and over it fairly quickly. As I got to the top, a spectator was screaming, "A 77 year old man just took the hill!, a 77 year old man just took the hill!" over and over. Impressive yes, but enough already. And not in my ear please.

Encouraging message near the end of the race

I always expect the last part of the race to be triumphant, with a predominantly downhill section that leads to Main Street and the finish line. But after everything that comes before that point, it's hard to exploit the opportunity to push hard. It's basically a matter of holding the gains and pouring it on with whatever is left at the end. The finish chutes appear when there's about a fifth of a mile left in the race. Like an oasis, they seem to remain out of reach despite moving relentlessly toward the line.

I crossed the line 58 minutes after I started, though I didn't check the clock when I came through the finish. I saw my wife and kids and that made me happy. They are a great support team. I had to look up my results later, and they closely matched my Garmin's time.

After the race we headed to the crowded waterfront festival where I was able to get Gatorade and a couple of bananas that helped restore my electrolytes. There was a great band playing and lots of booths showing products and services. We ran into Bill and one of my daughter's teachers before getting back on the bus that took us to where we parked the car.

So one more Cow Harbor race is on the books. Mohamed Trafeh won the race today for the fourth time and Alisha Williams was the first woman to finish. I know there are bigger races with many more participants and more features, but on Long Island, (giving due respect to the LI Marathon Festival of Races) nothing quite compares.

Cow Harbor 2012: rain or shine (but please shine!)

Not what I'm hoping to see tomorrow

Today is rest day number two, prior to the Cow Harbor 10K. The weather report for tomorrow is slightly discouraging due to some bad timing. They are saying that both Friday and the weekend will be beautiful, except for some rain that will sweep through between 7:00 and 9:00 AM. If that's accurate, we could be in for a soggy start.

I won't worry about the weather because there's nothing I can do about it. I don't enjoy running in the rain because it can cause some annoying visibility problems for me (glasses). Worse, I really dislike the feel of moisture permeating my socks and sloshing around my running shoes. On the bright side, if it's raining we won't have to deal with the hot baking sun. I hope it doesn't rain, but if it does I'll deal with it.

In terms of my readiness for tomorrow, I don't think I'm at the same level of conditioning as I was a year ago. I looked at Daily Mile and saw that I've only done four runs longer than 6 miles since the beginning of August. Half of those happened in the last two weeks, so it isn't like I've ignored distances altogether. But even with those workouts, my base isn't really optimal for a hard 6.2 mile run.

I'm still debating whether to do numbers pickup later today, or get them tomorrow before the race. I haven't chosen my race day gear but I have my nutrition figured out. I'm excited to be running Cow Harbor once again and I hope conditions are good. I'm also hoping my colleague FS also has a great race this weekend when she runs the Dutchess County Half Marathon.

Red Bull's Cow Harbor sample

One way to moo-ve faster on race day

As a blogger who reviews running related products, I occasionally receive interesting items in the mail. When I came home on Tuesday night, my wife handed me a small cylindrical package and asked if I was expecting something. I looked at the return address and saw it was  from Red Bull North America. I wondered what they sent me and why they sent it.

The package contained a can of Red Bull, accompanied by a printed note that thanked me for being part of the Great Cow Harbor 10K. I thought that was a great marketing idea. It probably cost a lot more to mail these cans than simply include them in race goody bags. However, this certainly got my full attention and it tied the product directly to the race.

Will I use this can of Red Bull on Saturday morning to kick-start my run? Not a chance. I still have trust issues with energy drinks and I would never use a supplement for the first time on race day. Still, I give Red Bull credit for their smart approach to demographic targeting and I appreciate their support and sponsorship of Cow Harbor and other races on Long Island.

Cow Harbor training dissonance

After Bayview, the nightmare begins

Today's run (street): 2.5 miles

This morning's run was my last before Saturday's Cow Harbor 10K. As I worked my way through my daily route, I thought about the luxury of waking up tomorrow without the obligation of a run. I pushed myself to a reasonable level, mostly after the first mile, and completed the run close to my normal time. I was happy with the workout but, almost immediately afterward, I started to question whether I've properly trained for the race.

James Street in Northport, otherwise known as "Widow Hill", is Cow Harbor's vindicetis maximus. It's a half mile of steep road that starts close to the two-mile point in the race. In the past two years I've trained on the Cow Harbor course to ready myself for that hill. It's helpful to know at the start of the race that I've run that monster in recent weeks. This year, my training has been less focused. Though I did run some hills over the past few weekends, they pale in comparison to what I'll face on Saturday.

I'm also thinking about my taper. Some might think it's overkill to rest two full days before a 10K. But I like  knowing (even if it's just psychological) that my body is using that downtime to repair and strengthen my leg muscles. I'm debating whether to run through core exercises on Thursday and Friday to give my glutes, quads and hamstrings some extra conditioning. That's an impact free workout that just might make me feel better about my training so far.

Techno-vandalism brings down Emerging Runner

Today's run (street): 2.5 miles

Today is the 11th anniversary of 9/11 and it's hard to believe that so much time has passed since that Tuesday in 2001. Last year I posted an essay about my experience and I thought this morning about how my children, so young at the time, are now in middle and high school. They'll never remember a time when 9/11 was just another day in September. I hardly do now.

Yesterday afternoon hackers brought down GoDaddy, the web hosting company that provides DNS services for the Emerging Runner. Consequently, my site was unreachable for a few hours. It's troubling when people selfishly disrupt technologies that provide services to so many who rely on their websites for income. Emerging Runner isn't a commercial site so, for me, it was just annoyance. But for those with the "Occupy Wall Street" mentality, I'll point out that this type of techno-vandalism mostly hurts the people they claim to represent.

I'm glad to have my site back and very happy to experience chilly, fall-like temperatures on my 4:00 AM run this morning. I ran my usual route and finished about 30 seconds faster than I normally do. It's hard to know how I'll feel on Saturday (race day) but my last two runs have gone well. One more run before I rest.

Finally, as I feared, BH Fitness sent us the wrong parts for our elliptical machine, so after waiting 6+ months, we still don't have a working unit. Here's some advice: If you are considering buying a piece of BH Fitness equipment, I recommend that you consider something else.

For Cow Harbor, it may all come down to this

My running experience this weekend varied greatly, with Saturday's humidity restricting my progress and Sunday's cool, dry conditions providing an energizing atmosphere. I don't have much to say about Saturday except that I knew from the start that it would be a tough run. I covered more distance than the three miles I'd originally targeted, so I was pleased with that small victory. Sometimes you need to give due respect to the heat and try your best, even if you don't run very long.

Yesterday's experience was much different and I knew from the start that I would have a better time on the Bethpage trail. I'm not sure how much credit I should give to the Accel Gel, but both times I've used it I've liked the results. The big hill at Bethpage is no James Street monster, but it's the best I could do as a training resource. It was nice to come up and over the top without feeling like I had nothing left, as I often do when finishing long runs there.

More than once I've had terrible runs on Saturday, followed by a really good run on Sunday. This coming weekend I'm hoping I peak early and feel race ready on the 15th. The two days that I'll rest prior to Saturday may improve my chances, but it doesn't guarantee I'll be at my best. I really hope we have great weather like last year on race day rather than the stifling heat and humidity of the year before. Above all else, weather can make the difference between a good or difficult race experience.

Ever higher on the Bethpage trail

Entrance to new bike trail extension

Friday's run (street): 2.5 miles
Yesterday's run (street): 3.9 miles
Today's run (Bethpage State Park): 6.9 miles

My excitement about Bethpage's bike trail extension continued this morning when I headed over to the park for my last long run before Cow Harbor. I wanted to cover at least 6 miles to prepare for next Saturday's 10K distance. Most of the humidity we experienced on Saturday had moved out the time I started my run this morning. With temperatures in the mid 60's, conditions were near perfect.

I brought along the RooSport that worked well during yesterday morning's run. I was able to verify that the pocket's design did a much better job keeping its contents dry than the SPIbelt. I was curious to see how the front fitting pouch would feel through a longer run.

Instead of starting with the new trail extension, I decided to run the first mile on the old bike trail so I could take on the big hill that comes at the end. I'm used to dealing with that challenge after six to twelve miles of running, so it seemed like a snap this morning. While that was true, I knew I had some more hills to deal with throughout the rest of my run.

I haven't felt great this weekend and I was somewhat concerned about my readiness for a long run. I ate an Accel Gel prior to the start to give me a boost and I think it helped. I got to two miles fairly quickly and remembered the rolling course from last weekend. My plan today was to run as far north as I could on the newly paved trail before turning back.

The first paved section ends at Haypath Road and, with no road traffic, I crossed easily to the continuing trail. This was new ground for me and the trail followed along the line of an adjacent neighborhood before wrapping into a wooded section. The route was rolling, but the elevation was biased in the northern direction. That made me happy because it meant I'd have more downhill sections than uphill when I returned.

I crossed Old Bethpage Rd. and continued until I reached Old Country Rd. I was a little confused at that point where the trail picked up again. It looked like I'd need to cross that busy road and I didn't feel like doing that today. I was at 4 miles by then, so I turned around and headed back. I knew I'd cover close to 7 miles by the time I reached my starting point.

The run back went by quickly despite a few challenging hills near the end. The RooSport fell short of expectations over the length of the run. My Brooks shorts don't have the same stiffness at the waist than some of my other running shorts and the phone-laden RooSport pulled down the front enough to be distracting.

I finished much stronger than I'd expected to at the start. My pace wasn't super fast but it was credible. Now it's time to taper, which means I'll rest on Monday, run on Tuesday and Wednesday and rest again on Thursday and Friday. The parts are finally in for the elliptical (after waiting half a year!) so with repairs scheduled for Monday I may get to use it this week. I'm looking forward to an elliptical session, after going so long without that cross-training option..

Running with the RooSport

Today's run (street) 2.5 miles

TGIF. I have no right to say that because my work week started yesterday, but I'm saying it anyway. It's been a tough week with the kids returning to school and lots of other stuff going on. I skipped yesterday's run because it didn't work with my schedule but I got back to it this morning.

Instead of using my SPIbelt, I tried the RooSport for the first time. RooSport claims that its product provides better moisture protection than SPIbelt and I was curious to see if that proved true. I had concern that the RooSport would feel awkward tucked into my running shorts, especially with a phone inside it, but it was surprisingly comfortable. I really didn't notice it was there.

I went for my run and quickly forgot I had the RooSport but later I thought to check it out of concern that it fell off. That was my own paranoia. The RooSport attached securely to my shorts using a strong magnet and it would not come loose on its own.

I ended up having a decent run and probably could have pushed a little harder than I did. Still, I beat my normal time on this route by almost 30 seconds. I checked my phone after I finished to see if it was wet from sweat. It did seem much drier than when inside the SPIbelt, but it wasn't completely dry. It was a good experience and I plan to use it on my longer runs this weekend.

Ready to run with a RooSport

Front view of RooSport, ID pocket on other side

Today's run (treadmill): 30 minutes

It's been a long time since I've done a post on Runner's Tech Review but that will soon change. This morning I received a product called the RooSport, a pocket that attaches magnetically to running shorts or pants. The idea is similar to the SPIbelt but the RooSport does not attach around your waist while you run.

I've been a fan of the SPIbelt for years and I use it every time I run. I'm curious to see how the RooSport feels compared to the SPIbelt, especially when loaded up with a smartphone and other small items. I'm also wondering how comfortable I'll be wearing the RoosSport on the inside of my shorts. This is the method recommended and demonstrated by Brenda Brundage, who created the product.

We've had a lot of rain over the last two days and that kept me inside for today's run. I considered wearing it on the treadmill, but I wanted my first experience with the RooSport to happen on an outdoor run. I ran for about 30 minutes this morning, fast enough to get my heart rate to the edge of the anaerobic zone. If the weather cooperates tomorrow, I'll use the RoosSport outside on my run. I'll share that experience and will post the full review in a few weeks on Runner's Tech Review.

Labor Day morning run

Today's run (street): 4.2 miles

Today is a Monday that feels like a Sunday because it's Labor Day. Normally my kids would be celebrating having an extra day added to their weekend, but today represents their last day of summer vacation. We have plenty to do today, so I got out early to get my run in, before our day got started.

Although the hot days of August are behind us and the skies were mostly cloudy, the combination of heat and humidity made for uncomfortable conditions. I adopted a moderate pace and followed a different than normal route. I covered a little more than four miles, providing a nice start to this week's mileage total.

I've exceeded 20 miles in each of the last two weeks and hopefully I'll do that again this week. Tomorrow is a vacation day for me, but with some scheduled work calls, a doctor's appointment and the process of getting my son and daughter ready for their first day of school, it doesn't feel much like a day off. I plan to take Tuesday as my rest day and I think I'll need it. I haven't taken a day off from running since last Monday.

A big surprise at the Bethpage bike trail

Northern entrance to (now paved) trail extension

Today's run (Bethpage State Park): 5.25 miles

Years ago I was at a management off-site in Montauk where we stayed at a well known resort. We arrived late at night and went directly to our rooms. I was pleased to see my small, but cozy, bedroom, with a modest sized window that looked out at the ocean. I went right to bed so I'd be ready for the early morning meetings.When I woke the next morning, I was astonished to discover another room, twice the bedroom's size, with floor to ceiling windows looking out to the beach.

I had a similar experience this morning at Bethpage State Park, where I planned to run the bike trail. I knew that they were doing work on the north end of the trail but I didn't really understand what it meant. I decided to explore the paved path that led to the golf courses, since I'd hardly seen them in all the time I'd run there. I first encountered a group flying large, remote control planes over the open field. Very cool, but I couldn't stop to watch.

As I made my way deeper into the golf course, I was interrupted by a groundskeeper who told me I couldn't run there and that I needed to head - immediately - to the bike trail. When he realized I wasn't trying to break any rules he got nicer and explained the risk of flying golf balls. I turned back to where I began, and decided to explore what looked like a small section of newly paved trail that extended off the driveway leading to the parking lot.

I saw other runners running there and became curious how far this path would go. I expected the answer to be a few hundred feet, but then I saw a runner turning around and heading the other way. I was amazed. Clearly the trail went far enough to be worth a return run. I followed the paved path and saw that it continued past my line of sight. A teenage runner coming from the other direction asked me how far the path led. I asked him the same, and he said "about 20 minutes." Hmmm.

This new trail was like a gift. I read that they were extending the bike trail at some point but I didn't think they'd actually done it. Soon I realized that the patch of paved road that I'd recently encountered after coming to the end of a dirt path was part of this trail. Like the rest of the bike path, this extended portion was rolling, with some tough hills along the way.

I followed the extension to where it ends on Haypath Road. I saw that I could cross the street and pick up the Trailview path that runs all the way north to Cold Spring Harbor. Instead of doing that, I decided to head back. I didn't bring any water and I was beginning to feel overheated. The hills were no kinder on the way back but I welcomed them. When I got to the end, I doubled back another half mile for the distance and ended up covering 5.25 miles altogether.

I'm very excited about this new extension for many reasons. First, I now have another option to run at Bethpage when I don't feel like doing the usual bike trail. Second, the new bike trail section has numerous exits into the wooded trails that provide options for combining trail and road running. Third, I can now explore Trailview as it goes further north. Theoretically, I will be able to run from Bethpage into my own town. With a few busy streets in the way that might be too good to be true. But you never know.

Stillwell Woods fun: toughest trail run this year

Finally found my way across the full preserve

Today's run (Stillwell Woods): 4.5 miles

Now that the Barclays is over and Bethpage is open once again, I considered heading over to run the bike trail. But I changed my mind on venue and opted for Stillwell Woods instead. A few miles on the wooded trails is a great way to free your mind, body and soul. That is, if they don't beat you to a pulp.

I usually run the same route at Stillwell that starts on the main trail and follows north, and then east, before looping back around to the trail head. I usually run it twice, for a distance of about 4 miles. I like this course because it's primarily hard packed single-track, with a few rocky and hilly sections thrown in. The challenge of getting through this loop is moderate at best, but it's a great experience running among the trees, plants and animals.

This morning's Stillwell run started like usual, and I followed my standard loop until I turned left instead of right, just before the one mile point. This little change quickly turned the dial from easy to difficult. Instead of my familiar paths, I soon encountered the first of many sharp inclines up rock, scree and sand, followed by numerous steep, carved out, drops.

Technical trail running can be fun provided you're wearing the right shoes and have an understanding of your course. I had neither, but I did my best. Thinking I'd run my usual route, I wore a pair of road shoes that performed remarkably well in most circumstances, but barely had enough bite for some particularly steep inclines.

I'd brought a compass and that was very helpful for navigating across the entire preserve. Still, I didn't know what to expect from minute to minute. The route I'd taken brought me up and down, with almost no level sections between the one and three mile points. I began to get frustrated by this pattern because I didn't know what lay ahead. I only knew it would be tough running.

Just when I started to think about taking a break or even walking some of the difficult sections, I found myself on a familiar trail that's part of my normal route. Knowing the worst was over, I happily followed my way around to the trail head and ran the paved drive almost to the street and back. 

Ups and downs through the first three miles

What started as a routine Stillwell run turned out to be an exhausting hill workout with lots of technical terrain and obstacles. I needed to duck under or leap over a lot of stuff and all that sand was irritating. I was proud of myself for meeting every hill challenge head on. But I did need a mid-day recovery nap to get my energy back, so I could play soccer with my daughter.

Tomorrow I'll go back on the road again. Perhaps I'll head to Bethpage for six miles or so on the bike trail. After today's run, that might feel easier than usual.

A surprisingly decent time for a low PE run

Today's run (street): 3.6 miles

My Labor Day weekend started this morning, so I had an opportunity do a weekday run longer than my usual, time-constrained 2.5 miles. It's actually 2.53 miles, but who's counting? Well, I am. An extra three hundredths of a mile drops my average pace by six seconds per mile at that distance.

I targeted about 3.5 miles for today because it's a nice bump up from the 2.53 on a weekday, but short enough to get it done quickly. Although I didn't need to rush out the door when I returned home, the rest of the day was booked and I wanted a chance to relax before I headed to my first appointment.

My run was interesting. It was hot by the time I got outside and I wasn't really in the mood to push hard. I used only my heart rate as a way to gauge my performance and adjusted my speed to get into my targeted zone. Even while my pulse increased, I didn't feel like I was working as hard as I did last week, when I broke 9:00 four mornings in a row.

I ended up completing this run in the mid-9:00 range. Going only by perceived effort (PE), I expected that number to be 20 secs/mile slower. I was pleased with that performance on a hot day when I wasn't really working that hard. My average HR for the run was at the lower end of the anaerobic range. That tells me I have more on tap than I've been using on most runs.

Like the DJIA, running performance has its gains and losses

Today's run (street): 2.5 miles

My performance gains of last week have given way to more moderate results this week. It's almost like a market correction where I've found myself dropping speed, but still holding some gains. I wonder if my ups and downs of running ever synchronize with the Dow. That would be an interesting investment strategy.

Tuesday's performance was hard to measure because I don't fully believe the numbers that I see on the treadmill. If I were to go by heart rate, I'd say that it was a credible run. Yesterday I did a street run and used my heart  rate monitor to guide my level of exertion. It became clearer to me how my perceived effort affects my speed. I didn't break 9:00 on Wednesday, but I came close.

This morning was a different story altogether. Running felt harder than the day before, and my stride did not feel fluid. I just wanted to get through the run so I could relax for 15 minutes before starting the rest of my day. Although it didn't feel like I was slacking off too much on my pace, my overall time was almost two minutes longer than yesterday, along the same route.

I expect to get out a little later and go a little longer tomorrow because it's a day off. I'm looking to experiment further with the relationship between heart rate and speed. I also need to get some hill training in so that I can be somewhat ready for big hill at the Cow Harbor 10K in a couple of weeks.

My most important decision in the last four years

Four years and many miles

Today's run (street): 2.5 miles

This past weekend I realized that it's been four years since I took the results from my annual physical as a call to action. At that time, I weighed thirty pounds more than I do today. My cholesterol was very high, as were most other indicators. These results were no surprise to me at the time. I had become sedentary and, while I maintained a decent diet, I did not do a good job of regulating portion sizes or sugar intake.

With a wife and two young kids who depended on me, I could no longer ignore the truth. I got off the phone after speaking to my doctor's assistant and told my wife that I was going to change. I don't know if she fully believed me, but she supported my intention. My wife has always been active and she suggested that I use the treadmill in the morning before work and to really watch how much snacking I did after dinner.

In August of 2009 I began to walk, first on the treadmill and, on weekends, around my neighborhood. I pushed my walking pace and, within weeks, I was throwing in some short running segments. It took a while before I could comfortably run a mile but by the end of September I was doing that. By October, I had given over from being a walker to a full time runner.

Along the way, I lost those 30 extra pounds and by year's end, even more. Running is easier the less you weigh. It becomes more interesting when you can track your progress with devices that capture your speed and distance. I made a lot of progress in the first six months after I returned to an active life. Four years later, I'm doing even more.

This is the 1,300th post I've done on the Emerging Runner. I started the blog as a personal journal to help me record my experiences and share them with others. I wondered how long I would be able to maintain the discipline of running every morning and whether I would tire of the routine and the work that comes with it. But four years later, I feel exactly the same as I did the day that I completed my first continuous mile.

Finally using my HRM (with good results)

Today's run (treadmill): 25 minutes

I knew it would be rainy this morning so I planned to do a treadmill run. I finally got around to setting up my heart rate monitor on Sunday and linked it to the Garmin, so I had that to play with. With the rain outside, it was very humid in my guest room. I put the fan in a fixed position and aimed it directly at the front of the treadmill. This reduces the heat, but the forced air causes dryness in my sinuses and throat.

It's been a long time since I've used an HRM. The treadmill has grips that allow you to capture your current heart rate, but read time takes a while and it's awkward to run that way at speed. The Garmin is much more convenient and it monitors in real time, providing important information as you run.

One important thing I learned was that my usual routine on the treadmill did not tax my heart as much as I'd thought. Since I despise this method of running it always feels hard, at any speed. What I thought was a good workout pace turned out to be on the threshold between the recovery and aerobic zones. To really get benefit I needed to push myself into the anaerobic zone (between 80-90% max HR).

I watched my heart rate as I increased the treadmill's speed and was surprised how hard it was to bump my HR higher on the aerobic zone. It may have been psychological, but I found it easier to sustain paces below 9:00 after seeing that my heart rate was still below 80% of max. I ended up running faster than I usually do on the treadmill without feeling much fatigue during or afterward. I'll be curious to see what kind of numbers I see when I take it to the streets tomorrow.

The crossroad of speed and volume

My overall time at last May's LI Half Marathon was 2:08, which translated to a 9:49 pace. As race paces go, that was fairly slow (even for me). But my 2012 finish time improved almost 14 minutes over the year before. I would have liked to break two hours on the half, but my stretch goal for that race was to break 2:10, and I did that.

To prepare for this year's race, I'd looked at the challenge of running the half marathon as one of stamina, not speed. Interval training can be an effective way to prepare for a 5K, but I knew that the only way I could achieve a credible time for the half would be to train for distance. A lot of distance. Between mid-March and and May, I spent almost every Saturday morning at Bethpage State Park, doing progressively longer runs until I was satisfied with my conditioning.

This volume training was the key to managing my effort across more than two hours of continuous running. There's obviously a big difference in training for a 5K versus a half, but what about a 10K? A 6.2 mile race is double a 5K, but not quite half of a half. There's speed involved, but also enough distance so that endurance can become an issue.

For my upcoming 10K, I've decided to focus on pace during my shorter runs, but work primarily on volume and hills during my longer weekend runs. Hopefully, both strategies will meet somewhere in the middle to allow me to run my best at Cow Harbor.

Living with GPS tracking errors

Today's run (street): 6.8 miles

My GPS watch always shorts distance, usually by about 3%, but this week the margin of error has been closer to 5%. If the GPS was more accurate, I could know my true performance as I ran. The Garmin FR210 does give me a map of where I ran, and this is useful when I run in unfamiliar places or forget which streets I covered.

An alternate to GPS tracking is the foot pod that, when calibrated, is far more accurate.  Its downside, besides the need to calibrate, is the lack of course mapping and the need to affix it to your shoe. Some shoes, like the Saucony Hattori, don't have laces and, therefore, cannot be easily used with a foot pod.

My plan for today's run was to go out easy and stay that way for five to six miles. I pushed hard on my runs during the week and I tried to do the same during yesterday's run. I figured I'd earned the right to ease up on my pace and enjoy the experience today.

Things started well and along the first mile I wondered how long it would be before I broke a sweat. I also knew that runs like these are deceptive, often becoming much harder after a few miles. After 25 minutes I was certainly sweating, but five minutes later I began to feel energized again. I spent half of the run going around the neighborhood that sits directly to the south of mine, and the other half going around local streets.

As I got close to home I saw that I was nearing six miles. I decided to detour north rather than follow my usual roads, in order to get some extra distance. That change added a half mile according to the Garmin. After plotting my run on Gmaps, I saw that I'd actually covered 6.8 miles. If I knew I was that close to seven, I would have run another quarter mile before calling it a workout.

Even though I took it easy, by the end it felt very hard. I was glad to exceed 6.2 miles, which I'll need to do as often as I can before the Cow Harbor race in mid-September.

A good effort but the clock doesn't lie

Today's run (street): 4.3 miles

I had an early appointment that delayed today's run until mid-morning. The temperature at 10:00 AM was a reasonable 77°, but the sun was making it feel warmer than that. My plan was to go out fast and maintain the speediest pace I could, for as long as I could. I followed a route that would take me up and down the streets that run north of my house, and then head further south to round out the course.

I decided to check my watch at the half mile point to see what the Garmin was displaying for pace. The watch said 8:52, which seemed about right, and I figured that I could maintain that for 40 or 50 minutes. I didn't feel too overheated and I thought I was in for a run that was close to, or below, 9:00 per mile.

As it turned out, I began slowing down after passing the first mile. By the time I reached three miles, I saw that my pace was 30 seconds off my targeted range. It bothered me that my performance did not match the level of effort that I was putting into the run. After downloading the Garmin and correcting for distance errors (the GPS accuracy has been abysmal this week), I saw that I'd run the first mile in nine minutes, but my pace had crept up into the mid-nine range until improving near the end.

The combination of heat and effort prompted me to cap my run at 40 minutes, for an overall pace of 9:23. I was disappointed with that result because I felt I'd pushed harder than normal. I wanted to break nine minutes, but I don't think I did all that badly. I'm planning to go longer (and probably slower) tomorrow. It's okay really. After the past week's running, I know what I'm capable of doing.

The secret to running a faster pace: trying

Pacing well, at least for now

Today's run (street): 2.5 miles

It's interesting to see how a little extra effort can result in much better performance. Once again, I beat the 9:00 threshold this morning with a run that took exactly the same time as yesterday's. Running this way is not easy by any definition, but I haven't been going all out as I'd do in a race. On average, I'm probably registering a 3 (out of 5) on the effort meter. This week it's been closer to a 4.5.

It's no miracle that my performance this week has improved about 6% over my average for weekday runs at 4:00 AM. Back in 2009, I would beat 9:00 paces regularly. That was probably due to going out with the expectation that I'd run as fast as I could manage. I also used to monitor my pace as I ran, whereas now I only look at elapsed time on my Garmin.

The pace I ran this morning felt a little harder than it did on prior days, and I wondered if I tried to put too many hard runs together in a row. But even so, it wasn't an all out effort. I recovered quickly after I finished, with no residual effects later. I'm going to work on base tomorrow and probably won't be seeing the same pace that I've been able to achieve this week. I do hope the higher cadence and harder running I've been doing will help me when I run greater distances this weekend.

The significance of breaking a 9 minute mile

Cow Harbor aspiration

Today's run (street): 2.5 miles

I had two reactions after I finished today's run. The first was the happy acknowledgement that I'd completed three consective runs under 9:00 a mile (8:55, 8:50,  8:57). Not so hard for many, but a big deal for me. The second reaction related to how hard I'd worked to barely break nine minutes today.

I remember reading a post on the Runner's World Loop a few years ago that defined a "runner" as a person who paced below 9:00/mile. This person declared anyone who ran slower than that to be a "jogger." I rejected that assertion, as did many others through their comments. But since then I've always thought about sub-9:00 runs as a validation of my running fitness. A high percentage of my runs fall into jogger territory, so I feel encouraged with this week's performance.

The reason why I've put more attention toward my speed is that Cow Harbor is weeks away and I want to be prepared to run it competitively. My PR pace for a 10K is 8:48 but that race was run on the flat roads and boardwalk of Long Beach. My hope is to beat my PB for Cow Harbor, which means a pace of 9:12 or better. If it wasn't for the James Street hill, I'd be feeling confident about my chances for doing that. As long as I'm beating 9:00 on my training runs, I know I'll have that possibility.

Ayn Rand as my running coach

All things in life relate to running

Today's run (street): 2.5 miles

I sometimes experience good runs that are followed by a mediocre workout. It's almost like a tease. When I think I've made a breakthrough, I'm often disappointed the next time I run. There are many reasons for that, but I'm beginning to believe it all comes down to self determination. As Ayn Rand has put it, "The question isn't 'who is going to let me'; it's 'who is going to stop me'."

While I'm not an "Objectivist", I do agree with the idea that we control our own chances for success. That was my mindset this morning when I took off on my run. I was determined to prove that yesterday's measurable improvement in performance wasn't a random event. Just for a change, I wore the Spira XLT's, and as I moved along the first section of my route, I noticed how similar it felt to yesterday's run.

It's easy to run lazy. The fact that you are running will boost your self esteem regardless of how hard you're pushing the pace. I often fall into that trap, telling myself it's okay that I'm running slowly because it's really all about doing the workout. Instead of pushing myself hard enough to achieve my pace goals, I often default to running at a speed that feels comfortable.

Today I ran my regular route ten seconds faster than yesterday and a full three minutes faster than I usually cover it. That's two in a row. Ayn Rand would be pleased that I rejected the easy path and pushed myself once again to good results. But if she was my running coach, her expectations would go far beyond this level of improvement. For now, stringing two good runs together is defining success for me. Hopefully tomorrow I'll make it three in a row.

Successful start to Cow Harbor training

Once again, it's about speed

Today's run (street): 2.5 miles

Nothing forces a runner to pay attention to their performance as much as a race. Once the registration is completed, the clock begins its countdown to the starting gun. A good outcome is never assured, but preparation is always key. With a click of the submit button on Active.com, I've once again committed to training for the Great Cow Harbor race.

Every race I run fits within an easy/hard continuum. On the easy end are 5K's that are run fast but over within a short time. The hardest effort I've experienced over the last couple of years has been the half marathon, mostly due to covering so much distance with race pace urgency. In between are runs between 4 and 6.2 miles, some harder than others.

Of these races, Cow Harbor is the biggest event by far. With over 5,000 runners invading Northport, NY, on a Saturday morning, it's a race experience that stands out above all others. The energy of the morning, as runners gather at the Laurel Avenue school, grows by the minute as participants move into their designated wave sections. The chill in the air gives no clue to the scorching heat we'll experience along the course.

This morning's chilly air gave me the spark to start my run fast and keep the pedal down until I'd finished. Everything clicked and, despite my harder than usual effort, I felt completely comfortable pushing my speed. I ended up finishing my run three minutes faster than I did last Friday. It was the first time I broke 9:00 per mile in months and I can't remember the last time I did it at 4:00 AM.

One run doesn't make me ready for Cow Harbor, but I'm happy with my performance on Day One of training. I have three weeks until I taper and rest and I'm hoping to continue to perform like this. Lots to do before September 15th, but I'm off to a good start.

Committed to Cow Harbor 2012

What made skipping Dirty Sock so easy for me this year was that I put off registering until it was one week before the race. Since I had no financial obligation, I made my decision to stand down without needing to consider that I'd already spent the money. That worked great for this past weekend, and I'm still happy with my decision. Still, I didn't want the same thing to happen next month so I signed up for Cow Harbor this morning.

With so many people running this race, the Cow Harbor organizers ask registrants to list their expected finish time. This is so runners can be placed into appropriate pace groups, called waves, at the start. It makes perfect sense and I always wonder if I'm under or overestimating my performance when I do that. Last year I finished in around 57 minutes and I'm hoping to do as well this year. I've run 10Ks faster than that, but not ones that have a hill as challenging as James Street.