Test new running shoes? Yes, please

The new Saucony Kinvara

Today's run: Central Park (planned)

I was recently contacted by a PR person from Saucony about an opportunity to try their new Kinvara lightweight trainer. This shoe is more neutral than what I'd normally wear but I'm interested in its low profile with a heel-to-forefoot ratio of 18/14 mm. I haven't forgotten about mid foot running but my Brooks GTS-10's are so great I would be reluctant to give them up. Given their unique nature, and their low profile the Kinvaras may make a great addition to the Emerging Runner's collection of running shoes. Besides the Brooks GTS-10's I also have pairs of GTS-9's and ASICS GEL-1130's. On the trail side I have Helly Hansen Trail Lizards for the toughest technical terrain, Adidas Response 15's for multi-surfaced trail and street running and some NB 460's that fit and perform really well despite being a "value priced" shoe.

Left out of this collection are any lightweight trainers or racing shoes. I was very interested in the Brooks Green Silence when it was announced but when the time came I opted for the 10's to replace my 600+ mile 9's. I signed up for (and was accepted to) Brook's test program but I have not been contacted to try anything. Even if I do I won't be able to talk about the shoes or mention them on this blog, per the terms of the program. No problem there, the chance to try Brooks experimental shoes is worth the silence, green or otherwise. I'm happy to try any running shoes or gear that companies want to send to me to review. I'd even try Nikes but not those silly ones with the shock absorbers on the heel.

I'm planning another Central Park run today and I'm hoping to cover some new ground north of the reservoir. I keep hearing about the hills up there and I'll see how well my training has paid off.

Foregoing my run today

No workout today

I decided to forgo my usual Thursday workout this morning and take an additional day of rest this week. I'm looking to add more distance to my weekend runs and I've recently added a longer run on Fridays in the city. It's taken a while but I'm beginning to understand the value of rest as an enhancement to my training. On a recent run with my friend and running advisor, CK, we talked about the frequency of my runs. CK suggested that more rest would be beneficial for recovering from longer runs and the additional rest would probably help me improve my performance. I'll see if that's true tomorrow where I plan to run the big loop around Central Park (6 miles). My goal is to average around 20 miles a week and I should be able to do that even if I take two days of rest on some weeks.

Return to Jackrabbit

Today's run (street): 2.4 miles at 9:24 per mile

Yesterday I headed over to Union Square with my friend CK for lunch and a visit to Jackrabbit Sports. CK was in need of a new pair of running shoes. The NB 1225's he was using were a year old and had a lot of mileage. He was never very happy with these shoes, mostly because of their wide toe box that can make the forefoot feel unstable. I showed him the Brooks Adrenalines that I wear and really like. He tried on a pair and initially said he felt "flat-footed" but after a few minutes he said they felt very comfortable. I could tell CK was ambivalent about the shoes and I encouraged him to try other pairs. He selected a pair of Saucouny Guide 3's and loved the fit and the energy return that he thought was better than the GTS-10's. CK bought the Guides and I picked up an Amphipod water bottle that is form fitted for carrying while running and has a strap that secures it to your hand. I'll probably use it on Friday during my Central Park run. I could have used it last weekend when temperatures were close to 90.

This morning I headed out again for my run and was surprised by how cool it was compared to Tuesday. I actually felt cold having dressed for warmer temperatures. It took a few minutes to get comfortable but once I did it felt pleasant because there was little humidity in the air. My pace felt much brisker than yesterday's and while it was still a leisurely 9:25 average per mile that was :15 per mile faster than the day before. If not for my time constraints I would have added more miles. I returned home fresh and wishing I had more time to run. I guess it's always to finish wanting more.

An illuminating run

Today's run (street): 2.4 miles at 9:40 per mile

Not quite this bright!

I know I've already made too much of Sunday's long run but this morning my legs were really sore. I tend to feel the effects of a tough workout a couple of days later and that was the case today. My first thought upon awakening was to give myself a break and take another rest day. I dismissed the thought and considered an easy elliptical or treadmill session instead. Once I saw that the temperature at 4:00 AM was in the high 60's I decided to run outside.

The last few times I'd run with my Petzl Tikka headlamp I noticed that the intensity of the LED beam seemed low, even on the brightest setting. It had been a year since I bought the Petzl unit and had not yet changed the batteries. I corrected that on Sunday and this morning I was amazed by how well the lamp illuminated the streets. I had obviously become used the diminishing beam and had actually done an early morning run recently without the headlamp and didn't notice until I returned home. It was fun seeing my neighborhood lit up this morning, the bright blue-tinged light again creating illusions of evil faces reflected off the front of BMWs and Acuras. More importantly I could see the road better and was able to avoid a torn up stretch where a gas line was recently installed.

I didn't run fast today but I really felt great while I was out there. The air was cool enough to keep things comfortable and my legs, though tired, were fine once I hit the street. It may not have been my most rigorous workout of late but it was one of my most enjoyable early morning excursions. Today I plan to visit Jackrabbit with a friend who is looking for a new pair of running shoes. Between this morning's run and an opportunity to visit a running store during the work day, I couldn't be more pleased.

Lengthening my long runs

Today's workout: Rest day

A "long run" has different definitions based upon who is doing the running. For some, it's runs over 13 miles with the half marathon length serving as the demarcation point. For others (like me less than two years ago) a 5K can be considered an aspirational length. I have been thinking about yesterday's run and how it felt to break a personal distance record. Could I have gone on longer than the eight miles that I'd covered on Sunday? As a practical matter the answer is yes. I stopped when I did because I'd met my goal of eight miles - four out and four back. If my distance goal was nine or ten miles I probably could have accomplished that as well. I finished my run at eight because I had nothing more to prove on Sunday.

I have a goal of doing a 10 mile run this year. It's a distance considered by some to be a nice training run while others view it as an impossibility. I'm happy that it is at least a possible distance for me at this point.. Looking at my splits for yesterday's run, I noticed that my pace dropped measurably after an hour's running. I ran the first 6.2 miles averaging 8:57 per mile but miles seven and eight were far slower, closer to 9:30. I really liked running for longer than an hour. It surprised me that I had enough energy to pass other runners even near the end. Perhaps I'll look at increasing distance as my next focus point and worry less about pace. Well, maybe just a little less.

1,000 calorie run at Bethpage State Park

Today's workout (Bethpage bike trail): 8.15 miles at 9:10 per mile


Not counting last year's Cape Cod marathon relay in Falmouth where I ran 9 miles across two non-consecutive legs, I established a personal distance record on today's run. Unlike Falmouth, today was an uninterrupted run that covered over eight miles in an hour and fourteen minutes. I'd made the decision not to run this morning's RXR 10K and, perhaps out of guilt for not racing, I decided to do a long distance run on my own. In order to break out of my usual 5-6 mile doldrums that have been standing in as my long weekend runs over the last couple of months, I knew that needed to leave the neighborhood to help frame out a longer run.

I headed to Bethpage State Park and paid my fee at the gate. I tried to buy an Empire Passport on the spot but they only accepted a check or cash and I only had a little cash and some credit cards. I began my run at the end of the bike trail and immediately met the sharp but mercifully short initial hill. Once level I knew that I'd enjoy a long downhill at the half mile mark. The enjoyment was bittersweet because I knew I'd need to climb that long hill upon my return when I would be depleted from an hour-plus of running. I followed the trail for four miles and passed a number of runners and walkers and winced each time a cyclist whizzed by from behind a little too close for comfort. At one point two cyclists, who were riding side by side, came toward me and would have run me off the path but I stood my ground. Unfortunately for the closer rider, the end of my elbow struck his arm and produced a yelp. I apologized by yelling "share the road!" I think they learned their lesson. At least they didn't come after me.

A funny thing about the Bethpage bike trail is that it often gives the illusion that you are running uphill even when you're not. As I made my way for the 4 mile out segment I kept thinking how I'd enjoy the downhill side of the hills I was encountering. I turned around shortly after crossing the overpass to the Southern State Parkway and was dismayed as I headed back for the second 4 miles that the path seemed to run uphill. I still had plenty of energy at the midpoint so the hills were easily met but in the back of my mind I was dreading the long uphill stretch I'd encounter between miles 7 and 8. I caught and passed a few more runners and walkers and monitored my Garmin to make sure my heart rate was staying within range. I managed to keep my pace around 9:00 per mile for most of my run but by mile seven I slowed down to the mid-9:00 range, especially on the run-ending hills. The only time I questioned whether I could finish what would be a personal best for distance was leading up the big final hill. When I got there I just dug in, took smaller steps and hoped it would soon be over.

In the end I covered 8.15 miles and when I looked at the run summary on the Garmin I saw that I'd expended exactly 1,000 calories over the course of my run. I'm pleased that I've broken the 8 mile single run barrier and I feel better than I thought I would after all that work. Some day I'll run 9 but for today, the record stands at 8.15.

Two good runs: one fast, one slow, both hot.

Yesterday's workout (Central Park): 3.25 miles at 8:52 per mile

Today's workout (street): 5.48 miles at 9:21 per mile

In terms of effort I'd say both today's and yesterday's runs were about even. It's hot today and it was hot in NYC yesterday when I trekked over to Central Park. I much prefer the cooler seasons for running but I also appreciate the way the trees and plants bloom in late spring and summer. The Park was filled with runners, cyclists and walkers when I arrived and I made my way over to the bike path on the lower loop to start my planned 3 mile run. My friend Steve had a conflict so he couldn't join me today so I decided to go it alone for a run that followed the lower and upper loops below the reservoir. I knew that the hardest part of the run would happen in the first half because a good part of that route is uphill.

Surprisingly, it took me about a mile to break a sweat but once I did I got REALLY hot. I cut across the Great Lawn and headed back down, hugging the shade and happy to know that a few downhills awaited me. I'd maintained a decent pace even with the uphill challenges and I passed a number of runners although I also got passed a couple of times near the end. By the time I returned to my starting point I was glad to finish, cool down and head back to the office. A meeting had spilled into my planned running window that caused my run+lunch timing to be very tight. I quickly changed, grabbed a fast bite and finished a minute before my 2:00 meeting. I was glad that I'd run an 8:52 pace or I might have ended up being late!

This morning I headed out for a neighborhood run with no planned route in mind. I intentionally ignored the Garmin because I didn't want to influence my pace in any way. Although it was hot and sunny I figured that I could a cover some good distance as long as I didn't push too hard. I did check my heart rate throughout the run to ensure I was keeping to around 80% of max. I traveled through my neighborhood roads and cut across to neighborhood #2 at the 2.5 mile mark. I chose some different streets that I hadn't run before, just for a change. I wound up covering 5.5 miles and finished feeling like I'd done a lot of work this morning. I need to work more on distance so I'm considering heading to Bethpage tomorrow to run the bike path where I can cover 8 to 10 miles out and back. Either that or a return to Stillwell to begin training for the next XTERRA race.

Racing through spring

Today's planned run: Central Park

I'm feeling rested after taking a break yesterday. I'm hoping that this will translate into some good running today and over the weekend. I'm planning to run again with my friend in Central Park at lunchtime. It should be 70 degrees by noon with lots of sun. Oh, for the want of a shower in my office!

It's amazing that tomorrow is already May 1st. This year is going by quickly and I attribute much of that to spending a good part of January recovering from pneumonia. It's like I lost a month. But spring is here and the weather has been nice for outside activities. I'm thinking about my racing plans between now and summer. Right now, I've got three events in my sights:

The Brooke Jackman Run for Literacy 5K - May 16
A local race in mid-May. It's a run/walk so my family can also participate.

The XTERRA Trail Race Series 8K run at Stillwell Woods - June 6
This is the second Stillwell XTERRA race this year. I did the first in March and it was tough. Add 1.5 miles  to that course and you have the June 6 race.

New Hyde Park 8K - June 13
I ran this race last year and learned my lesson about starting too fast. I bonked 2/3 of the way through the course but still ended up with a sub-9:00 pace (just barely).

This would mean I'd be running three races in one month's time. It seems like a lot but I do those distances as training runs every weekend. The XTERRA is the biggest challenge and until recently I thought I wouldn't be up for it. I will do what's necessary to be ready to run it by the 6th. After all, racing is a great way to train for other races.

Take a break, it's good for you

Today's workout: Rest day

For the third time this week my day started with the loud bleat of my my alarm clock. Yesterday's run, though short, was tough and I decided that if I woke up on my own, minutes before the alarm as I usually do, I would do my planned workout. If not I'd take a rare mid week rest day because I obviously need it this week. Even so, I struggled with the decision but, ultimately, I'm glad that I rested.

When I ran in Central Park with my friend CK last week I'd mentioned that I run or work out every day except Mondays. He was incredulous (he obviously doesn't read my blog!) and said I shouldn't run so often. I told him the distances I am covering during week days and he agreed that my schedule is probably fine. However, he did say that resting a day or two, or even for a week occasionally, can be beneficial. I guess that helped me feel better about skipping today's planned elliptical session. I'm planning to run in the city tomorrow and I'm sure this week's extra day of rest will help reset my energy level and prepare me for longer runs over the weekend.

Defining a good run

Today's run (street): 2.3 miles at 9:19/mile

By now I've done enough running to know that some runs just go better than others. I don't get upset when I struggle through a run because I know it's circumstance, not ability, that is making the going tough on that particular day. I've done long runs that seemed effortless a day after I ran a particularly difficult shorter run. What defines a good run? Is it how you feel when running or how fast you covered the distance? Or is it the way you feel at the end that matters?

I didn't feel particularly energized this morning when I went out and I started off slower than usual. I know this because my Garmin kept chirping to indicate that I was drifting out of my defined pace range. It was cold at 4 AM and with the wind, even colder. I dressed for the weather but it took me a few minutes to warm up. I usually start my runs on cold days by going north on roads that have slight elevations. This makes me work a little more and helps get my body temperature regulated. The extra work needed for the hill plus that first few minutes transitioning to aerobic breathing sometimes makes it feel hard. That was the case today and it didn't feel much better ten minutes into the run.

It was probably fatigue but my legs felt heavy and though it seemed like I was running at a brisk pace I could see that I really wasn't. I can't say that I enjoyed today's run as much as other recent workouts but when I finally reached home I had the same feeling of accomplishment that I get every time I complete a run. It's a great feeling and I didn't care about the numbers. I got through a tough one today and as I cooled down I knew I'd soon be rewarded with a hot cup of coffee. That was enough to call it a good run.

Pacing discovery on the treadmill

Today's run (treadmill): 2.4 miles at 9:08/mile

Although I was fully prepared to run on the treadmill when I set up my gear last night I felt a little differently this morning. The alarm woke me up from a sound sleep and made me question whether a workout or thirty extra minutes of sleep would do me the most good. I would have liked the extra sleep but I knew if I didn't run I'd feel guilty for the rest of the day. Despite its negative connotations, I truly believe that guilt has its good side. I had a little coffee and got on the machine, resigned to running a couple of miles.

As I started my run I compared the pace on the display to the pace on my Garmin that I knew was accurately calibrated. The two readings were closer than I'd expected them to be. I increased the tread speed and saw that the paces changed in sync with each other but once I got to target speed I found that I could achieve a faster pace on the Garmin, compared to the treadmill's, just by quickening my cadence. When I resumed my default running rhythm the Garmin's readout resumed duplicating the treadmill's. It was an interesting discovery because now I know I can naturally speed up or slow down a little without needing to mess with the treadmill's controls. That makes a big difference to me because much of my frustration with the treadmill is from the tedium that comes with being forced to maintain a hardwired pace.

Although I started off tired I did rebound and got through 2.4 miles at a decent pace. I don't know why I find treadmill running so much harder than road or trail running but I do. Still, I rather it be that way than the other way around.

Sunday run with the Emerging Runner Girl

Yesterday's runs (street): 4.4 miles at 9:02 + .75 mile fun run

Counting Friday's run in the city, I managed to cover a little more than 12 miles this weekend. Out of those twelve my favorite experience was on a distance less than a mile (more below). With last Tuesday's 4.8 miles in Central Park and another 2+ miles on Wednesday, I still fell short of my informal weekly goal of reaching 20 miles. Of course if I include the 2 miles covered on the elliptical last Thursday I'll be able to claim that goal. Okay, done. 21 miles for the week!

As hoped, the rain slowed down by early Sunday afternoon and I took the opportunity to hit the neighborhood streets. I don't generally do my best speed running at 1:30 in the afternoon but I tried to keep the pace as brisk as possible. Due to the wet roads I wore my Adidas Response 15 trail runners. That was less for protection on the slippery road service and more to keep my Brooks GTS 10's from getting wet and dirty. I ran about 1.5 miles on local neighborhood streets and then cut over the neighborhood #2 for the bulk of the run. Since I was running in trail shoes I took advantage of a few areas alongside the road that had packed dirt and grass. It was pleasing to hear the chirp of the Garmin as I passed the two mile point. The third followed surprisingly soon after the second. At one point I looked at the watch and noticed that it was giving me readouts that said "00:15 ahead" which confused me. I then realized that when I updated the FR60's firmware yesterday it switched to a default setup that included a virtual running partner. I would have had fun with the virtual partner if I better understood the interface. I again relied on my heart rate monitor to guide me in terms of effort. My pace seemed fast for those conditions but, after verifying on Gmaps, I confirmed that the Garmin was accurate.

When I got home from my run I was met by my 11 year old daughter who had been riding her scooter and waiting for me to return. We decided to run a loop around some of the local roads and covered .75 miles between 10-10:30 mins per mile. Though it had been months since we ran together she kept up very well. My daughter has near perfect running form and she lands on her front foot naturally. I think she was happy when I told her that I learn things by watching her run. Next weekend I hope we will be able to cover more distance.

It's still very soggy in NYC and on Long Island so I'm not sure what outdoor running I'll be able to do during the week. I'm planning to get at least one Central Park run in before next weekend, assuming we see clear skies this week.

Racing decisions for May and June

Today's workout: Rain delay

I wasn't surprised to see pouring rain when I woke up this morning. All the same I was very disappointed. I'd held out hope that the weather reports would be wrong and that the storm would miss Long Island. No such luck. My issue with running in the rain comes from wearing glasses. A light rain is really no problem, it's sort of like driving through mist. But when the rain starts to come down hard it's windshield wiper time. Since my glasses don't have wipers, running through rain can be very disorienting. I'm surprised there isn't some rain protection invention for runners who wear glasses. I guess corrective goggles or using contact lenses would be my only choices. Neither option is too appealing.

The weather reports are indicating intermittent rain this afternoon so I may luck out for running later. I had hoped to run with a friend earlier this morning but it was just too wet at 6:00 AM. He and I are planning to try again next Sunday since I've decided not to do the RXR 10K race next weekend that would have conflicted with that. I may run one of the local 5K's taking place later in May or just skip this month for racing and focus on racing in June. There's the XTERRA Trail Series 8K at Stillwell on June 6 and the New Hyde Park 8K on the 13th. The Stillwell #2 race would be my toughest racing challenge to date. Stillwell #1, held this past March in the ice and snow, was very difficult even with the course cut down to 3.5 miles due to trail conditions. I ran New Hyde Park last year and struggled with pace, clocking in just under nine minutes per mile. I'll need to decide which to run in June. Maybe I'll run both.

A tale of two 3.5 mile runs

Yesterday's run (Central Park): 3.5 miles at 9:12/mile

Today's Run (street): 3.5 miles at 8:45/mile

Yesterday I was excited for the chance to do another run in Central Park. It was a busy Friday and I managed to wrap up morning meetings in time to change and meet up with my friend Steve for the jog up to the park. The skies were bright and the sun was out but the 57 degree temperatures felt cold on the building-shaded streets. We started our run at the 6th Ave. entrance on Central Park South and made our way to the lower loop to run counterclockwise to the north. Steve admitted to really feeling last Friday's workout for a couple of days after our run but he said he could do six today. I told him that he may feel differently once he started to encounter the hills. We set off at a decent pace, low 9's, and enjoyed watching all the activity in the park. At one point we were set upon by a group of tourists on bicycles who didn't seem to understand the concept of sharing the road with pedestrians. We also saw a person running around wearing Kangoo Jumps that look like in-line skates with elliptically shaped spring devices on the bottom. He certainly got some energy response from the shoes. Looked like fun but I'll stick to my Brooks for now.

Once we reached the reservoir we followed the path on the southern edge and then headed south. Steve was very glad at the 2 mile point that we weren't really going to run six. He did a great job keeping up with me and I told him his reward would be downhill running to balance all the hills we'd hit on the way up. We ended up covering 3.5 miles and felt fresh, even at the end. Good thing too because we both had long afternoons ahead. We walked south back to our offices, energized for the rest of the work day.

I woke up this morning with a headache that I attributed to sinus pressure. Rather than hoping it would just go away on its own I took a Sudafed and ibuprofen and chased them with a strong cup of coffee. I headed out around 8:00 AM for my run. I warmed up after about a mile and covered a route that took me first around and then through the neighborhood. I was concerned that the effects of the Sudafed would impact my running and while I felt tired I still managed to keep a decent pace. I originally thought I'd go 40 minutes but I cut it short to ensure I'd be ready in time for this morning's activity, an Arbor Day festival at a local preserve. I was pleased with today's run. I've programed the Garmin to automatically roll through the various metrics as I run such as pace, distance, time and heart rate. I used the heart rate numbers rather than speed to guide me in terms of effort to expend. It paid off with a decent pace, close to what I achieved recently in a 5K race.

Tomorrow I have plans to meet my friend KWL at a local park for a run at 6:30 AM. The weather is supposed to be pretty bad so chances are we'll need to postpone. That would be too bad but I can't complain about all the great running weather (and great runs) I've enjoyed this week.

Will geek appeal get me to the race?

Today's workout (elliptical): 25 minutes

I forgot to set my alarm this morning and slept about 15 minutes later than I usually do. Feeling tired and knowing this late start would cut into my workout, I briefly considered skipping exercise altogether. Thankfully guilt prevailed and I ended up spending about 25 minutes on the elliptical. It was sufficient to raise my heart rate and make me sweat. Other than that I can't remember a thing about it.

Tracking tag that's built into the bib

My racing plans have been on my mind lately. I'm still on the fence about whether I will do the RXR LI Marathon 10K the first weekend in May. I enjoy racing and I do believe it helps push me to higher levels of conditioning than I would reach were I solely a recreational runner. The thing is, I just raced a couple of weeks ago and I really just want to take a few weekends to get out and have fun on the roads and trails. It's different when preparing for a race where every run is about preparing to meet performance goals. On the other hand I've only competed in one 10K, a trail race, and I'm curious to see how I'd do in a road race at that distance. I did the LI Marathon 5K last year so the 10K would represent progress, or at least a new experience. I should be able to run 6.2 miles competitively right now without a lot of race-specific training. I have until Sunday to decide. That's when registration closes. They have a new system where your race number is also your tracking tag. The geek in me is really intrigued by that. It may be enough to get me to the starting line.

Central Park: once around for good measure

Central Park Reservoir (1.58 miles around)

Yesterday's run (Central Park): 4.8 miles at 9:18/mile

Today's run (street): 2.16 miles at 9:37/mile

Yesterday  afternoon I ran in Central Park for the second time in less than a week. I met my friend CK at the statue of the Maine in Columbus Circle and we set off with a vague plan to cover the distance to the reservoir and back. CK is still dealing with a foot injury that has forced him to scale back on his running in favor of other sports and activities. Like the last time we ran, he said he'd need to take it easy due to the foot injury. This time I knew not to believe him. CK laughed at me as I prepared the Garmin for the start. He's more old school, relying on time from his stopwatch rather than using an over-engineered running watch that captured distance, pace, etc. However, I noticed that he asked me more than once how far we'd gone during the run.

The sun was high in the sky but the heat was moderate. By the midway point I did find myself gravitating to the side of the road that had the most shade. By the time we reached the reservoir I began to feel the effort. CK managed to subtly push the pace past my default comfort zone. I wasn't exactly hurting but I felt like I was running at race pace although the Garmin's display did not reflect that. By the time we'd circled the reservoir and headed toward the east side of the upper loop I was ready to slow down. We ended our 4.8 mile run near the outlet to Central Park South and then grabbed some water to cool down. Once again I had a great Central Park run and CK pushed me hard, as always.

I tossed and turned last night and I believe that related to being so wired from the midday run. My plan for this morning was to cover two miles at an easy pace to balance the hard work from yesterday. I was suspicious that my recent recalibration of the Garmin led to under-counting my distance so I used this morning's run as a benchmark, comparing the Garmin numbers to Gmaps. Both came out exactly the same: 2.16 miles. I was hoping the Garmin was off which would explain why I felt I worked so hard yesterday and only managed a 9:18 pace. I guess I need to work a little more on speed. The hills didn't help but I can't blame them. What goes up one also comes down and it probably evened out in the end..

Keeping up with the older crowd

Today's workout: Central Park run (scheduled)

Yesterday was a busy work day but I'll admit to occasionally checking updates on the Boston Marathon during the race. An amazing record breaking run for Robert Cheruiyot and two Americans finishing in the men's top five. Later I looked at the searchable results to get a sense of the paces that people were maintaining over 26.2 miles. It's a given that the elites can run 5 minute miles all day but I was surprised to see how many "regular" people were hitting paces that I can't manage at a fraction of the distance. I looked at my own category and saw that age is no excuse for slowness. Seeing what my contemporaries did was in equal parts inspiring and intimidating. Then again, a couple of weeks ago, a 73 year old man beat my 5K finish time by 37 seconds.

I'm heading out at lunch to run with a friend who has a few years on me but can outrun me any day of the week. We're going to Central Park to run about 4 or 5 miles. Temperatures will be in the low 60's with sun. I'm hoping I can keep up and I'm glad I've made progress on the hills because there will be a number of them. My friend has been plagued with a foot problem and he claims that will force him to hold back a little. I've heard that one before!

Which race to race?

Today's workout: Rest day

My city run last Friday was a great lead-in for a satisfying weekend of running. It's rare that I string three days of excellent running in a row like that so I appreciated it all the more. All that running has made me think about my summer racing schedule and the races and distances that I should target. We're more than halfway through April and I've still not decided how, or even if, I'll compete in May. I've considered the RXR LI Marathon's 10K, stepping up from the 5K that I ran last year. The 5K course was flat but uninspiring, more like running in an industrial park than on a race course. Except for that, there aren't many local races to choose from in distances greater than 5K. I love running 5K's but I'd like a little more variety and distance right now.

June has the opposite challenge. There are two races I'd like to do - the New Hyde Park 8K and the XTERRA trail series second Stillwell race. As I reported back in March, the first Stillwell XTERRA was pared down to about 3.5 miles due to icy conditions on the trails. Even at that length it was a great struggle to manage that course. The June race won't have the ice factor so the run will be an 8K over difficult terrain. Even with my daily running, hill training, cross training and passion for the trails I'm concerned that I could run competitively that day. I would train even harder than I did for the first one and I think I'm in better shape than I was in early March when I was still dealing with residual issues from pneumonia. The New Hyde Park 8K is a less interesting course than Stillwell but I've felt like I had a score to settle because the original race result posted me at 9:00 per mile and I really wanted to break 9 minutes. I checked the results again and they now have me listed under 9:00 so that argument is moot. I'm going to take a look at the RXR 10K course map to see if that route is more interesting than the 5K. I still have a little time to decide on June's challenge.

Breaking 9:00 at Stillwell on my pre-birthday run

Today's workout (trails): 3.9 mile at 8:58/mile

I was concerned that between Friday's long run in the city and yesterday's brisk run in the neighborhood that I'd be too tired to do much in terms of a workout today. A year ago I ran my first race, the 2009 Marcie Mazzola 4 mile run. I didn't place in my age group that day but I walked away with a prize nonetheless. It was a $50 gift certificate to a local restaurant which I won because I had the closest birthday to race day. Tomorrow is my birthday but we're celebrating it today because it's the weekend. There's lots going on today so I decided to indulge in a trail run before things got too busy. Yesterday's overcast weather had transitioned to sunny skies by 8:00 AM today and the cool dry air made for perfect running weather.

I've become familiar enough with Stillwell to navigate it in a semi competent way. Between my basic knowledge of the trails and the direction of the sun I can usually make my way around without getting too lost. I successfully found the Black Trail this morning and followed it for a while. As I ran through switchbacks and roller coaster elevations I recalled that we traveled that way along the Xterra race course. I eventually reached a fork and had to choose a direction. I noticed a couple of runners a few hundred feet ahead so I began to follow them. There were lots of runners and mountain bikers on the trails today and everyone I encountered was friendly and polite. I caught up with the two runners ahead and passed them quickly. A few minutes later I came around a bend to find about six other trail runners who may have been waiting for the two that I'd just passed. We all said hello as I passed and I heard one of the woman say "I don't think I could keep up with him." Ha! If she only knew.

I wore my new iPhone armband which is better made than its predecessor but I had trouble getting it tight enough on my arm. I do have some upper arm development but this holder seemed like it was made for bigger biceps than mine. I used MotionX to record my path and I'm always surprised when I see where I ran versus where I thought I ran. I didn't go as far east as I planned but I covered a lot of ground north to south and finished with a loop around the open field trail. I ran faster than usual for a trail run and I noted again how well my Helly Hansen Trail Lizards handled all types of rock, scree, roots and sand without a problem. I've done a lot of running over the last week and I feel very good about my performance. Tomorrow is the Boston Marathon. I'll enjoy that vicariously on my rest day.

Time to calibrate the FR60

Today's workout (street): 4.17 miles at 8:57/mile

Yesterday's run felt so effortless that I wasn't ready to stop when we reached the end. Business took priority over pleasure but I did feel great for the remainder of the work day. The run itself was work and I felt the effect of all those hills this morning when I woke up. Still, I was anxious to get out for another run. My wife and kids were volunteering at my son's elementary school all morning. I had nothing on the calendar until after lunch so I headed out for my run around 9:00 AM with temperatures in the the high 30's under overcast skies. My Garmin was fairly quiet so I knew I was within pace range although a check of the display showed my pace to be a little slower than it seemed. I stepped it up after the first mile and would periodically surge for 30 seconds to a minute before falling back to my default pace. I was running faster than yesterday's city excursion and I felt the difference. All the same I didn't feel that I was working that hard and the data from my heart rate monitor confirmed it. I felt like I had covered a lot of ground but I ended up only going a little more than four miles. It was just far enough to count as a good workout.

When I finished the run I checked my Garmin and saw it displayed 4.07 miles, averaging 9:10. 9:10 isn't a bad pace and I figured that yesterday's run had wore me out more than I'd thought. I then mapped the exact route using Gmaps and saw that the Garmin under-counted the distance by 2.3%. Adjusting my pace for that variance, my overall average was under 9:00 (8:57) and my splits were 8:54, 8:57, 9:03 and 8:59. Love the FR60! I'm going to try to calibrate it a little closer so I don't have to do so much math. I haven't messed with the calibration adjustment on the FR60 yet. The default accuracy is +/- 3%. It wasn't all that easy to adjust the 50 so I'm hoping the 60's controls are better. My problem with calibration is that I switch my foot pod often between my pairs of street and trail running shoes and every change affects the calibration accuracy. Overall, I'm happy with my recent runs and glad that I've made my way down to the low 9:00's that I was running prior to my pneumonia disruption. I don't know what I'll run tomorrow. The skies are looking ominous but I'm hoping that this passes and that the trails are in good shape by Sunday.

I tortured my banker but, hey, great run today!

Riverside Park, NYC

Today's workout (street): 5.5 miles at 9:33/mile

I don't think my friend and investment banker, Steven, knew quite what he was getting into when he agreed to run with me today in the city. I had proposed a route that would cover 3.5 miles with an option of running or walking another mile back to our office buildings at the end. Prior to today, Steven had not yet run three full miles and most of his running had been on the treadmill. He was willing to push himself today and the route, which should have taken us from 6th Ave. to the West Side bike path to 72nd Street and then through Central Park, looked straightforward on Gmaps.

We set out at a brisk but manageable pace, the skies were overcast, the air was cool and dry and the river provided a great view to our left.  Everything was going fine until we passed the 2 mile mark along the bike path. We could not find any signs that told us how far north we had run but I knew that we were getting close to the 70's and I started looking for a cutout that would take us under the West Side Highway and lead us east towards Central Park. There was no obvious exit point and by the time we found one we were already up around 88th Street. After some experimentation we made our way to Riverside Drive and headed south and east until we reached the park.

When we passed the three mile mark Steven was pleased with his personal distance record. The extra blocks added  two miles to our planned distance and by the four mile mark he was having some trouble with the hills. We slowed the pace until he felt comfortable and then hit a downhill stretch that he greatly appreciated. I have to say that the hills were hardly a challenge for me today. I guess all that training for last week's race has paid off. By the time we reached the bottom of the lower loop in Central Park my Garmin was showing 5.4 miles and Steve was pretty exhausted. I encouraged him to run another tenth so he could say he ran 5.5 miles. I felt remarkably good and could have easily gone another five.

I felt a little guilty for torturing my friend but I kept encouraging him to stop if he needed to rest but he carried on without complaint. If I pushed my friend too hard today it didn't discourage him as we agreed to do another run next Friday, schedules permitting. I'm planning to run with my friend CK next Tuesday. The last time we ran I was the one who had trouble keeping up. I hope I do better next week. If not, I only have karma to blame.

A little Sole and a lot of X1

My BH Fitness X-1

Today's workout: Treadmill and elliptical, 26 minutes

I haven't been on the elliptical for a while so I thought I'd return to using it this morning for a change of pace. I prefer running over most other workout options but I also recognize the benefits of cross training. The elliptical, with its no impact motion, along with some upper body resistance, provides a good workout. As a bonus, it's user powered so it operates fairly quietly compared to other gym equipment. As I prepared for my session I couldn't ignore our Sole F63 treadmill that now operates correctly since a technician realigned the belt and replaced the motor last week. I had not used the machine since this work was done so I was a little curious to re-experience running on the now-stable unit. I decided to run for about five minutes, just to confirm that the belt slipping had truly been cured. I hit the 6 MPH button and started running, edging the speed up to about 6.7 after a minute. The treadmill worked fine but I wasn't enjoying the experience at all. Unlike my wife who is able to focus daily for 45 minutes on this machine I could not wait to stop. No matter, with all the rain we're expecting this weekend I'll likely be spending a lot more time on it in the coming days.

After about five minutes I switched over to the elliptical, setting the resistance to generate 75 watts (medium high) and starting at a fairly fast pace. The treadmill warm-up helped me get to speed quickly and I continued for about 21 minutes. I've said before that the elliptical provides a deceptively effective workout. It doesn't seem as hard as running but the sweat index is often greater. I've compared my heart rate between a treadmill run and an elliptical session (of the same perceived level of effort) and noticed running definitely provides a more elevated pulse rate. Different benefits and different effects. That's why we cross train. I'm due to run in the city tomorrow with a friend (weather permitting) and I have a Central Park run scheduled with another friend, CK, on Tuesday. That walk in Central Park on Monday made me wish I was running that run/bike loop. Next week I'll finally get to do it.

My iPad moment

Today's run (street): 2.5 miles at 9:19/mile

I have not been one of those people in the media technology world who view the iPad as the Thing That Will Save Publishing. My iPhone experience has been occasionally frustrating and inconsistent but I still wouldn't go back to the Blackberry. Unlike others I know (e.g., Sedentary Man), I refused to buy an iPad because I didn't understand it from either a value or utility perspective. Imagine my surprise yesterday when my IT person stopped by with a white box containing a shiny new iPad, courtesy of the CIO. The first thing I did was boot it up and look at The Emerging Runner on the browser (no Flash - argh!). The second thing I did was go to iTunes to see if they had any interesting running apps. Not much there. AG kidded me that I really shouldn't run with it (besides there's no GPS!). I was going to use the iPad to write today's post but I found it difficult to position the tablet and type within the confined space of an LIRR train seat. I'm hoping that this tablet will find its place in my technology portfolio. More to come on the iPad/running intersection as things develop.

Although I bought a new armband to carry my iPhone on my runs to record time and distance, I still haven't used it. The Garmin FR60 is proving to be a great purchase, capturing everything but a a route map and elevation. It's a much better running watch than the 50 that it replaced. I went out this morning with temperatures reported to be in the middle 30's so I wore an additional layer over my long sleeve tech shirt and was glad I did. I forgot to wear gloves and my hands froze the entire time I was running. I have to believe it was closer to freezing than the posted 36 degrees. The run felt fine, energy level was good and I tried to push it a little near the end. That didn't translate into a fast pace overall but the handy run report on the Garmin confirmed that I did negative splits after mile one. I'm planning to return to the treadmill tomorrow since the weather may be iffy and I haven't used the new machine since it's been fixed. I have plans to run in the city on Friday, weather permitting.

Runner's envy in Central Park

Today's run (street): 2.4 miles at 9:06

I didn't run yesterday but I took a three mile walk at lunchtime to Central Park. My route followed the lower loop and I included a few side paths as well. It was perfect weather for walking, bright and sunny, but cool enough for me to be comfortable in my suit jacket and tie. I watched enviously as runners, cyclists and in-line skaters passed by. I really wished I was running on the bike path rather than walking along the pedestrian strip. The park was filled with people, but my surroundings had a quiet (but positive) feel. Central Park is truly an oasis within mid-town Manhattan and I wanted to spend more time on my walk but I really needed to head back for a meeting. The only negative was that all that walking was rough on the bottom of my feet and I was in a little pain by the time I'd returned to the office.

This morning I went out for my first run since Sunday's race. Due to resting for two days prior and one day after the race, I've only run about 10 miles over the last seven days. It was great getting out at 4:00 AM but it felt far chillier than the 49 degrees that the local Long Island television station reported. I was concerned that the irritation from yesterday's walk would have a negative impact on today's run but with a good pair of socks and my trusty GTS 10's, I had no issues at all. I started my run on a street with a slight (~2%) elevation and re-lived the running of the big hill on Sunday. Of course today's challenge was shorter and far less steep. It was just enough to get my body temperature to a comfortable place and I headed into the next series of roads, listening for the chirp that would tell me I'd passed my first mile. I encountered no cars and the only sounds were birds (and my Garmin) chirping, interrupted occasionally by the clattering sound of a lawn sprinkler. I felt I ran harder than normal and ended up averaging 9:06 per mile, which is a good pace for me at that early hour.

Note: I want to give a shout out to my friend FS who also raced on Sunday (NYRR "Run as One" 4 miler). She maintained an impressively fast pace (low 9:00's) - a possible PR for that distance.