Racing to run

As I’ve mentioned in past postings, my morning routine is planned with a similar precision to a space shuttle launch. The alarm goes off at 3:55 AM, I pour my coffee at 3:58, turn on the treadmill at 4:00, put on my shoes and running clothes by 4:05, set up the HRM by 4:06, consume half my Special K bar and 1/3 of my coffee by 4:08 and start my warm-up by 4:09. This gives me approximately 20 minutes to run two miles at target pace before ending with a couple of minutes to cool down and reduce my heart rate.

Some mornings the routine goes flawlessly and I sometimes gain a few minutes and run a little longer. Other times, like this morning, time went by in fast motion and before I had even started my run the clock read 4:12. This left me with only 15 minutes to run, forcing me to get up to speed faster than normal. I ended up running 15:00 at 9:05 (1.66 miles). I thought I’d actually run faster than that but the Garmin doesn’t lie (unless I calibrate it wrong). Making things worse was my treadmill display that sputtered out after about 5 minutes. That left me no easy way of monitoring progress and performance short of toggling through my watch settings as I ran. That’s fine once or twice during a run but repeating this process soon becomes tedious.

It seems like 9:05 is my new default pace, quicker by far than my average daily performance in 2008, but again, not under 9:00. I could blame my cold and my leg soreness for being off goal pace but I know that I could have pushed harder than I did today. I’m working from my home office tomorrow which will give me an opportunity to run a little later (possibly outside) and longer. If I keep it under 3 miles tomorrow I won’t be happy with any pace above 8:59.

Powering through

My head cold continues and yesterday afternoon I paid a visit to my company’s medical department. The doctor, who I’ve known for years, said “Sorry, but I don’t have a cure for the common cold.” I told him it wasn’t the cold that was bothering me, I actually wanted his take on my running injury. He had me lie on the table and tried to isolate the problem but it was inconclusive. He didn’t understand why the pain was intermittent and why the discomfort went away after I walked or ran on it. He then suggested that I see an orthopedist and though he warned me not to overdo it he didn’t tell me to stop running.

This morning I was determined to run and, despite some sneezing and coughing I got on the treadmill for what I’d accepted to be a low impact run. Once I got moving my leg started feeling better so I turned up the speed. I ended up running 1.75 miles at a 9:05 pace although the last two thirds were probably faster since I’d run the first six minutes at about 9:50/mile. Since the run I feel pretty much okay. It wasn’t a long run today but I needed to show my cold who’s in charge.

Core for the common cold

As strange as it may sound I was happy to see that my sore throat was just the first sign of a cold. Having had a few bouts of strep in the past I take sore throats pretty seriously. Colds are annoying but relatively easy to ignore. I don’t consider them an excuse not to exercise and, in fact, I believe that powering through a cold actually speeds recovery.

My biggest concern right now is an increasingly noticeable stiffness and pain in my upper right leg. As I have mentioned, this discomfort disappears while running but it always returns. I should be icing it more but it was a busy weekend. Yesterday we returned to the track and I ran a little more than 3 miles at a 9:07 pace. I purposely held back to protect my injury but I did push the speed a few times. There was another runner on the track who was pacing (I’ll guess) around 7:30/mile and I didn’t want him to lap me.

This morning I decided to skip both running and elliptical and instead did 15 minutes of core followed by 10 minutes of upper body work. That was a great combo. My leg felt a lot better and I got my heart rate up a little. I’m thinking of doing core again tomorrow before running. It seems to help but it will cut into my running time. I guess I’ll just have to run faster!

36 darn seconds

This morning, with the temperature in the high 20’s, it didn’t feel like much like spring. My right side soreness was better but I was concerned about aggravating it with a long run. As I prepared to start, my next door neighbor (a CPA) was preparing to head to his office to deal with corporate tax filings. He said he’d rather be running than doing that (who wouldn’t?) and I said “Cheer up April 16 isn’t too far away.” For me it was time to run.

I decided that I would run a minimum of 5 miles today and planned my route on Gmaps to help me stay focused on the goal. My secondary goal was to stay under 9:00 per mile but I knew that running 5+ miles puts me at the edge of my distance capability. I set out on a road with an incline to help me get my heart rate up quickly. It was cold and I dressed with a minimum of layers anticipating that I would build heat as I ran. I was running an 8:55 pace as I reached my first mile and I started wondering how long I could maintain that rate. As planned, I cut over to neighborhood #2 and did the big loop. Not being fully familiar with that area I made a navigation error and I ended up running about half a mile away from my planned exit. I didn’t mind, miles are miles no matter where you take them.

Around the 4.5 mile mark I started struggling and I had another episode of hyperventilating. What was different about this is that I was relatively far from home when it happened. Like last time, I simply held my breath and ran until I felt rebalanced. I took a couple of slow deep breaths and soon returned to my previous rhythm.

I’ll admit that the last leg, about 1/3 of a mile, was a struggle and I tried to generate as much speed as I could but I knew I was near my limit. I Gmapped my actual run and compared it to the Garmin and was happy to see that they were within .01% of the distance of 5.22 miles. I calculated my overall pace at 9:07 which meant that if I’d run 36 seconds faster over 47 minutes I would have averaged 9:00 min/mile. Later I’ll look at my split times to see if I’d held pace under 9:00 for the first 3 miles which was the original goal.

I’ll decide tomorrow whether I’ll try for another long run or shorten the distance and turn up the speed. My injury seems no worse for the long run and I’m hoping the pain doesn’t return later.

Spring training

Today is the first day of spring, marking the end of my second season (fall and winter) as an emerging runner. I’m pleased with the progress I’ve made in the past six months and now, with 29 days to my first race, it’s time to get serious about training.

It’s interesting to think about the benchmarks I’ve passed since last September. Not long ago I struggled through my first mile and I’m proud to say I can now run more than five. My training approach has been anything but scientific but I like the way things have worked out. Back in December, when I signed up for the May 5K race, I was barely able to run three miles. Before I do that race I’m facing a 4 miler in April with no concerns about the distance. The goal now is pace and that’s where the training comes in.

Two of my running advisors, CK and CMC, have given me great guidance on using speed work to increase fitness. I read blogs from other runners who are much more disciplined about these methods and this explains why they run 6 and 7 minute miles and I don’t. I just like to run and by integrating some faster paces into my normal pacing I’ve been able to improve my overall pace. I’ll start stepping that up this weekend and will try again to run over four miles at under 9:00 per mile.

This morning I achieved that pace at half the distance, running 2.01 miles at 8:46 per mile. I felt like I could have sustained or even exceeded that pace if I had time to run a couple more miles. Some of that comes from conditioning and some comes from the fact that I only did upper body exercise yesterday. I’m beginning to appreciate rest days as a training tool.

Training to train

This morning I did a 5 mile neighborhood run, including about 1.25 miles running around neighborhood #2. Considering the length of the run I am happy with my 9:17 overall pace although my target was to average under 9:10/mile and my goal was to stay under 9:00. I guess you could call that a stretch goal. Maybe if I did more stretching I’d have made it.

The Garmin 50 pulled a new trick, about 3 minutes into my run I noticed that while it was happily reporting time, speed, cadence and heart rate the distance stopped incrementing after .08 miles. I couldn’t figure that out so my only recourse was to stop the timing and restart. Somehow it took that action as starting a new split but at least the Garmin was recording distance again. I felt really good throughout the run (gee maybe there is something to taking rest days) but in the final minute I experienced a reaction where I suddenly had difficulty breathing. This was hyperventilating and not related to being out of breath from the run. I had a similar experience the last time I ran over 5 miles. I recovered by forcing slow breaths and holding my breath until it re-regulated. I’m sure it’s psychological. I just hope it doesn’t continue to happen.

The reason I’m training hard this weekend is that I’m participating in a group run next week that’s been organized by Adventure Girl to start her team’s training for the Ragnar relay race in May. This relay is a 175 mile race from Woodstock to the Bronx with 12 members who each run three legs. I’m not participating in that race but I’m excited about this training run because it will be the first time I’ve run with people in over a decade. I have to admit I’m a little concerned about carrying a conversation while running but I’ll do my best. My other concern is that I’m going directly to the office afterward without a shower. The run, which takes place in Central Park, is only 4K so if I under dress I might be abe to minimize the amount that I sweat.

I’m going to try some trail running tomorrow to take advantage of the weather and to exercise some different muscles.

Just don’t call me a @#$%! jogger

This morning I saw a news story where a reporter was interviewing two women who were out for an early morning run. Superimposed on the screen were their names and the word “Joggers.” It made me laugh to see that. These women were serious looking runners but the word jogger evokes, in my mind, someone dressed in a designer sweatsuit and headband, holding a bottle of Vitamin Water, listening to an iPod and bouncing along at a fast walking pace. Someone recently asked me if I was “still jogging” and I was tempted to say “I don’t jog, I run.” Instead I just said yes because to most people it’s the same thing.

So what is the real definition of running vs. jogging? Does it have more to do with speed or attitude? I read one view that the difference between the two is an entry form. Meaning a runner races and a jogger just jogs. I’ll debate that since I know at least one serious runner who never races. Another view was that joggers run 9+ minute miles and runners run faster than that. That seems like a fairly arbitrary distinction. In that case, with an average pace of about 9:15 I’d be an aspiring – not emerging – runner. I’m not going to change the name of my blog so I’ll have to reject that definition.

This morning I (ahem) jogged 1.76 miles in 16:02 for an overall pace of 9:06. Since I have already filled out a couple of entry forms I’ll accept the first view and say I had a pretty good run.

Speeding along

I have 39 days to train for my 4 miler in April. For those who have run many races my countdown is probably a little dramatic but it’s my first race since returning to running. I was looking at my run data this weekend and noticed how my average pace time has improved between September and today. I look at the improvements over the first five months as organic, that is, directly related to improved fitness and weight loss. Obviously, running with less weight and better Vo2max capability will yield better performance. My pace history describes a Pareto curve with earliest times in the low 13:00 range, following a steep decline until it plateaus at around 9:50. Last month, with the encouragement of some of my more experienced running friends, I started integrating faster segments into my regular runs. As I’ve become more comfortable with faster paces I’ve held them longer and the result has been to move down that curve even more. My average pace for February had improved to about 9:30 and over the past two weeks it’s closer to 9:15. This weekend I did my two long runs below 9:10 so I really like the direction,

This morning I decided to push the pace to the edge of my comfort zone and after starting around 9:30 I quickly turned up the speed about 8% and ended up running 2.05 miles at 8:46. Needless to say I’m happy with that performance. What I don’t know is how well I’d have done if I had time to run another 2 miles. This weekend I almost broke 9:00 for 4 miles but almost doesn’t count. Well it counts a little I guess.

Garmin 50 – illogically lovable

A number of years ago, on vacation in Paris, my wife and I were completely puzzled by the challenge of crossing the street to visit the Arc d’Triomphe. If you’re not familiar with its location, the building sits in the middle of a traffic circle off the western end of the Champs-Élysées. It was clear that crossing that traffic would lead to instant death by Renault and yet we saw a number of people milling around the Arc. After some searching we saw a small sign indicating an underground passage that led to the center. It certainly wasn’t obvious to us but in retrospect it made perfect sense.

The Garmin 50 reminds me very much of that. Before the Garmin I used the Nike+ Sportband which had less complexity but also less features. It was simple to set up and use, basically it had two buttons that controlled everything and good documentation to show you which ones to push. The Garmin has four buttons that seem to do different things based upon the mode of the watch that can be switched between time, training, interval timing and history. The simple idea of using it as a stopwatch took me almost three weeks to master. The process to do this is simple but the lack of instruction in the manual made it maddeningly difficult. As I use the watch I’m beginning to better understand how the sequence of buttons makes things work. It’s still a little annoying when the display says “press OK” when it really means “press the View button” but now, after experimentation, I know to do this.

Of course now that I have gained some comfort with its operation I am thrilled with the data it collects and presents. The combination of pulse rate, speed, cadence, time and distance (accurate to about .03 miles now that I’ve figured out how to calibrate it) and the Garmin Connect website (that collects and reports the information) are really good. There are dozens of things I’d do differently in terms of functionality and user interface but in the end, it works. However I do wish it calculated pace on the watch, not just speed in MPH.

This morning I ran 4.06 miles at about 9:05/mile which didn’t make my target of staying under 9 minutes per mile, but I fully accept it as great progress. It was about 43 degrees when I went out for my run. I only wore a base layer plus a long sleeve technical jersey under a lightweight windbreaker. I was comfortable throughout most of the run but I got very hot near the end. I didn’t make either my speed or distance (8 total miles) goals for this weekend but I am very happy with what I’ve accomplished.

A miss is as good as 3.6 miles

I came within 1% of my goal of running over 3.1 miles at 9:00/mile this morning, completing a 3.57 mile run with an average pace of 9:03. The chart above from Garmin Connect illustrates the technique I used throughout the run where I alternated between my normal pace (~9:20) and a speedier pace. I was pleased to see that the slowest pace that I ran today was 9:28 and the fastest was 8:24. Overall I’m 99% satisfied with the run. The temperature was around 40 degrees when I started but it rose quickly and, coupled with direct sun, I became very hot. I made the mistake of wearing too many layers. This worked great for the first eight minutes but I found it to be a burden over the next 24. At around 2.75 miles I really started feeling taxed which surprised me since I didn’t run on Friday and I’d had more than my usual overnight rest. I’ll blame the hot weather and the faster pacing. After hitting a wall so soon into the run I am slightly concerned that my conditioning isn’t where it should be. But I did recover pretty well and my new focus on speed should help that going forward.

I was also glad to see that my large toe, although still tender, did not cause me any problems during the run. I’m trying to decide on tomorrow’s run strategy: 1. Try again to make the “3+ mile, sub 9:00” goal, 2. Aim for a shorter run but make the target pace even faster or 3. Accept today’s 99% success and just go for distance on Sunday.

All suggestions welcomed.