Boston is back and back to the track

Tracking Marathon friends on BAA.org

Today's run (track intervals): 
6 x 400's plus 1 mile warm up/cool down

Yesterday was a big day for running, with the 118th Boston Marathon taking place (thankfully) without incident. Both SIOR and TPP's sister ran great races, and it was fun to watch their progress using the tracker on the BAA website. How perfect that Meb Keflezighi won the men's race. I'll never look at Skechers the same way again. I was disappointed when Shalane Flanagan dropped back after leading for so long, but she scored an American course record while finishing seventh overall.

The marathon would have been great inspiration for a Monday run, but I held to my rest day to ensure I'd recover from Sunday's long distance. Speed work was on the calendar today, and since the schools are closed until tomorrow, I went over to the track to run intervals. I've done weekly speed workouts all throughout my half marathon training cycle, but I hadn't done a single set on the track until today.

The temperature was 55° when I arrived at the high school. Although I was wearing shorts, I was concerned that having two top layers would cause me to overheat. With the 6 MPH wind, it felt chilly enough to keep them both on the entire time. The high school cross country team was assembled at the southern end of the track infield and I wondered if my workout would happen alongside a crowd of much faster runners.

My HRM now takes 5 minutes to sync

It turned out that I didn't need to share the track at all. The coach was having the team run laps barefoot on the grass, first slowly, then at speed. While that was happening, I started my workout with two laps around the track at around 8:50/mile followed by 6 x 400's at 8:00/mile. I finished with a half mile cool-down that I ran at a mid-9 pace.

It was good tactical workout. I probably could have added another two quarters, but I wanted to keep it light today. I'll try to cover much more distance tomorrow. With the race on Sunday, I'm not sure what to do about my weekend long run.

Barely okay, but better than the last one

Ready for some speed play

Today's run (street): 3.4 miles

My definition of an okay run has changed a lot in the last couple of weeks. If not for the intervals I ran on Tuesday, I'd be convinced that I've lost my ability to run at any speed but tepid. Wednesday was a difficult experience, made worse by the wind. I did manage to get through my five miles that day, but it was rough. I hoped today's three miles would be easier, and they were. It was...okay.

The warmer temperature this morning seemed to help, and I improved my pace by over a minute compared to Wednesday's. I was supposed to do today's workout at half marathon race pace, but I fell short by about 35 seconds per mile. In truth, I wasn't going for speed as prescribed, I really just hoped to have a decent experience.

I think about my friends who frequently run long distances at paces that I cannot match (except when I'm running 400's and, in some cases, 200's). Are they working that much harder than me? Probably, but I suspect it also has to do with being better disciplined about their workouts and putting in the necessary miles. I understand that running 18 to 20 miles a week is not going to build enough endurance get me to a competitive state, but I don't think I can fit many more into my schedule.

I knew I wasn't pushing as hard as I could today, but it wasn't a leisurely effort. There's a certain amount of energy that I'm willing to expend during a race that I seldom bring to my daily workouts. I'm always concerned about running out of energy on a training run and I tend to hold back to conserve what I have. Tomorrow I plan to add some fartleks (Swedish for "speed play") to introduce interval level running into a continuous run. If I run out of energy, I can always take down the pace. Or take a recovery rest on the sidewalk.

The fashion-challenged runner

Sorry girls, but I'm married

Today's run (street): 3.4 miles

The only thing that travels faster than light is communication between women. I know this sounds sexist, but hear me out. This morning I went out for my 3 miler and this is what I wore (see above). I know, I know, but my daughter wasn't there to give me a her look that combines horror, shame and pity, followed by a polite suggestion that I change into something less embarrassing. I dressed for the weather - the temperature was 45 degrees (39° with wind chill) and didn't give a thought about how I looked.

I felt good, even better than yesterday, so I felt I could push my pace a little harder. I ended up running a half a minute per mile faster than on Wednesday. A scan of my Garmin data showed I ran the same cadence, but my stride length today was .2 meters longer. Doesn't sound like much, but it's almost eight inches. Multiply that by 4,000 or so steps and you cover a lot more ground. Apparently it's 27 seconds per mile more.

I loved the run and being outside, except for when I ran directly into the wind. That was unpleasant, but at least it wasn't freezing like yesterday. I planned for only three miles, but my route took me beyond that. About two miles into my run I took a right and spotted a car that turned in after me on the same street. The car continued and parked in a driveway a few houses north. When I passed the house the driver was just getting out of her car and I saw that it was one of my wife's good friends. I said hello and continued on.

When I got home my wife told me that she heard I was spotted running in the neighborhood. It was then that I saw myself in the hallway mirror and realized that I was dressed like a complete dork. My wife's friend didn't mention my fashion choice, but she happens to be very polite. Oh well. It used to be a lot easier when I'd run at 4:00 AM. The only person who ever saw me was the the guy who drove around tossing the NY Times on driveways. You should see how he dresses.

Road running reunion

On the road again

Today's run (street!): 4.2 miles

Spring must finally be coming. I looked in the backyard and could actually see parts of our deck that weren't completely covered in snow. It was 41° this morning when I prepared to run in my neighborhood for the first time since January 12. This winter's snowfall has not been good for outdoor running. In the nine and a half weeks since New Year's, I've only run outside seven times, including today.

Spring is on deck

Running indoors is mostly about fitness while outside running widens the experience to include far more stimuli. The smell of a backyard barbecue in summer or new construction on a house a few blocks over can positively distract from the rigors of the run. Not to mention the great sensory overload you can get from trail running. I was excited to be able to run outside today, but I'll admit to being a little nervous about breaking from the comfort of my normal routine.

It was an easy transition to my neighborhood streets and I felt stronger than I expected as I came up on my first mile. Unlike many who perceive the treadmill as an easier workout than running on the road, I have the opposite view. I suspect my treadmill speed is actually faster than what is shown on the display. I fell into a comfortable pace today and every once in a while it would occur to me to add a little speed. At one point I was overtaken by another neighborhood runner, but that didn't bother me too much.

I ended up averaging a little under ten minutes per mile. Not good compared to my normal outdoor pace, but far better than the speed I struggled to maintain when I ran with my friends at Eisenhower Park a couple of weeks ago. My cold is gone, but some chest and sinus congestion still remains.

I want to go out and do another easy run tomorrow and try to push the distance a little more. I may put that off until Monday and take advantage of having access to the high school track on Sunday. Last time I tried the track it was covered with snow. I hope today's thaw helped to clear it. If it looks like my backyard deck I'll head back to my local streets.

Return to a real workout

 

Today's run (treadmill): 3.25 miles

Colds are funny. No matter their severity, they all seem to follow the adage, "Three days coming, three days staying, three days leaving." An impending cold signals the start of an uncomfortable week. Bad decisions are often made (certainly by me) about how far to push myself after the first symptoms appear. I questioned whether it was wise to run 6.7 miles two Sundays ago, when it was clear that I had started a cold. But if that had an effect on this cold's duration, it was a minor one.

Aside from some residual stuffiness, this cold has pretty much passed. I decided to ease back into running during the "leaving" phase, with extremely easy workouts. This morning I felt close to full strength and went back to my usual routine. I'll admit that I picked a program on the lower end of the performance scale, but it was a legitimate workout.

My concern was that resuming a normal training pace too soon would tire me out before I could finish the run. I had a moment around the first quarter mile when I wondered whether I'd taken on too much too soon. Happily, that didn't last long. Although the rest of the run felt long, it was completely manageable. My other concession to recovery was forgoing the anaerobic sprint I usually do for the last quarter or eighth of a mile.

The best thing about today's workout was knowing that I'm ready to train again. I'll take it fairly easy over the next week and hopefully see some pavement this weekend.

Tuning up for an outside run

Foggy view from the treadmill

Today's run (treadmill): 3.3 miles

This has been a great week with the kids being off from school. I've had to work on projects, but I've also had a good amount of family time. My business in the city yesterday produced the need to do lots of work today. I didn't get to run on Thursday, but I covered a few miles on foot. I'm loving those gel insoles.

I'd hoped that this morning would provide an opportunity for me to finally get outdoors and run. However, the snow hasn't melted much and there was a thick fog that was produced by a rapid change in temperature. Both of these things made street running too dangerous, so it was back on the treadmill. I no longer curse my fate as I look outside at the still-icy roads. I know I'm fortunate to have the option to run indoors.

I'm planning to run with my Runsketeer buddies on Sunday, so I tried to up my game in terms of speed. I've been extremely complacent in terms of performance and I shocked my body a little by doing a progressive speed run. This treadmill regimen has taken me out of race shape so I hope I'm able to keep up with the "twin turbos" this weekend. I usually do better on the road than on the treadmill in terms of pace, but the last time I ran on pavement, my legs did not like it at all.

A little Xmas contribution to my 2013 mileage

A white-ish Christmas

Today's run (street): 3.3

It's Christmas day and even though it's a Wednesday, it really feels like a Sunday. That being the case, I was prepared to go out for a long run this morning. When my wife mentioned the combination of 20° temperatures with a wind chill making it feel like 11 degrees, I considered an indoor run. But I had counted on running outside today along the quiet, snow-dusted roads, and I decided to deal with the cold by adding extra layers.

I thought about how wearing compression pants under track pants, along with three upper layers, might slow me down. Since I wasn't planning to go out for a fast run today, a little speed restriction didn't bother me at first. I made my way through the first few roads at a jogging pace and encountered some bundled-up couples who were taking a Christmas morning walk. They greeted me happily when I went by. My present was not giving them a lecture about walking on the wrong side of the street.

The conditions made the going tough and my face was beginning to freeze. It can be very uncomfortable running with glasses in the cold, especially when the wind is hitting head-on. I own a balaclava, but it restricts my breathing and traps moisture that causes my glasses to fog up. Besides that, the tightness at the sides creates a fit issue at the temples that can tilt the lenses and distort my view. I haven't worn contact lenses in 20 years, but days like today make me miss them.

At around the one mile point I began to tire. I was running easy so I didn't understand it, but I definitely lacked energy. It could have been the cold or the extra weight of so many layers, but I just couldn't generate much speed. I toughed it out and ended up covering 3.3 miles. I'd planned to go longer but I was glad to finish when I did. It was nice to run without needing to share the road with cars, trucks and buses, but I was somewhat disappointed with my performance.

Mileage history (2013 projected)

My speed and stamina have taken a dip since the Hot Chocolate 5K and I wonder if I need to take a few days off to rest. I may do that tomorrow, but I need to get back to schedule after that. I'm 12 miles short of hitting 900 miles for the year, which means I'll need to cover at least that distance in the next week. Even so, I'll end up running 41 less miles in 2013 than 2012. But that would still be 100 more miles than I ran in 2011.

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.

I swear I didn't run through my neighbor's houses

I love data visualization

Today's run (street): 4.2 miles

The sky is as white as paper and the temperature is dropping. We're supposed to get two inches of ice and snow by late afternoon. Nothing so far, but I can tell it's coming. For that reason, I made sure I got outside early to get in a few recovery miles before conditions got worse.

I had no intention of running as hard as yesterday and had to throttle my speed a couple of times. A recovery run is supposed to be done well under anaerobic threshold to help flush lactic acid from leg muscles. I used my heart rate monitor to guide my pace, averaging 75% of HR max throughout the run. It was a nice relaxing workout, although my (gloved) hands got surprisingly cold.

No actual yards or living rooms were entered

I've written a lot about the variability of GPS as a measurement tool and today's margin of error was particularly egregious. Not only did the Garmin show me starting the run three blocks from my actual beginning point, the accuracy was laughably bad throughout the entire route. The Garmin route map (see above) makes it look like I ran through many people's yards and houses.

Distribution of pace times through the year

Reflecting back on 2013's racing season, I charted my race paces to see if there were any obvious patterns. The data doesn't show any trends that would explain my performance, as times were all over the map. I'm hoping that next year will yield faster times and more consistency. At least I finished the season in a good place.

Race report: 2013 Seaford Hot Chocolate 5K

Post-race with SIOR

Today's run (Seaford Hot Chocolate 5K): 3.1 miles (8:54 pace)

Today's Seaford Hot Chocolate 5K was my last race of the year and I wanted to make it count. After some disappointing racing experiences throughout 2013, I was happy to cap off the year with some decent results.

I had never run the Hot Chocolate race before, but I heard it was big. With over 900 participants, numerous volunteers and a large group of Seaford HS band members playing in the main hallway, it felt like an event. I ran into a few people I know along the way and found my buddy SIOR at the registration area that was set up in the main auditorium.

The plan was for the "Three Musketeers" to run this race together, but unfortunately the Petite Pacer was dealing with both a bad cold and an overheated car. We were disappointed that she couldn't make it today, but after running four races in the last month, resting was a smart move.

SIOR and I got to the starting line and before we knew it, it was 9:00 AM. I was so caught up in our conversation that I didn't experience my usual starting line race jitters. Soon enough, the start was called and we were on our way. I tried to match SIOR's cadence for the first minute, until she disappeared into the distance like a royal blue apparition.

I felt good at the start and hoped that I would be able to maintain a decent pace throughout the run. The Hot Chocolate course is a big rectangle and the first mile comes up near the corner of Mill Rd and Washington Ave. I was a little surprised to see the first mile clock showing 10+ minutes when I passed it. For a moment, I questioned my ability to judge my own performance. A look at my Garmin showed I'd covered the mile in 8:33. Apparently that clock time reflected the earlier start of the physically challenged participants.

Washington Ave seemed to have a slight slope and I tried to take advantage, but lost about 20 seconds on mile two. I was surprised to see us passing the rear of the high school so soon, until I remembered that this was a 5K. After two recent 10K's, it was nice to know that I'd be getting through this course a lot quicker.

I did something today that I've rarely done this year - pass a lot of people. I was able to maintain my speed fairly well and, before I knew it, I came to the turn onto Seamans Neck Rd. At that point I said to myself that SIOR had probably just crossed the line. Still, it was the last, straight shot to the finish line and I worked hard to stay on pace.

I thought I was tracking toward a 27 minute finish when I saw the chute far off in the distance. I stepped up my effort and even passed a few people as I drew closer to the line. Once I could see the clock, it was already reading 27:xx. I thought I had a chance of keeping it under my targeted 27:50. I was pleased when I crossed the line and saw that the timer read 27:37.

Post finish "action" shot

Photo courtesy of She Is Out Running

SIOR greeted me after I'd crossed the line. She finished four minutes earlier than me and picked up yet another age division podium spot. We looked at the readouts posted on the timing truck and then headed into the high school to get some hot chocolate, the real purpose for running this race. We were hoping that the award ceremony would begin soon after so she could collect her medal while I cheered. Unfortunately, we both had family obligations that required us to leave before the ceremony started.

Nice race shirt

I had a really nice time this morning and was happy with my performance today. It was great to hang out with SIOR and to experience a new race under good weather conditions (I'm still slightly traumatized by the Long Beach Turkey Trot experience). My next event will be the LIRRC Hangover Run that takes place in Eisenhower Park on New Years Day morning, followed by the Long Beach Snowflake run in February.

Is 93% of max the magic number?

Not far from 180spm, so where's the speed?

Today's run (street): 3.5 miles

I'm a little disappointed with today's run because I could not generate any speed. Despite clocking my first mile in 8:57 (easy for many, but hard for me lately), I ended up averaging an unremarkable 9:29 pace over 3.5 miles. After a good start, I'd lost time on mile 2 and then tried to make up for it over the last 1.5. I felt like I'd made a good effort, but according to Garmin Connect, my heart rate across the whole run ranged only between 77-85% of max.

I took a look at my race history and compared my pace performance with my average heart rate. Since I've only run about a dozen races using a heart monitor, this wasn't a statistically significant representation. Directionally, it seemed to indicate that my best times happened when my heart rate averaged 93% of max HR or greater.

Does this mean that I'm somehow holding back, even as I work to push my speed during a run? The numbers seem to point to an opportunity to unlock some speed by adding even more effort. My cadence rate has actually improved over the 5+ years since I've starting daily running, but that hasn't translated to speed. I will do my best to hold the effort on Saturday. I'm not asking for much, but beating 27:50 would be nice.

Short & sweet threshold run

Today's run (Threshold): 3 miles

This year's racing experience has been a mystery. After a decent start in February, my performance has really tailed off. I'm not sure if it has to do with my change to a less structured schedule this year or less intensity in terms of training. Whatever the reason, I haven't been satisfied with my results. November has always been my best month for achieving personal bests, but that's not been the case this year.

The Hot Chocolate 5K happens next week and I've hoped that the two 10K's I've done in November have put me in racing form. I debated whether to go to the track today to run intervals or do a threshold run. I decided a run in the neighborhood would more closely duplicate race conditions.

It was another cold morning with mid-20's temperatures. I was chilly at the start, because I wore fewer layers. If I was going for speed, I didn't want anything inhibiting my progress. I took off fast up the road, looking to get into high gear quickly. The street has a slight incline that gives way to an equally slight downward slope. I knew I was moving faster than I do on a normal training run and my Garmin shows I covered my first mile in 8:25.

I didn't have a set distance for this threshold run. It was more about running a short (but not too short) loop with some urgency. I lost some speed on the second mile, but came back fairly strongly by the end of the run. I wasn't paying attention to my distance, but after I'd stopped I saw that I'd covered three miles at 8:46. Not too bad considering my HR only averaged 85% of max.

A year ago I might have done that run 25 seconds per mile faster, but I won't complain about today's performance. I slightly regret not monitoring my Garmin and completing the full 5K distance. I doubt the numbers would have been much different. If I can hold my pace below 9:00 next Saturday, I'll consider it a successful effort. I'm hoping I'll do better than that and certainly no worse.

Turkey trot not

Today's run (street): 3.9 miles

Happy Thanksgiving. This is many people's favorite holiday, mine too I guess, because it is so inclusive. No divisive factors such as religion, culture or politics at play. As long as you don't think about what really happened on or around the first Thanksgiving (SIOR recently made the point that the original dinner was anything but inclusive), you can enjoy a middle of the workweek break. We're heading out for Thanksgiving dinner soon. Rumor has it that our hosts are cooking a lot of vegan food, but there WILL be turkey.

Thanksgiving time is a runner's paradise, because of all the local Turkey Trots that happen around the holiday. I had a good time, under miserable conditions, while running the Long Beach Turkey Trot last Sunday. We were signed up for this morning's Nissequoge 5K, but we decided to forgo our plans in favor of doing something else. We've run that race for the past three years as a family, at a very easy pace. I've never run a competitive race on Thanksgiving day, but I'm thinking of changing that next year.

Instead of a Turkey Trot, I settled for a neighborhood run this morning. With 12 MPH winds, it felt like 21° outside. I probably overdressed for the run, but the Long Beach experience was still fresh on my mind. Even so, when the wind hit head-on, it seemed to pass through every layer I was wearing. I was feeling okay about my progress until I encountered another runner coming from a connecting street who turned onto the road behind me. He passed me a few seconds later, before taking a right while I kept going straight.

I sometimes have trouble understanding why people run faster than me. This person seemed to be maintaining the same cadence as me and his stride was not particularly open. Yet he moved at a faster rate than me. Puzzling. I know that, in reality, his cadence was faster and his stride was longer. It just didn't look like that.

Today feels like Sunday, but the weekend is yet to come. I plan to address the speed issue on one of those weekend days by running intervals at the track. Perhaps that, and a continued focus on increasing my average distance, will help me achieve the elusive sub-9 pace that I used to expect when I raced. I like to think that I would have saved 30 seconds per mile on Sunday if I wasn't running into 29 MPH winds. But that may just be wishbone thinking.

Race report: 2013 Hope for the Warriors 10K

Seconds before the finish

Photo courtesy of the Petite Pacer

Today's run (Hope for the Warriors 10K): 6.2 miles - 58:56 (clock time) 

I'm not sure that it signals a move toward improved performance, but I ran my fastest 10K of 2013 this morning at the Hope for the Warriors race. Although I'm pleased that I finally broke an hour, today's time was measurably slower than my two prior Hope for Warriors efforts. The upcoming Long Beach Turkey Trot will tell me if today's performance was positively directional.

Team ER on race tee and bib duty

We arrived early because my wife and kids had volunteered to work the registration area. Their job was primarily focused on handing out race tees, but they also handled some of the bib distribution. I spent much of my time trying to stay warm over the three hours between arrival and race start. I tried to find spots in the crowds that had direct sunlight.

Chillin' (literally) before the race

The wind was brisk and that contributed to the chill. I regretted my decision to leave my calf sleeves home. Beside their energizing effect, they would have provided some additional warmth. I also regretted wearing running shorts instead of pants. However, I was glad with my gear selection once I was running.  

The armed forces were well represented, as always

The 5K starts first and they line up those participants ahead of the 10K bunch. A few years ago, everyone started at the same time and it was a mess getting past the 5K walkers in the first few minutes. Now the 5K starts 15 minutes before the 10K and the road is clear until we catch up with the 5K tail-enders on Wellwood Ave. It was hard to find exactly where the 10K start was going to be. There was no mat to capture starting time, so everyone was tracked by clock time. My net time might have been a little more favorable were that the case.

At race start (directly to the right of the giant head)

Shortly before we started, I ran into the Petite Pacer. She went to say hello to another friend so I didn't see her again until I saw her come up the right side, moving swiftly. She had a great run today and a 10K PR. She was very kind to video me as I made my way through the final meters and over the line. I found her after the race and was able to introduce her to my wife and kids.

The Hope for the Warriors 10K course is the least remarkable thing about this race. It's a big box with few notable characteristics. Without scenery to distract me, I kept my mind on my stride but I purposely ignored my Garmin's display. I wanted to run the race by feel and perceived effort. I was surprised that there were no clocks or split announcers along the route. I did have a basic understanding of where the splits were located and that was reinforced by chirps from my watch.

The first two miles went by quickly and I felt like I was moving well. I ran the first mile under 9 minutes but I was in the 9:10 range by the three mile point. My performance slipped a little after that, although it improved once I cleared the on-ramp from RT 109 to Sunrise Highway. Coming up that on-ramp was tough and it threatened to take the fight out of me. I tried my best to maintain speed once I hit Sunrise for the last half mile.

Happy to be finished

Me and TPP who ran a great race

I wasn't sure whether I'd trained well enough for this race and my struggles in the late miles made me wish I'd done more base work. Overall, I was fairly satisfied with today's performance. I'll be interested to see how it goes in Long Beach, two weeks from today. Tomorrow is a rest day!

No expectations, but plenty of Hope

 

Last year I participated in a race that was put on by my division's parent company. Before the race even started, one of my colleagues shared the tweet he planned to send after he finished. I told him that I never write my headline until I'm done with the race. Too many things can happen between the start and the finish lines. I don't know what my friend ended up tweeting, but I still hold fast to that policy. I ended up having a far different race experience than I'd anticipated that night.

Tomorrow is the Hope for Warriors 10K and I've set no expectations in terms of how I might do. I've done this event twice and have a good understanding of the course. Two years ago, I attained a 10K PR at HFW, after almost skipping it because I hadn't really trained. 2011 was a year of personal bests. I got a another PR at the Long Beach 10K Turkey Trot, just one weekend after Hope for Warriors.

This year has not produced many race highlights. My best performance came early on at the Long Beach 4 mile Snowflake race, where the Petite Pacer beat me over the line in an impressive burst of speed. Since then, I haven't broken a 9:00 pace in a race, even in 5K's. I'm going to run the best race I can tomorrow. As always, I'll wait until I finish before I compose my headline.

Lies, damn lies and Garmins

Look how fast I didn't run!

Today's run (street): 3.4 miles

I was in meetings all day on Tuesday and didn't get a chance to do a run. I did cover a lot of ground on foot, so that should count for something. Along the way I noticed many marathon tourists (after all these years I can easily spot them) enjoying the sights prior to running the race on Sunday. A couple of my meetings were held near Time Square, where sports demonstrations publicizing the Sochi Olympics were going on. It was a mob scene, but fun to watch.

I had no city meetings today, so I resumed my run schedule this morning. I've been running with my foot pod so that I can capture my cadence, but I still use the Garmin's GPS to measure my mileage. Due to that, I haven't bothered to calibrate the foot pod for distance. When I fire up the Garmin, it detects the foot pod and asks whether I'm running indoors. If I say yes, it will turn off the GPS radio and use the foot pod for measurement instead.

Today I went through the routine and when it looked like the signal had locked in, I was on my way. I hadn't gone half a mile before the Garmin chirped saying I'd reached my first mile. I figured that the GPS signal must not have actually acquired before I started and the watch was working off the (uncalibrated) foot pod. I didn't care much, because I always Gmap my run to get exact distance.

The watch did switch to GPS mode shortly after that, and my remaining splits were in line with my normal pacing. While I would have liked to meet the performance that the Garmin recorded for today's run, I must admit to a far less impressive pace in the mid-9:00 range. So the Garmin lied, but I'll forgive it. If I could run five minute first miles for real, I might actually break an 8:00 pace on my training runs.

Progress made on a progressive run

Progressively paced

Today's run (street): 3.25 miles

I've been feeling a little down about my running lately, because I haven't been able to generate much speed on my training runs. I feel I should be meeting certain paces and I've come up short over the last week. The fact that my race times have been going in the wrong direction has fed into this frustration. Today's run didn't completely reverse my perspective, but it certainly helped my confidence.

It's hard to explain my current issues. I'm not running to exhaustion, but I've felt like the effort I'm putting in isn't translating into commensurate performance. I haven't been pushing the pace like I'd do if I was training for a race, although I do have a 10K coming up in three weeks. I shouldn't be expecting greatness, but perceived effort seems greater than observed performance.

I started out slowly and expected this run to be another disappointing effort, but I picked up speed every mile, finishing up a minute and half per mile faster than I started. This improvement was not apparent in the moment. It wasn't until I'd downloaded my Garmin's data that I saw my negative splits and realized I'd managed to hit an acceptable overall pace.

I'm glad to have tomorrow, my weekly rest day, for further recovery. I'll need to turn my attention to race training soon. For now I'm just happy to have broken my streak of sub-par runs.

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.

Race report: 2013 Town of Oyster Bay Supervisor's Run

Seconds after crossing the line

photo courtesy of The Petite Pacer

Today's run (Town of Oyster Bay 5K): 3.1 miles - 28:39

This morning I ran the Town of Oyster Bay Supervisor's Run for the third time and had a great time. My performance was puzzling because I thought I'd do better than I did. I had an RPR (reverse PR - just made that up), having run my slowest ever 5K. Aside from that, it was great. I met The Petite Pacer for the first time in person and she was every bit as personable and charming as she is on her blog.

The morning started out well. I arrived a few minutes before 8:00 AM and parked at the high school. It's a fairly short walk the hill up to the Community Center where they do registration and hand out race numbers and sweatshirts (hoodies this year!). I gave them my name, but it wasn't on the list. After being referred to some GLIRC volunteers, I realized I'd never actually signed up. Not too smart of me. The GLIRC people were incredibly nice and gave me a race number after I'd filled in a registration slip. They didn't even ask for money, but I had the cash on me and insisted they take it.

After pinning my race bib, I ran into The Petite Pacer. We headed toward the starting line that's located about a quarter mile away on South Street. TPP suggested doing some strides so we ran a few hundred meters and returned to the starting area a couple of minutes before 9:00 AM. Our position was at the front and I mentioned that we should probably move back to keep from getting run over by the 6 minute milers.

The race started, but I found it hard to move in the crowd. I regretted suggesting that we move back before. TPP broke away and I saw her farther ahead before losing sight of her as we turned on Berry Hill Rd. I could not get past the clumps of runners ahead of me and I think it lengthened my first mile time quite a bit. According to my Garmin, I ran the first mile at 9:35 and came through mile 2 around 19:18. I did the last 1.1 miles in 8:21.

I thought I was in better shape for this race and didn't struggle on the long hill, so I was puzzled by my time. The hill gets steeper after the first mile and I remember feeling the increased burden. Still, I felt like I was maintaining a decent stride. I obviously made up a lot of time on the mostly downhill second half and passed a lot of people along that pretty tree-lined road. The peacefulness was broken only by a runner behind me who was singing loudly and off key to the music on his iPod.

All hope of finishing under 27:50 (which would put me below a 9 minute pace) was dashed when I saw the 3 mile clock. I pushed as hard as I could and crossed the line at 28:39. TPP was already there, having finished a few minutes before me. She videoed my crossing the line which was an unexpected surprise. I'll return the favor the next time I finish before her, which will probably be never.

Post race recovery with TPP

TPP and I got our time slips and I saw my official pace - 9:13. It was far slower than I expected to run this race. Last year I averaged 8:22 per mile. I have not had a good year in terms of race times but I still have a few more races on the schedule to improve my standings.

More important than my time was the great experience I had with the kind volunteers who helped me get registered and the opportunity to spend some time with The Petite Pacer. Tomorrow I'll get out and go as far and fast as I feel like running. That's the best part of a Saturday race. You have a bonus day to do another weekend run.

Making my last taper count

A serious threat to pant-kind

Today's run (street): 3.1 miles

As much as I love running, business needs to come first. For that reason, I was unable to get in my workout yesterday. I was in the city all day for meetings so the opportunity for a run didn't surface. I'm temporarily boycotting my Fitbit because the holding clip has deteriorated to the point where I fear it will rip my pants when I wear it. Without it, I don't know how much distance I covered yesterday on foot, but I'm estimating it was between 4 and 5 miles.

Today I had no excuses. Without a commute into the city, I had enough time for one final run before Saturday's 5K. Although I've heard that I need to do weekly speed work in order to avoid embarrassing myself on race day, I think I've prepared well for the race. I decided that a good hard run over three miles would be a nice way to end my taper.

I took off at a brisk pace and tried to maintain that turnover throughout the entire run. The difference between this type of workout and a race centers on two factors: the influence of other runners and the psychology of competing in a timed event. Without those two things, my expectation was to see a very good, but not spectacular performance today.

That's exactly how it came out. I'd kept my heart rate around 85% max and covered the distance in a little over 28 minutes. For me, that was exactly on the mark. I could have pushed harder and dropped my pace into the 8:00 range, but I didn't see any reason to do that. 9:06 was a decent average under the circumstances. I'm making no predictions for Saturday. A lot of it will come down to how I feel on race day morning.