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.