A chilly, windy, wonderful run

Circuitous route

Today’s run (street): 5.6 miles

Yesterday’s steamy treadmill workout reminded me that we’re not quite done with humid days. All I hoped for this morning was clear skies so I could get outside for my run. What I didn’t expect to see were temperatures in the mid 40’s — cold even for early October. Goodbye humidity and hello dry air. I was thrilled.

45° is chilly enough to wear long sleeves, yet warm enough for shorts. Since I’m more concerned about comfort than fashion, that’s the combination that I went with. The stiff wind from the west made things occasionally unpleasant. Changing direction along today’s circuitous route helped to keep things manageable.

Unlike last Sunday’s long run, I didn’t encounter too many oddities along the way. I did notice that the Justice Monkey sign was replaced by a small kick board that someone had hung in its place. Once again, puzzling and strange. I also followed a skateboarder down one of the longer roads. I tried to stay with him, but was never able to catch up. How fast do skateboards go?

I would have liked to do a full six miles this morning, but I needed to get back in time to meet our day’s schedule. Even so, it was great to be outside and running in the crisp fall air. A review of the run data shows that, despite replacing the battery in the foot pod, it didn’t record my cadence. That was disappointing because I tried to work on that and would have liked to see the results. I’ll probably have to re-link the foot pod to my Garmin 210 to make it work again.

Hoka Clifton (top), Saucony Kinvara 5 (bottom)

Today’s run was a nice antidote to yesterday’s treadmill slog and I hope this cooler weather sticks around until next weekend. I’m starting to think about replacing my Virratas and I’m on the fence on whether to stay with a minimal platform (i.e., Kinvara 5) or join the new wave of cushioned running shoes that Hoka started. After running in Hattoris, Kinvaras, Pure Drifts and Virratas over the past four years, I’m open to a change.

Running against the clock

Home with time to spare

Today’s run (street): 3.7 miles

Fall is a busy season, especially on weekends. All summer I could usually count on having enough time on Saturday mornings to get out for a five or six mile run without having to start at the crack of dawn. Lately, that’s not been the case, and I did the best I could with the short time I had to run this morning.

I usually run against a distance target, but today I needed to get my run done by a certain time and live with the mileage. Instead of setting the display on my Garmin to show elapsed time, distance and mileage, I kept it on the clock. I knew that no matter where I was in the run, I needed to be back before 7:15. I was fine with this because it was nice not having my average pace flashing at me every time I looked at my watch.

I was cruising through the neighborhood, feeling liberated from the Garmin’s judgement, when the watched chirped, indicating that I’d reached my first mile. I realized then that even though I didn’t have the distance display up, the Garmin was keeping track. I looked at the time and saw what was left and felt pressure to accumulate some mileage before I had to be home.

I can’t say that I significantly increased my speed once the Garmin announced my progress, but I did gain about ten seconds on each mile that followed. I managed to get home a minute sooner than my deadline. If I was late, Mrs. ER would not have been pleased.

Tomorrow I’ll try and take advantage of having more time and get out for at least 5 miles. Fall may be busy and disruptive to my running schedule, but the weather is far more running friendly.

Numb Runner

Distance lost

Today’s run (street): 5.4 miles

Instead of heading out this morning with my running buddies, I was at the dentist having a broken filling repaired. I like to get out as early as possible on my weekend runs, so I can cover longer distances and still have my day. If I scheduled the dentist any later in the morning, the inevitable backups would have taken too much time. That’s why I’d asked for the first appointment of the day.

It’s been years since I’ve needed to get a local anesthetic at the dentist, so that was lots of fun (not). My dentist talked to me about Cow Harbor. She lives in Northport and has run the race a couple of times. I told her I’d run it this year if she does. I’m pretty sure I will participate either way, so I can run it with SIOR and TPP. I’m still on the fence about Dirty Sock though.

Since I have so few opportunities to run these days, I knew I had to get out today. The weather was ideal, mostly overcast, with temperatures in the low 70’s. One side of my mouth was still unpleasantly numb when I set off from my driveway. Almost immediately after starting, I was flagged down by a man on a bicycle who asked me a question about the neighborhood. I stopped my Garmin while I chatted with him, and thought I’d restarted it once I resumed running.

I had covered about 1.5 miles when it occurred to me that I hadn’t heard the one-mile chirp from the Garmin. I looked at my watch and realized that it wasn’t recording time or distance. I restarted the timer, figuring I could determine my mileage when I got home by mapping my route with Milemeter. Since I had started off with the Garmin recording my start time, I was able to back into my pace by subtracting the “chat” time from total run duration.

Surprisingly enough, my mouth was still a little numb by the time I got home and that prevented me from having my usual post-run refueling. I did drink about 24 ounces of water to re-hydrate. Within an hour, the numbness had thankfully worn off. Between the dentist and the run, I was fairly wiped out, so that came at a perfect time for lunch. I was glad to get in some decent mileage today. I’m not sure what I’ll do tomorrow, because the family has early morning plans. Maybe a 6:00 AM run is in order. That might help prepare me for even earlier workouts on weekdays.

My Garmin lied and the truth hurts

My Garmin made up most of this route

Today’s run (street): 3.75 miles

Halfway through today’s run, I glanced at my Garmin and saw that I had covered two miles in about 17 minutes. That would have put me on track for my best training run in memory. I was puzzled because my perceived effort was nowhere near what I’d expect for that pace. I tried to rationalize the reasons for such a dramatic improvement in my performance compared to yesterday. It was 10 degrees cooler and cloudy, but could that account for running over a minute per mile faster?

When I got home and saw my time and mileage on the Garmin, I thought I’d rocked it. Maybe I was turning a corner with my training. After all, I used to regularly average 8:45 paces on my daily runs. Breaking 9:00 minutes on a run these days is a notable achievement for me. I hoped it was accurate and not some weird Garmin fail.

Despite that wishful thinking, it did turn out to be a badly confused GPS. For some odd reason, the Garmin put my starting point 3 miles north of where I began my run. Looking at the run data through Garmin Connect, my course appeared to have frequent 50-foot elevation changes. That’s definitely not the case for my relatively flat route. I’m guessing that the low cloud cover may have interfered with the GPS signal and caused it to skip.

I Gmapped my route and was disappointed to see that I’d only covered 3.75 miles, rather than the 4.35 that the Garmin said I’d run. I wanted to run 4-5 miles today and thought I’d met my objective. The good news is that I beat yesterday’s pace by 42 second per mile. The other good news is that it’s a long weekend and tomorrow we’re hosting a Runsketeer pool party. If the weather reports are accurate, the skies will be clear and I’ll be able to get in a longer run in the morning.

Uncooperative Garmins can’t spoil a good run

And taking its sweet time doing it

Today’s run (street): 4.25 

Despite Wednesday being National Running Day and finally getting access to my company’s fitness center, I haven’t been running. Work is the culprit and I haven’t figured out how to get in my weekday workouts without reverting back to 3:30 AM runs. Ironically, I can be extremely flexible in terms of my morning timing, but I prefer to be on the road very early to beat the heavy traffic.

I did attempt to use the fitness center yesterday but traffic was terrible and I got in a little late. The result was a fairly crowded locker room, along with the realization that I lacked both a combination lock and soap for my après-run shower. My wife has since packed both items in my gym bag, so I’ll be better prepared next time. I still don’t like sharing a locker room with co-workers, but I’ll have to get over that.

I worked from home today and that provided an opportunity to do a run around the neighborhood. Once again, it took an annoyingly long time to get a signal on my GPS. I was concerned because I had some calls in the morning and every minute I waited (it actually took ten) was a minute less that I could run. The progress bar finally made it all the way across and I was on my way.

In the past, my first run after so many days away would almost guarantee a great experience. I wouldn’t define today’s run as great, but it met my need. It didn’t hurt that the weather was perfect. I haven’t looked at the Garmin data yet, so I don’t know my splits. Overall, I did better than I expected.

Tomorrow is a Runsketeer group run and I’m looking forward to seeing my Runska-buddies for the first time since we ran the Brooklyn Half. I’m not happy to be cramming all my week’s running into three weekend days, but it’s the only option I have right now.

The history of my running speed

Directional declines

Today’s run (street): 3.6 miles

I decided to do some data mining on Garmin Connect to compare my historical averages with my current performance. In order to keep the information consistent, I only used data captured from one source, my Garmin 210 that I bought in 2010. I know I’ve lost a lot of speed over the past year and my interest was in seeing whether my recent history is an aberration, or if it merely reflects a long term decline.

Charting the trends reveals a changing relationship between race speed and overall speed. My average pace has followed a linear decline, but my race paces have dropped measurably since 2012. Up to 2012, I generally paced 7.5% better in races compared to my overall average. After 2012, that gap has closed and is now almost equal to my training run times.

As I often say when working with business data, these findings are only directional. The Garmin data, acquired by GPS, has a variable margin of error. I tried to correct for that as much as I could, but the numbers do have some skew. I only selected runs I’d tagged as “street running” to filter out slower trail paces and faster track paces. It’s also important to note that the 2014 data is only through May 25, not a full year.

In terms of these findings, I’m not happy to see declines, but at least the drop-off has not been as sharp as I’d suspected. I did today’s run as a tempo, taking it easy through the majority of the distance and picking up the pace more at the end. The last mile was a minute faster than the prior few, and I finished feeling great. I wish I could tap into that speed more often, but based on my recent race performances, it’s a little more complicated than just trying a little harder.

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.

Despite real evidence, a puzzle remains

Cadence confirmed

Today’s run (5.3 miles)

This morning’s run brought me closer to understanding the impact of the metronome, but there is still a missing piece of the puzzle. I put a new battery in my foot pod and clipped it to my shoe for the first time since I bought my Garmin FR210 in May 2011. The FR210 uses GPS, but the foot pod allows me to capture my cadence during my run. It’s a metric I’ve missed having when I analyze my performance data.

The good news is that I now have proof that the metronome works. I set the app for 87 SPM before I started and the data shows I averaged exactly that on today’s run. This is no coincidence. I have mounds of pre-FR210 data that shows that (at best) I used to average 83 SPM on a training run. The cause and effect of the metronome’s beat could not be clearer. All I have to do is jump it up to 90 SPM and my performance is optimized. Problem solved!

(Cue sound of record scratch)

What? That’s not the whole story?!! Indeed it is not. While there seems to be evidence supporting the effectiveness of a metronome, the result of today’s 87 SPM performance was an average pace of 9:42 per mile. I measured my route using two different browsers (Milemeter is behaving much better now) and they were pretty consistent, so I’m going with that pace. So cadence improves, and my pace gets worse. Huh?

The last puzzle piece clearly involves stride length. It’s likely that I’m achieving my SPM target by maintaining a shorter stride. It makes sense that opening stride length with an increasingly higher cadence will bring my pace down to my targeted level. Sounds easy, but we all know the danger of over striding. I think I’ll take one victory at a time and work my way up to 90/180 SPM and see what that gets me. Once I can do that consistently (and without the need for a metronome), I can start experimenting with stride technique.

Running in the morning and (multi) culture at noon

Eye of the tiger (actually lion)

Today’s run (street): 3.75 miles

I needed to get out early this morning for my run, so I deferred a visit to Stillwell or Bethpage until (possibly) tomorrow. I had more time than yesterday, so I figured I’d try to cover a little more distance. In an attempt to shave off a few minutes, I turned on the Garmin while I was still inside. I thought the chances of acquiring a signal were low, but I figured I’d try. Amazingly, while still in the house, the Garmin was ready to rock in about ten seconds. When I turn it on while standing outside (under clear skies), it can take five minutes or more to go to ready mode.

In keeping with my policy of never running the same route twice, I departed from my usual starting street in favor of another road to the west. I continued to choose less traveled roads until I reached a point that put me back onto my usual route. I ran easy today because I ran fairly hard yesterday. It wasn’t a fast run, but all considered, it was still in the range of acceptable performance.

Indian music, dance and drum

Korean synchronized drumming
Lion dancers
Japanese calligraphy
Thai dancers

Multi-cultural parade

I returned home and quickly took a shower, knowing my wife would soon be back from a morning coffee date with a friend. We immediately headed out to a multinational cultural festival that was being held at a local college. This event, that was sponsored by the Asian-American Cultural Circle of Unity, had many exhibits that featured food, art and local products from around the world. There were many performances, including Korean drummers, Chinese lion dancers and numerous musicians.

We all had a great time, and I recommend this free event to everyone!

Happy resolution, happy morning run

I should design a route that spells out my name

Today’s run (street): 4.5 miles

The outcome of the manhunt for the surviving Boston Marathon bomber ended with a live suspect and no further casualties. As good as that is, it’s important to remember that lots of innocent people were killed or maimed this week in the name of religious zealotry and hate. The Boston Marathon’s joy was hijacked for the benefit of no one. I only hope the city’s powerful reaction to the senseless acts this week will ultimately strengthen the event.

There are a couple of high profile NYC races this weekend and I fear that some weak-minded fool will try a copy-cat attack. I also worry that the London Marathon will have similar threats. I’ll never cease to be amazed by the level of depravity that exists in the minds of some people. Cowards will always look for easy targets.

Okay, back to talking about running! Less than half of my workouts over the past seven days have happened outdoors and I was determined to run outside today. It rained overnight and into the morning, so I waited until the skies cleared before going out. The temperature was 48° around 9:00 AM, so I dressed in shorts, but wore a log sleeved running shirt. That turned out to be a good decision, because the winds were strong from the south and the extra warmth was appreciated.

My Garmin annoyed me (once again) by taking over five minutes to lock into its signal. Standing in the shade of my garage was a chilly experience, but once I got moving I felt comfortable. I elected to run south on Jericho for a change, but the stiff winds forced me to duck back into the neighborhood. It was one of those situations where conditions were perfect in some directions and awful in others. Despite that, I felt great throughout the run.

I didn’t have a distance target, so I just followed roads until I found myself heading in the direction of home. I could have easily run a few more miles, but my son and I are planning to hike later and I wanted to keep some energy in reserve. It was a completely pleasant experience today and, for the first time in days, I was able to think of things other than the events that have played out around Boston. I’m really hoping that this weekend the races will be about the runners, and the stories will be all be happy.