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.

Low mo leads to slow go

GPS margin of error

Today's run (street): 3.5 miles

Usually, after a rest day, I'm more than ready to get back outside for a run. Today was one of those near perfect running days with plenty of sun. The temperature was warm enough for shorts yet cool and dry enough to keep sweating to a minimum. Despite all these positive conditions, I found myself unmotivated. My half marathon training schedule only required a 3 mile race-pace run today, yet I was mentally unready to do it.

I didn't sleep well last night, and that probably explained the lack of drive I was feeling this morning. I didn't consider skipping today's workout, but time kept slipping by. We had people coming over in the early afternoon and I needed to get my run completed in time to shower and finish lunch. I decided to dial back the intensity and just do my mileage at whatever speed I could sustain. That got me out the door.

I set a pace that felt sustainable and changed up my route to keep it interesting. While I consciously avoided focusing on speed, I did successfully keep my cadence within my targeted range. I ended up running three minutes longer than I would have if I'd followed the race-pace plan. Although the skies were clear and sunny, my Garmin did a poor job of tracking my progress today (see comparison above). Further, I had no way to gauge my actual performance while I was running, because the readout was based on flawed data.

Tomorrow I'm due to run 8 or nine miles. I may participate in the GLIRC Clubhouse run in the morning if I feel up to it. Otherwise I'll probably head to Bethpage a little later and do it on my own.

Technology saves an operational goof

XML salvation

Today's run (street): 4.25 miles

I did the unthinkable after finishing my run today and failed to properly stop my Garmin. While I happily traced the driveway on my cool down walk, my Garmin continued to count the seconds, obscuring the actual time I'd finished. By the time I discovered my error, at least a couple of minutes had gone by, so my calculated pace was way off.

I really envy people who tell me they run without a watch or track their performance in any way. I think about how liberating it would be to run without regard to time. Unfortunately, I've never been able to do that. On the plus side, I've compiled an online record of every run that I've done over the last five years. Despite my failure to operate my watch today, I was able to reverse engineer my finish time by reading the XML output file.

The run itself was nothing special, 4.25 miles at around 9:30 a mile. The weather was downright chilly, low 50's with strong winds coming from the northeast. When I wasn't heading directly into the wind, it was extremely pleasant. I had considered doing either a long easy run or a short, faster run and I ended up doing something in the middle. I'm not sure what today's run accomplished or what I'll do tomorrow. But Wednesday's run will be the last one I do before Cow Harbor. I hope that one counts.

Running within a palooza

Lacrosse day on fields 1-5

Today's run (track): 4 miles

Today my goal was to increase outdoor running mileage without hurting my recovery from the sore tendons around my hip. That meant another moderately paced workout on a softer surface than pavement. My choices were either to run the trails, or to go to the local high school and run on the track. I chose the track option because I wanted a surface that was harder than dirt, but softer than the road.

When I arrived at the high school, I saw hundreds of parked cars and many more drivers looking to do the same. I almost turned around and drove home, but decided to try a remote lot near the track in case there were any spots. Luckily, I found a space and walked over to the track where I saw hundreds of lacrosse players and their coaches on the field. Adjacent to the main field, baseball games were being held, and lacrosse players from various towns were warming up everywhere.

I saw a single runner and a couple of walkers on the track. I figured that if they were there, it would be okay for me to join them. I set off at a high nine-minute pace, hoping to avoid collisions with parents standing in the track lanes. A few players and lacrosse balls whizzed across the lanes as I went by, but there were no close calls.

As I made my way around, I observed hundreds of players in the surrounding fields and noticed some concession stands that were branded with the NY Lizards logo. That explained the crowds. Apparently today was a Lacrosse-a-palooza, with games and (possibly) a clinic. Later, when I was leaving, I saw many cars parked across the road at Stillwell. After seeing that mess, I was glad I didn't opt for a trail run today.

I think the players would've noticed if I ran across the field

I ran well today. I split my direction halfway, first running counter-clockwise and then reversing after two miles. I suffered no hip pain, although I did begin to sense some tightness by the first mile. I kept my speed moderate except near the end, when I picked it up a step. I couldn't determine my true pace because the Garmin's tracking was way off. I knew this because the watch chirped for its first quarter mile a good thirty meters before I'd lapped it. After looking at the run map (above), I could see that it had also recorded me in places I didn't travel.

I finished my four miles feeling like I could easily go another few. I decided to stop at that point, because I'd achieved my goal of progressive distance. I saw no reason to risk further aggravating my injury. Another run like this will work for me tomorrow, perhaps at Bethpage where I would encounter some hills. I'll give it a few more runs before I restart speed-oriented training. Right now, it feels great to run, both physically and psychologically.