SIOR and I hit the Massapequa trail

Well Preserved this morning

Happy Bastille Day! Despite meeting my distance target for June (goal was 65 miles and I actually recorded 66.84, but who's counting?), this is the first post I've written in July. I now have more time to post and I'm running a lot more, but there isn't a lot to write about when every run is pretty much the same. Today I had the pleasure of running again with SIOR who accommodated my mediocre speed and actually had me pacing at a level I haven't seen in a number of months, More on that further below.

Back to the monthly mileage goal for a minute. I measure my runs using Gmaps to get a more accurate distance number than the Garmin records. This is because GPS watches have a technical limitation with the way they track vectors around corners and sometimes on straight roads. You can improve the accuracy by increasing the number of GPS "pings" per minute. It would be an easy fix, but battery life would be terrible. I've figured out that my watch generally under counts distance by about 2% so (technically) I probably ran 68.17 miles in June. But again, who's counting?

Today was not about distance or speed, although I ultimately covered 3.4 miles and paced better than my average. It was about getting in an easy run and having good old conversation. I haven't been able to keep up with the speedy Runsketeers in the past year, but SIOR made it easy for me.

We met at the Massapequa Preserve trail head at 7:30 AM with a plan to do a three mile out and back. After the usual game of Marco Polo (SIOR was in the big lot, I was in the small lot) we found each other. I had a big day Saturday up in Putnam County at Cold Spring and Bear Mountain and wasn't feeling great. I told SIOR that I'd understand if she wanted to run her pace but she was having none of that and we took off together.

This looks like a lot more than 3 miles

SIOR claimed she also wasn't feeling great and we stopped from time to time and walked. That may be true, but I think she may have done that because 12 minute paces hurt her knees. Whatever the reason, today was a throwback to the "early" Runsketeer days when I was better able to hold my own in these group runs. Some pretty funny conversations used to happen back then, with me and SIOR verbally jabbing and counter punching and TPP laughing and encouraging it all.

According to my Garmin, me and SIOR covered 2.6 miles actually running. Since we turned around at the 2 mile mark (SIOR correct me if I'm wrong) I suspect that we ran more than that. After looking at the GPS map that cut out a lot of our route and my step count on my Garmin, I'm sure we covered at least three, if not more. Here's one example of GPS malfeasance:

I don't remember running across the water

No matter the actual distance, we enjoyed it. We saw a big dog chilling in a stream and lots of other runners on the trail. I felt 100% better after my run than before it. Then there was only one thing left to do: coffee at Starbucks! You'd think after all that trail conversation we would have covered every  possible topic. But you don't know us. The thing that always amuses me when the Runsketeers get together is how little we actually talk about running. And that's just fine with me.

I wanted to record at least three miles today so I ran over to the nearby middle school and did 4 x 160 meter repeats and ran back home. That added another .8 miles to today's total and finished off my week with 16.5 miles. According to Garmin Connect, I'm at 36.26 miles for July which they say is 48% of of 70 miles. But my math (backed up by a calculator) says that's actually 51.8%. So what gives Garmin? Either way, I expect to reach 70, even with GPS under counting and Garmin Connect's "math problem."

The only spring in my run is new construction

Springing up in spring

Today's run (street): 3.75 miles
Yesterday's run (street): 3.2 miles
Last Sunday's run (street): 3.7 miles
Last Saturday's run (treadmill): 3.3 miles
Last Friday's run (street): 3.1 miles

I know it's been a while since I last posted, but here I am again. You're welcome. It's been a combination of busy schedules and the acknowledgement that my running journal-cum-social criticism blog has become somewhat redundant. The exception to that being my write ups of activities involving the Runsketeers. On the plus side, I've still been doing my runs and today I realized that the journal really helps me with the get outside and do it part. So here I am again.

Last weekend's runs were unremarkable, although I did have a good treadmill workout on Saturday. I don't remember the other two runs, but I know I did them because they're listed in my Garmin Connect log. Further, these runs even have my average stride length because I wrote to Garmin about that metric not showing up on Connect. Amazingly enough, Garmin responded that they'd corrected the issue. Apparently this was a problem for many. I was able to re-import my runs that lacked that data. and it showed up when I imported this weekend's activities.

My running has been dismal. With a few rare exceptions, I'm back to where I was last September in terms of performance. Slow doesn't begin to describe it. Yesterday morning I did an early run in light rain and just couldn't get into gear. I averaged 72% max HR which pretty much guaranteed a poor pace.

Today's route

Today's weather was far better, but my performance was exactly the same. I varied my route. Since I was running slowly, I took the time to look around my neighborhood. I noticed many new homes had sprung up in the places where prior dwellings were razed during the winter. These humble ranches and Capes Cods are being replaced big contemporaries that rise like Olympus above the Serengeti. Toto-ly stole that phrase.

Despite my lack of speed, I was happy to be outside on a cool and quiet spring morning. I know I can run faster, but lately I haven't been motivated to push too hard. SIOR is guilting encouraging me to re-enter the racing realm by running a 5K in July. She's even picked one for me. Okay, let's see what I can do.

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.

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.

History shows that January is treadmill month

 

Today's run (treadmill) 3.25 miles

Today has been an interesting day, due to an odd combination of business and non-business related happenings. Amidst this jumble, I managed to work in a treadmill run. Although the roads are fairly clear, we saw snow overnight that made street running dangerous and sidewalk running impossible.

I've been somewhat frustrated by this January's weather that has forced me off the road and onto the treadmill so often. I looked at Garmin Connect and was a little surprised to see that 70% of my runs this year have been indoors. Curiously, a search of last January showed that I did the same percentage of treadmill runs in 2013. That made me feel slightly better.

The good news about frequent use of the treadmill is that it eventually becomes a manageable routine. I've found myself getting more comfortable with the different cadence and a more restricted stride. It's always a good workout and a safer way to get my miles than the road these days. I wouldn't go so far as to say that I'm liking these workouts, but I have started to appreciate them.

Running views and visualizations

Sure looked like fall along the trail

Today's run (Bethpage): 6.25 miles

The Hope for Warriors 10K next weekend prompted me to head to Bethpage this morning for a base run. I've plateaued on distance since Cow Harbor, having completed only a handful of 5+ mile runs since that race. After a week of rainy and windy conditions, today's clear, dry 57° weather made a run at Bethpage very appealing.

More scenes from today's run

When I arrived I saw that the right side of the lot was fairly full. There were lots of people with bikes and I wondered if there was a cycling event planned. I don't think it was anything that formal, although there were a lot more bikers on the trail than I usually see. Considering the density of cyclists on the path, along with many runners and a good number of walkers, I encountered few reckless riders.

With my headache and sinus pressure gone, I felt good energy along the trail and felt less intimidated than usual by the big hills. That isn't to say that I particularly enjoyed them. My plan was run 5K south and turn around at the 3.1 mile mark. It works for me to break a middle or long distance run into parts. For that same reason, I like to familiarize myself with a race course before running it for the first time. It's always valuable to understand the challenges of the course before you face them for real.

New Garmin Connect cadence graph

I didn't dog the pace but I wasn't looking to simulate race conditions either. The purpose of this run was to get a 10K distance under my belt close to the real thing a week from Sunday. When I downloaded my Garmin after the run, I saw that they'd changed the data visualization on Connect and added a new metric: average stride length. Better still, the site has a pop-up that helps explain SPM and running dynamics. I felt good when I read this in the explanation: "The data values in the green, blue, or purple zones are typical for more experienced or faster runners."

Good context on cadence

Ideally, I'll see less green and more blue data points as I work to increase my cadence. Races tend to bring out our best performances (my recent history excepted) so I might even get myself into purple territory next week.

Comparing race times is easy but results are confusing.

A tale of three races

Today's run (street): 5.25 miles

This morning I downloaded my recent runs to Garmin Connect. I noticed a feature that compares selected runs, allowing users to see performance data by split (click above picture to read). The difference between this year and the last two year's times are easy to see. One thing that puzzles me is that the times on split 4 are really inconsistent. This year I covered .11 miles in 50 seconds at 7:55 pace, Last year it took me one second less but the pace was 7:18. In 2011, it took one second more to cover that distance, yet the pace showed 23 seconds per mile faster than this year. Very strange.

Today my thoughts were on recovery rather than performance. Due to my tapering, I covered far less than my normal 18-20 weekly miles since last Sunday. I took it easy and aimed for five miles. Although the temperature was a moderate 54°, it felt colder. I wore a light running shirt with 3/4 length sleeves and shorts, along with a pair of light running gloves. It was a good combination to start, although by the end I was wishing for shorter sleeves and no gloves.

I ended up running faster than I planned, but not all that fast. Recovery runs are a strategy to facilitate muscle repair and eliminate the built up lactic acid that causes soreness. I wish I'd taken it just a little easier. I'm looking ahead to November 10, when I'll be running the Hope for Warriors 10K. It's a great event (although the course itself is only so-so). My prep for this weekend's 5K fell short, and I want to do better. 10K means more base runs as well. Better get started soon.

Timing is everything with the Fitbit

Little bit, lots of Fit

Today's run (street): 4.3 miles

In life, timing can make a big difference. The big news that I'm leaving my company after 20 years was followed two weeks later by the yet to be confirmed news that my company is in talks to be sold. I'm unbelievably glad to be leaving before that happens. At the other side of the good timing scale, my company is (once again) offering staffers the opportunity to purchase Fitbit trackers at a sizable discount (80%). If I'd left a few weeks earlier, I wouldn't have scored that discount.

The first time they've offered this, I bought a device and gave it to my wife. The Fitbit One is simple to use and it captures a copious amount of performance data. Among the metrics are steps taken, staircase climbs, calories burned and it can even track your sleep patterns. My wife uses it daily to track both her workouts and her daily steps. It provides fun feedback and motivation on its little display.

I decided to try using it because I'll no longer be in an office where I am constantly moving from place to place. My wife pointed out that, even though I'm good about doing my morning workouts, I risk falling into a sedentary lifestyle the rest of the day. I've learned in business that tracking indicators (of things you can control) helps to optimize desirable outcomes. So there you go. I hope to see my new device some time next week.

This morning I went outside for a run for the first time in two weeks. I couldn't believe that was the case until I checked my Garmin Connect logs and saw all the treadmill (and a couple of elliptical) workouts dating back to February 2nd. After checking the weather, I dressed for the cold and made my way outside. I had a slight concern about the residual snow that covered my main escape route, the sidewalks. I figured that if I felt any concern for safety, I'd do a dive into a nearby snowbank.

It turned out to be a very safe run with very few cars. The cars that were on the road maintained a respectful distance and drove slowly. Still I was hyper-vigilant because I don't trust drivers under even the best conditions. I wore a bright orange outer layer on top to maximize my visibility to drivers. I probably could have done with one less layer underneath, but I was fine overall.

My run went well and, despite 14 MPH winds, I managed to beat my average training pace by about 10 seconds per mile. If not for the winds, I may have improved that by another five percent or so. As I ran, I thought about next Saturday when I'll be racing in Long Beach. Last year the temperature was slightly above freezing and there was a mix of sleet and snow falling. I wore my ultra-minimal Hattoris and my toes went numb. But I still ran my fastest 4 mile race that day.

Embrace the hobgoblin

Today's run (street): 2.5 miles

Last Sunday I took a look at my running history on Garmin Connect. This dataset goes back to February '09, when I got my first Forerunner watch, the FR50. Although my modern running history starts a few months before that, the 750 recorded runs represent a statistically significant performance database. I ran a report of all my street runs and discovered that the pace and distances I ran in January 2012 are almost exactly the same as my all-time average.

I was happy to know this because it shows that my pace hasn't degraded in the three-plus years since I returned to running. A deeper look at the numbers confirmed that my paces in early 2009 were similar to today's, so this average isn't merely 1.5 early years of fast running, followed by 1.5 years of slowness.

This morning I had a slow start to my run, owing to my chronic pain above my right heel that may or may not be my Achilles tendon. The burning I feel when I start off tends to go away once I've warmed up a bit. The pain isn't bad. It's just that it's always there at the start.  Due to this, my first mile was slow -- over 10 minutes -- but I picked up the pace and finished with a time only 40 seconds longer than yesterday's.

Today's run and Sunday's performance review both reinforced the fact that, most of the time, I run about the same, regardless of what I think at the time. Ralph Waldo Emerson said, "...consistency is the hobgoblin of little minds." That may be true, but I think consistency, when it comes to running, is a great way to validate your efforts.

Pace perception, pace reality

I think I may have a distorted idea about what constitutes my "normal" running pace. In my mind I consider myself a 9:00 miler but in truth I'm not. Garmin Connect provides reporting tools that allow you to analyze your history and this helps me compare where I am today against previous periods. Sifting through the data and applying the appropriate filters allows me to see what paces I was doing last year on the treadmill, the road, the track and the trails. My overall pace, current or historical, means very little because it's a blend of those running types. Comparing or just reviewing anecdotal data, I see that my normal road pace is about 9:15. There is a margin of error because this data comes from my Garmin which has an over/under tolerance of about 3%, depending on its state of calibration. I often move the footpod from pair to pair depending on the type of running that I'm doing. When calibrate accuracy to .01 mile on my Adrenalines and then move the footpod to my New Balance trail shoes I'll get a different result. It's an inexact method but it's good for measuring trends over time.

Prior to last Sunday's race I had focused primarily on building up my running legs with less concern about pace. In the first two post-race runs this week I kept the speed dialed down in consideration of recovery. Today I decided to start faster and maintain a pace that was on the edge of discomfort. About halfway through I increased the speed a bit more and at the end I expected to see that I'd run the type of pace I do for road races (8:19-8:40). I was surprised to see the Garmin readout say I'd covered my distance at 9:00 per mile. It sure seemed faster than that. It's possible that the Garmin under-counted because of calibration variance and I was on the treadmill and not on the road. Next week we'll have our new treadmill that will provide a readout that I can compare to the Garmin's. It was nice to run my "normal" pace today, despite my delusions of grandeur.

Technical recovery

I have been operating without any personal information management device since Wednesday when my iPhone shut down and refused to come back up. I had been trying to get a satellite fix so I could track a family hike using one of half a dozen GPS apps that I'd downloaded to the phone. The iPhone flat-lined in the middle of that attempt and despite my IT support team's best efforts it would not come back to life. I still have a Verizon feature phone that I've been using when the iPhone can't get a signal (which is much of the time) so at least I am connected. However, without the iPhone I can't reach my business email any time that I wish and, most importantly, I'm unable to use GPS apps to track my runs.

After almost five days without an iPhone or Blackberry I feel pretty good. Funny that when these devices aren't available you can really focus on other things. My wife surely appreciated that I wasn't constantly staring at a 3" screen all week while on vacation. Now that I'm back in my office I have a legitimate need for mobile connectivity and I just found out that IT has resurrected my iPhone. I'm rather shocked since I tried for hours to get it to restart. They still don't know why it failed and they suggested that wiping it clean and starting over might be the best course of action. I'm unwilling to reload all the apps and content I'd put on it so I'm getting it back as is. I hope it doesn't fail again.

I'll use it tomorrow to track my morning run. Yesterday afternoon my daughter and I covered a couple of neighborhood miles which I tracked using my Garmin 50 that I'd calibrated at the track earlier in the day. I had some frustrations over the weekend when the Garmin Connect website coughed and sputtered and refused to upload one of my runs. The run appeared to upload but then disappeared from the site. I was thrilled when I went onto Connect yesterday and saw that the 'technical difficulties' notification had been removed and I was further amazed to see my 5.25 mile Saturday run magically appear in my log. So despite the clumsy way it happened two running technology issues are resolved. Well at least for now.

Letting go of data obsession (a little)

As a coda to yesterday's post I managed to delete this week's run history from my Garmin before I had a chance to upload it to Garmin Connect. I'm disappointed by that but I'm also okay because running has finally become more about the experience than the measurement. A year ago I began to log my activities, first when walking and then when I switched over to running. The act of capturing the data, monitoring improvement and summarizing my monthly mileage became my primary motivation. When my Nike+ Sportband stopped uploading to the Nike+ website I practically panicked because I felt if the run wasn't captured it didn't count. Like it didn't even happen.

I switched from Nike+ to MapMyRun after that and I meticulously transferred information captured on Sportband to this website for a while, until the Nike+ technology failed altogether. Every month I would look at the summary and compare my miles per day/week/month against previous periods. I'd key in my cross training to capture elliptical miles from a paper log I kept next to the machine. I think my focus on the data rather than on the event began to switch when I started running trails more often. Mixing pace times from rugged, hilly runs with flat road runs made monthly pace averages less relevant. I'm still interested in the metrics of each run but I'm satisfied to know that I ran about 20 miles in a week, not that I ran 20.65.

Does this mean that I have transcended the beginner phase of running by focusing metaphorically on the game rather than on the score? Many experienced runners chuckle when I tell them how I capture run data with foot pods and GPS apps. They say they've been doing it so long that they know the distances they run and can pretty much assess their pace as they go. I'm not willing to give up my measurement tools quite yet but I'm willing to live with a few missing sessions on Garmin Connect.

Garmin 50 - illogically lovable

A number of years ago, on vacation in Paris, my wife and I were completely puzzled by the challenge of crossing the street to visit the Arc d'Triomphe. If you're not familiar with its location, the building sits in the middle of a traffic circle off the western end of the Champs-Élysées. It was clear that crossing that traffic would lead to instant death by Renault and yet we saw a number of people milling around the Arc. After some searching we saw a small sign indicating an underground passage that led to the center. It certainly wasn't obvious to us but in retrospect it made perfect sense.

The Garmin 50 reminds me very much of that. Before the Garmin I used the Nike+ Sportband which had less complexity but also less features. It was simple to set up and use, basically it had two buttons that controlled everything and good documentation to show you which ones to push. The Garmin has four buttons that seem to do different things based upon the mode of the watch that can be switched between time, training, interval timing and history. The simple idea of using it as a stopwatch took me almost three weeks to master. The process to do this is simple but the lack of instruction in the manual made it maddeningly difficult. As I use the watch I'm beginning to better understand how the sequence of buttons makes things work. It's still a little annoying when the display says "press OK" when it really means "press the View button" but now, after experimentation, I know to do this.

Of course now that I have gained some comfort with its operation I am thrilled with the data it collects and presents. The combination of pulse rate, speed, cadence, time and distance (accurate to about .03 miles now that I've figured out how to calibrate it) and the Garmin Connect website (that collects and reports the information) are really good. There are dozens of things I'd do differently in terms of functionality and user interface but in the end, it works. However I do wish it calculated pace on the watch, not just speed in MPH.

This morning I ran 4.06 miles at about 9:05/mile which didn't make my target of staying under 9 minutes per mile, but I fully accept it as great progress. It was about 43 degrees when I went out for my run. I only wore a base layer plus a long sleeve technical jersey under a lightweight windbreaker. I was comfortable throughout most of the run but I got very hot near the end. I didn't make either my speed or distance (8 total miles) goals for this weekend but I am very happy with what I've accomplished.

A miss is as good as 3.6 miles

I came within 1% of my goal of running over 3.1 miles at 9:00/mile this morning, completing a 3.57 mile run with an average pace of 9:03. The chart above from Garmin Connect illustrates the technique I used throughout the run where I alternated between my normal pace (~9:20) and a speedier pace. I was pleased to see that the slowest pace that I ran today was 9:28 and the fastest was 8:24. Overall I'm 99% satisfied with the run. The temperature was around 40 degrees when I started but it rose quickly and, coupled with direct sun, I became very hot. I made the mistake of wearing too many layers. This worked great for the first eight minutes but I found it to be a burden over the next 24. At around 2.75 miles I really started feeling taxed which surprised me since I didn't run on Friday and I'd had more than my usual overnight rest. I'll blame the hot weather and the faster pacing. After hitting a wall so soon into the run I am slightly concerned that my conditioning isn't where it should be. But I did recover pretty well and my new focus on speed should help that going forward.

I was also glad to see that my large toe, although still tender, did not cause me any problems during the run. I'm trying to decide on tomorrow's run strategy: 1. Try again to make the "3+ mile, sub 9:00" goal, 2. Aim for a shorter run but make the target pace even faster or 3. Accept today's 99% success and just go for distance on Sunday.

All suggestions welcomed.