Today's fifty step run

No power, no problem, today

I originally thought the theme of today's post would be about my discovery that my Garmin was out of battery and that would force me to run outside without capturing any data. But that wasn't the way it played out. Instead, I ended up stopping my run almost as soon as it started. Nothing to do with technology this time.

I was actually looking forward to running free of big brother NAVSTAR as I geared up for the cold morning temperatures (29°). I'll admit that I wimped out and put on my Garmin 60 to use as a stopwatch, but I didn't connect the foot pod or the HRM. So technically I was running free. However, between elapsed time and Gmaps, I could still calculate pace and distance. And you know I would have.

After running fifty steps from my house on my way around the neighborhood, I realized that my hip soreness had not gone away. In fact it was fairly painful and I worried that continuing my run might only exacerbate the problem. I decided that getting in a routine run was not worth the possibility of further injury so I stopped, turned around, and headed home.

I iced the spot for about 30 minutes and then continued my day that included lunch with a good friend. I considered doing an afternoon run if my hip felt better (it does) but decided instead to give it additional rest until tomorrow. I may go for a trail run at Stillwell on Saturday. In the past, the dirt surface has provided a good, softer alternative to pavement. It's a good surface to run on when dealing with an injury. Of course, if the temperatures are still below freezing tomorrow, the dirt may be just as hard as pavement.

Echos of schedules past

Yesterday's workout (elliptical): 25 minutes
Today's run (treadmill): 25 minutes

It's been a very busy week and my schedule has interfered with my ability to publish my posts. I've had to resort to using the Blogger app on my phone in between engagements. I'm not sure how this will work, but here goes!

I've been going into the city the last two days for some industry meetings. The early morning wake-ups and commuting on the train were great reminders of my former daily grind. On both days I added long walks between Penn Station and Columbus Circle on top of my morning workouts.  I'm hoping I've impressed the Fitbit enough to earn another I LIKE U.

Yesterday morning I had one more go on the elliptical. I'm still not loving its rickety build, but it does provide a decent workout. I woke up this morning with some hip pain and I'd hoped that it would pass when I started my run. It didn't, and the pain continued throughout the day. The three additional miles I walked later in the morning probably didn't help it.

My hip's not bothering me too much at this point and I'm hoping to get back outside for a run tomorrow morning. I'm also hoping that the freezing temperatures and stiff winds are gone by then. I'm truly looking forward to a less intense day on Friday. How did I used to do this city thing five days a week?

Fitbits don't work across the room

Ouch

Today's run (treadmill): 3.2 miles

About halfway through this morning's treadmill run, I spotted my Fitbit sitting on the guestroom bed. I'm really into capturing my activity through that device, so I was a little nonplussed by the situation. While I was still capturing metrics like time and heart rate on my Garmin, all those steps would be lost to my daily and weekly totals. I considered stopping the treadmill to retrieve the device but decided that it wasn't worth the disruption.

Years ago, when my first Garmin failed during a run, I felt frustrated and asked myself, "If the run didn't record, did it really happen?" I know it sounds silly, but I once felt that way. A documented run is a tangible entity. Something that happened. Something to look back upon. A run performed independent of a watch or device doesn't become part of recorded history. I'll admit that on the rare times when I've gone out "watchless" on a run, I later Gmap'd my route so I could at least capture my distance.

Even without a device, running data on the treadmill is always available via the display. I don't fully trust the accuracy, but at least it provides ballpark metrics. I maintained a challenging pace through the workout and that took my mind off forgetting my Fitbit. So it looks like I'll need to wait a little longer to get my next Fitbit badge. Further, today's totals won't approach my daily goals. But I got a good run in today, despite the lack of evidence.

DST run with KWL at BSP*

*Bethpage State Park

Today's run (Bethpage State Park): 6.25 miles

Daylight Savings Time (DST) starts today and (for this one) we "Spring" forward. I wasn't thinking about that yesterday when I committed to a 7:00 AM run with a friend. In DST world, 7:00 AM is really 6:00 AM. By the time I got to bed, it was almost DST midnight. I somehow miscalculated all that and got up at 4:50 DST. So I ended up getting less than five hours of sleep.

My friend KWL arrived a little before 7:00. It was still dark when we headed over to Bethpage but it had lightened up in the ten minutes it took to get there. As I feared, the gates were up at the park so we quickly headed to Haypath Road. We were able to park the car in a spot that was adjacent to the Greenbelt trail head. This southern entrance put us on the newly paved section of the Bethpage bike path.

KWL and I started our run in 30° temperatures. We'd both dressed for the cold so we were comfortable as we made our way through the first mile. Our plan was to cover 10K easy, but easy is a relative term. KWL is a triathlete, accomplished cyclist and 1:40 half marathoner, so his "easy" pace is somewhat challenging to me. We happily compromised and settled into pace that worked for both of us.

The new section has some hills which I tackled easily, using my early run freshness to power through.  KWL loves inclines and I don't. On the other hand, he dislikes running downhill and I can do that all day. So in the rare times when I held the forward position, it was usually on a downward slope.

Along way we encountered a group running in brightly colored outfits. Both times we saw them they were about to run up a hill as we were running down. They were a cheerful, talkative bunch, undaunted by the challenge. KWL and I reached the 3.1 mile mark and immediately turned around to complete the out and back route. I was feeling a little tired at that point and wasn't looking forward to scaling the upcoming hills.

A few minutes after we'd met that challenge, I began to feel stronger. We picked up the pace with about 2K left to go. I'd thought that the trail extension would be easy, since (this time) we'd be on the better side of the hills. I'd forgotten that there were still some inclines going north. Before long, my Garmin chirped for 6 miles and we picked up the pace as we completed final quarter mile.

KWL and I both found the run exhilarating. Despite the DST change, we still had plenty of morning left. Today's experience reminded me how enjoyable it can be to run with company. I really should do that more often. Perhaps it's time to do something about joining a running club.

Searching for NAVSTAR and my next running shoes

Today's run (street): 3.1 miles

Wait time: 8 minutes

We had a late night last night and I didn't get up until 6:15 AM. That threw me off this morning's very tight schedule. By the time I went outside, my window for running was only 40 minutes. It was sunny and bright and I was glad to see that the roads were clear and runnable. This was somewhat surprising, since the temperatures were hovering around the freezing mark.

When I started the Garmin it looked like it would acquire a signal right away. Despite the clear skies, it took almost eight minutes before it finally locked in all the NAVSTAR satellites. This narrowed my running window down to 32 minutes. I'd watched the progress bar go almost to full, only to pull back to the middle. I had considered heading back inside to run on the treadmill, but I ended up waiting it out.

I set off on a rapid pace to help ensure that I'd make my minimum distance of three miles. A slight wind made the first half mile a little chilly, but it disappeared at the first turn. I felt fairly strong and figured I could maintain a low 9:00 pace without much trouble. I chose a set of roads that I expected would get me around the neighborhood and back in three miles and I ended up covering 3.14. It was an invigorating run and I made it back home a with a few minutes to spare.

While we were out this afternoon, I had the opportunity to satisfy my curiosity about two pairs of running shoes that I've wanted to try. I put on a pair of Brooks Pure Drifts that were one-half size up from the ones I'd tested for Brooks. My biggest criticism of the pre-production Drifts was the tightness on my toes on the lateral side. The toe box on the production shoes felt roomier, but I felt some ridging from the mid-sole on that side.

The other pair I tried was the new Saucony Virrata, a zero drop trainer with a surprising amount of cushioning. The shoe reminded me of the original Kinvara, but with even better response on toe-off. The shoes fit perfectly and I wanted to them on the spot. I decided to wait it out a little longer as my Kinvaras still have some life left in them.

Brooks Pure Drift production model

Saucony Virrata with zero drop mid-sole

My verdict on the two was that I'd run in the new Pure Drifts if I had them, but I would still want to compare them further with the NB Minimus, the newest Hattori and, just for fun, the INOV-8 Road X-Treme. The Virrata is another story. It's not a question of if I'd buy them, only when I'll do it. I'm hoping that the Kinvaras will last me another 100-150 miles. But if the stability of those shoes changes sooner, I'll be going Virrata shopping that day.