Running Watchpocalypse on the Bethpage trail

Somewhere on that path sits half a Garmin.

Today's run (Bethpage bike trail): 5 miles (estimate)
Yesterday's run (track): 3.5 miles

On November 18, 2008, I published my first post on Emerging Runner. Today, almost eight years later, I'm publishing post number 2,100. I've covered many subjects over that time, and my tag cloud on the left lists well over a thousand of them. This blog has definitely accomplished my initial objective, serving as my training journal and an outlet for communicating with the running community. Writing 2,100 posts took a lot of time and effort, but it's been worth every minute. If it wasn't for this blog I wouldn't have met my Runsketeer buddies who I both adore and admire. Don't tell them though. It would only go to their heads.

Running is a simple thing, but it has its nuance. One aspect that fascinates and frustrates me in equal measure is the technology we use to gather running data. I've been through three Garmins over the past eight years and most of that experience has been good. My original Garmin, an FR 50, served me well until I accidentally destroyed it while replacing its battery. I replaced it with an FR 60 that improved on the 50 and has a far better battery replacement system.

About a year after buying the FR 60, I broke down and bought my first GPS watch, a Forerunner 210. It was big step up from the 60. I liked it a lot, despite occasional issues capturing a signal and the need to replace the data cradle after a while. Recently, the loop that secures the strap broke so I took the intact loop off my retired FR 60 to replace it. Soon after that, the FR 210's strap broke off making the watch unwearable. I returned the loop to the FR 60 and resumed wearing that watch on my wrist as a stopwatch while I secured the FR 210 to my SPIbelt using a keyring loop. That worked fine until today.

Yesterday's run - the FR 210's last map

Yesterday, I went to the local track to get in 14 laps before the sun came up. I had to be somewhere at 8:00 AM, so that was the best way to get in my miles. I ran well and have really taken to the NB Zante 2's that did great on the track. It was a typical track experience with the usual personas walking, running, sprinting and one guy who was throwing a medicine ball around.

This morning I headed to the Bethpage bike trail. My plan was to run about five miles, which I think I did. I'm not sure, because the god of watches decided to mess with both my Garmins today. My run started fine and I was in a great mood. The clouds hid the sun, but not the humidity. I made my way south from Haypath Rd and ran through Bethpage Park almost to the Parkview Court crossing. There were lots of walkers and it looked like a large group had come out together because many were wearing tees that said, "Move It." Early in my run, when I was halfway up a short steep section of the path, a runner coming north shouted, "I hear that hill is pretty steep today." I laughed because it was true.

I ran well despite the humidity and was about a half a mile to endpoint when I reached down to my side to look at the FR 210 and see how much distance I'd covered. There was nothing to grab and I discovered that my Garmin had fallen off the SPIbelt. It was probably sitting on the side of the path somewhere. I doubled back about a quarter mile, but was unable to find it. I was upset, but I've been planning to replace it since using it that way was fairly awkward.

Without a GPS map of my run, I figured I'd look at Gmaps when I got home and use the time from my FR 60 to calculate my pace. Annoyed, I ran the final half mile and about a hundred feet from the finish, my FR60 started to beep and the display blinked, "Scale Not Found" and then "Scanning." I couldn't turn off the message or get back to the timer (or turn that off for that matter). The watch would not respond to the buttons when I pressed them.

So in the space of five minutes, I went from having two functional running watches to none. When I got home I removed and replaced the FR 60's battery. That got it working, but I lost all the data from today's run. Before I could declare even partial victory, the watch started flashing "Scale Not Found" again.

It's time for a new watch, so my search begins in earnest. I doubt I'll have a replacement in time for next weekend. Until then, I'll rely on Gmaps and my $15 stop watch to capture my distance and pace. That should give me something to write for my 2,101st post.

Running blind to time and distance

One lacks GPS, the other lacks a strap

Today's run (street): 3.75 miles
Yesterday's run (street): 4.5 miles

They ran the Dirty Sock this morning and I cannot imagine how those poor runners managed through 6.2 miles of hot and steamy air. Make that wet air. Air that you can feel without a breeze. The humidity today and yesterday could only be described as brutal. Despite that, I did get out Saturday and today, although there was nothing about my running that could be mistaken for a racing level effort.

Yesterday was the first time I ran without my FR210 on my wrist since I bought it, and it was disconcerting not to be able to monitor time or distance. I put the watch in my SPIbelt and tried to listen for the chirp that indicated mile splits, but I was unable hear them. Without that information, I had to guess my mileage based on the route I was running. I was surprised at the end to see that I'd covered 4.5 miles in sweltering conditions. I got home and jumped in the pool wearing my running clothes. Learning from past errors, I carefully removed my phone, Garmin and Fitbit before diving in.

This morning I'd planned to get out before the direct sun added to the already hot day. Unfortunately, I didn't actually start until 7:40 AM. By then, the air felt like a steam bath. After yesterday's experience  running without either distance or time indicators, I decided to put a new battery in my old FR60. At least I'd have a stopwatch to reference.

Equipped with phone, Fitbit and two Garmins, I set off into the heat and humidity. I still couldn't monitor my distance progress unless I pulled my GPS watch from my SPIbelt, not an easy thing to do while running. I felt like I ran more than 3.75 miles, but in this weather, that was more than enough.

Running with 1 1/2 watches is going to get old real fast. My FR210 wristband has further disassembled past the point where I could repair it with this cool hack. I should probably buy another GPS watch, but that seems wasteful because both the watch and GPS part of my FR210 still works. I'm open to suggestions.

In term of this weekend's running, my paces today and yesterday were glacial. Still, I enjoyed the fact that I'm getting through every run without worrying when fatigue will kick in. Even though conditions were suboptimal, I never once wished these runs would end. If I had run the Dirty Sock today in this weather I would have gotten through it. But not very quickly.

Short and sweat

All the kings horses and all the black tape...

Today's run (street): 2.6 miles

So very hot and humid this morning. I probably should have stayed indoors, cranked the AC, and set the treadmill and floor fans to max. Instead, I decided to brave the mid-August swelter. I can usually endure any type of weather for three miles (or in today's case, something less to that) and would have done 3+ today, but I had very little time to run and shower before my first meeting of the day.

Gimme swelter

Despite conditions, I was eager to get outside,. When I picked up my Garmin, the bottom half of the strap separated from the top, despite the awesome repair work I've been doing with electrical tape. My sister-in-law told me about some material that will fix rubbery plastic like this wristband, but I fear it's too late to save the FR210.

I ended up taping the watch all the way around and that secured it well enough to get through 2.63 miles. I really don't want to do that every time I want to take it on a run. The watch itself works fine so I guess, for now, I'll stick it in my SPIbelt. There is a hack to fix a Garmin that suffered wristband failure, but it requires that the first two loops that connect to the watch case be intact. One side is beginning to rip, so maybe not.

So what to do? I can continue carrying it with me or I could buy another watch. I've had this Garmin for about five years and it has served me well. I don't like replacing technology that still provides utility, but in this case it wasn't the technology that failed me.

Unfrozen and back on track

You're pushing it Garmin

Today's run (track): 3.4 miles
Yesterday's run (street): 3.2 miles

It's almost the end of the school year and there's a lot going on. My daughter is graduating from high school on Wednesday and it also happens to be her birthday. With that conflict, we decided to celebrate her birthday today. Due to those plans, I had to get out early for my run. Even with that, I was pressed for time and decided to run laps at the high school.

Last night, after I'd downloaded Friday's run from my Garmin, the watch froze and it wouldn't respond, no matter which buttons I pushed. I tried to shock it back by hooking it up to the USB and then the wall charger. Neither attempt worked, so I left it for the morning. I figured I could run with a stop watch if the Garmin failed to respond.

When I got up, the Garmin was still frozen and I began to entertain the idea of replacing my six year old FR210 with a newer model. Things are starting to break on it and I noticed one side of the wrist band is beginning to separate. Before giving up on it, I looked online and found a video that showed how to unfreeze my watch. It worked.

The track was almost empty when I got there. Just me and a guy who spent a lot of time stretching while I circled the track. I was eventually joined by another runner who circled the track much faster than I did. I was prepared to count the number of times I got lapped but the guy quit after a couple of times around.

Lapping it up

The stretching guy eventually made his way onto the track. He was wearing one of those elevation training masks and started doing intervals. Or should I say, one interval. I ran four more laps before he did his next one. By then I was finished with my workout.

We had a great birthday celebration and I managed to get in a lot of Fitbit steps throughout the day. Tomorrow is Father's Day and I'm going to try to get out early again to maximize celebration time.

An entire post about a little rubber loop

If you look closely you can see my perfect repair job

Today's run (treadmill): 3.2 miles

I've had my Garmin FR 210 for over five years and I've been pretty happy with it. Sure, it sometimes takes more than five minutes to grab a GPS signal and a close look at the GPX file on Google Earth shows why there's always a margin of error in the reported distance. Those things can be managed. It's why I Gmap every run I do for exact measurement. However, there's one thing about Forerunners that gives me pause. If the strap wears out, it can't be replaced.

There are hacks I've seen online that address this flaw, but they're a little complicated. So far my strap has held up, but the retaining ring has broken twice. The first time it happened I was able to fix it with electrical tape because it broke down the middle. Today it broke again, this time along the edge where it's harder to wrap tape or otherwise secure it. I did my best to repair the loop, but it looks ugly and I worry that it will break and I'll lose my watch.

An online forum had a poster who suggested using a plumbing O-ring. But I'd have to go to Home Depot for that! Amazon sells one for $4.49. Maybe I'll make the investment, since they're offering free shipping. Based on all the posts about these things wearing out. I'm wondering why Garmin doesn't include a replacement.

I suppose I could go super low tech and use a small rubber band, but anyone looking closely at my watch may realize that I'm not quite the style icon they thought I was. For now, it's being held in place by a whole lot of tape. If it breaks, I'll have an excuse to buy the Forerunner 630 with a color display.

Knight sighting on my run

This jacket is actually neon bright

Today's run (street): 5.25 miles

While it wasn't a great week for running volume, I was glad to get a couple of decent runs in over the weekend. Yesterday's treadmill workout was the right way to go. For some reason, the running experience on our Life Fitness machine is much better than on our old Sole F63. Today I had the opportunity to get outside and was rewarded with perfect weather conditions.

 

Rain wasn't expected but the skies were low and cloudy with 55° temperatures and a 9 MPH wind. That was a chilly combination, so I decided to wear my new running windbreaker. Its high visibility orange color would stand out on a dark morning. I was concerned that the jacket's lack of venting would build up heat as I progressed through the run. I managed to stay comfortable by opening up the front zipper and letting in wind-cooled air.

I wanted to cover at least five miles today and that meant running on almost every street in the neighborhood. Not much to report, although I did encounter some guys dressed like Templar knights running around inside a small park with an un-costumed guy following them. I assumed they were filming their own sequel to Monty Python and the Holy Grail. I was tempted to stop and take a picture, but I was moving along well and didn't want to stop.

I received my replacement charging clip for my Garmin F210 this week and was able charge my watch without having to precisely position rubber bands to attach the broken unit to the watch. As I mentioned yesterday, my work schedule is getting a bit tighter. I'm committed to getting back to at least four workouts a week and will need to do one or two before my work day -- or after. Easier said than done.

Garmin design failure no excuse for a new watch

Mis-connection

Today's run (street): 3.25 miles

Having a day off on Wednesday certainly made my work week go by quickly. Before I knew it, Friday had arrived. Yesterday was an interesting day. Some organizational changes meant that I had a new team to manage. I was fine with that, although I only found out about it that morning. I was thrilled not to have to drive to my office today, and that allowed me to do my usual Friday morning, pre-weekend run.

I work from home most Fridays, and the lack of a commute gives me plenty of time for a run. I had an early meeting happening via Google Hangout that put pressure on me to run and get back in time to look presentable on camera. That meant getting my procrastinating butt out the door early. On the positive side, the recycling trucks had not yet made the scene. On the negative side, our quiet neighborhood was already being overrun by cars and buses speeding their way to the middle school.

It was 64° with a little more humidity than on Wednesday, but it felt cooler. This was likely due to wearing short sleeves this time. The middle school traffic eventually disappeared and I thought I'd caught a break. But right on cue, I saw a stream of cars and buses heading to the elementary school. I avoided those roads and finished up my run.

Later in the day, I took a break to download my Garmin data and discovered the charging-data connector had broken since its last use. The design of the FR210 is a step backward from my old (non-GPS) FR60 that connected to my PC wirelessly and downloaded data automatically. The FR210's connector has a set of copper pins that match up with contacts on the watch. The connector is held in place by a spring driven clasp. It's a terrible design and, now that it's damaged, I'll need to figure out a way to keep it connected for charging.

Although this would be a great excuse to upgrade to a more contemporary model, I really have no need for a newer GPS watch. A quick search on the web showed that I can replace the connector for $15 through Amazon - so that's on order. I have my issues with the FR210, but after almost five years, it continues to be a very reliable unit.

Cramming in my workouts

The Dirty Sock route

Today's run (street): 3.75 miles
Yesterday's workout (elliptical): 30 minutes

During yesterday's drive home I realized that I'd missed my morning workout window. I was facing another week with all my activity crammed into the last three days. I'm not likely to return to 4 AM weekday neighborhood runs, but I could run on the treadmill before getting ready for work on weekdays. And yet I don't. As I crawled along the Cross Island Parkway, I made the decision to do a workout when I got home.

I took little time changing into workout clothes and considered both the treadmill and the elliptical for my workout. My thought process went like this: 1) "The treadmill is real running and the elliptical isn't." 2) "The treadmill gets my heart rate higher. I can change elevation and even simulate downhill running." 3) "I hate the treadmill so I'm going to use the elliptical." With that, I turned on the big fan and had a surprisingly enjoyable session.

This morning I was determined to get out earlier than I have done on previous Fridays. At 6:00 AM I told myself I'd go out at 7:00. At 7:00 I said 7:30. By the time I changed for my run and put on sunscreen it was 8:00. By the time my Garmin acquired a signal, it was almost 8:15. So once again I found myself in the prime hour for dodging recycling trucks.

The weather was promising, not too hot and hardly humid. I felt good from the start and that continued throughout the run. About halfway through my route, I saw a car coming from the other direction around a tight curve. I tucked in behind a landscaping truck until the car passed by. Coincidently, it was my landscaper's truck and he was standing right there. We had a brief chat about how running and working in the heat kinda sucks and then I was on my way once again.

The rest of the run was relatively vehicle-free and the time went by quickly. I ran a little faster than I usually do, but it was still nothing to brag about. Tomorrow the Runsketeers will be taking to the trails to run the Dirty Sock course. It's been over a year since I've run that route and I'm excited that my friends will be running it for the first time. I hope conditions will be cool and the path will be dry. It gets very humid around there in August and muddy trails are why the race is called the Dirty Sock.

Turkey day morning run

Today's run (street): 4.3 miles

Happy Thanksgiving! It's so nice to be on break from work and being able to spend time with friends and family. It's also a treat to have time to go out for runs (weather permitting) every day. Yesterday's running plans were disrupted by the freezing rain, but this morning's conditions were much more favorable.

It was 33° and cloudy when I got my gear organized. My daughter decided to join me for the first part of my run and I was excited about that. We waited outside in the cold while my Garmin locked in on its GPS signal. It has been taking longer and longer to acquire a connection and I hope that doesn't mean that I'm going to need a new watch. Actually it would be great to get a new toy, but I've been very happy with the FR210. Once the display came ready, we were off the driveway and on the road.

Our route was a clockwise loop around the roads adjacent to my house. We moved along at an easy pace and chatted away. Once we completed the circle I left my daughter at the house and continued on to complete my run. A few minutes later I began to notice some snowflakes fluttering down and I loved the effect. That, combined with the crisp air, the scent of wood burning and the aroma of Thanksgiving cooking made for a very pleasant experience.

There weren't a lot of people out at 8:00 AM, but those I saw were in a friendly mood. I wasn't the only person in the neighborhood who was trying to get in a holiday run. I crossed paths with three other runners by the time I wrapped up my workout. The rest of the day has been filled with holiday activities and LOTS of food. Still more fun to come on that.

I plan to get out tomorrow to burn off the all these calories. I'm not sure what I'll do, but the weather is supposed to be sunny and cold. Congrats once again go to TPP who put in yet another great race effort today at the Town of Oyster Bay turkey trot. One of these days I'm going to return to the track and work on speed. Maybe tomorrow will be that day.

When running watches use German syntax

Don't not not change to Yes

Today's run (street): 4 miles

Things started off badly this morning. I failed to think through a question that was asked by my Garmin running watch, preventing me from tracking my progress. Garmin is a German company and they seem to use German syntax (subject before the verb) in their menus. So instead of saying, "Use GPS?", my 210 says "Use indoors?" with the default of "No." All that double negativity caused me to incorrectly change it to "Yes", which disabled the GPS function.

All attempts to cycle through the menus or otherwise cajole it to turn on the GPS were fruitless. Unless I was willing to do a full reset of the Garmin, I was stuck with nothing but a stopwatch. At least the HRM synched up. I decided to make zitronen into limonade and do the run by time rather than by distance.

My run went pleasantly through the first 20 minutes, but despite maintaining less than a 75% of max heart rate, I started to feel tired. My legs were feeling heavy and it reminded me of how I had some surprising struggles last winter, even on some shorter runs. While I was dealing with that, I crossed paths with a woman who came onto the street a block ahead of me. I couldn't tell how fast she was running, but I tried to catch up to her.

I made up some distance and remained close until she cut over to another road. Pushing speed when I felt like slowing down added to my fatigue, but I managed to recover after a few minutes. I started feeling stronger and was able to increase my pace for the remainder of the run.

Since I ran by time and not distance, I needed to Gmap today's route to get my mileage. I would have liked to have GPS enabled so I could see my splits, but I lost my chance by telling my Garmin, "Keine GPS für mich danke!" After 700 or so runs with this watch, I guess that was going to happen eventually.

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.