SIOR and I hit the Massapequa trail

On July 14, 2019 By Emerging RunnerLeave a comment

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.”

After the treadmill, any outside run is good

On October 23, 2015 By Emerging Runner6 Comments

Short and sweet

Today’s run (street): 3.2 miles
Yesterday’s run (treadmill): 30 minutes

I took a vacation day on Wednesday to take care of some stuff. I had a 7:30 AM appointment so I didn’t get a chance to do a workout in the morning. I did get on the treadmill in the late afternoon and had a very rough 30 minute run. I’m not an afternoon runner and the treadmill didn’t make the situation any better. Although the minutes felt maddeningly slow, somehow I managed through it.

It was great to break up the work week with a day off but Thursday was tough and I was thrilled to work from home today. After that difficult workout on Wednesday, I was concerned that today’s neighborhood run wouldn’t go very well. It was a chilly 43° outside and I wore shorts and a long sleeve running shirt. It took almost five minutes to acquire a GPS signal. I began to rethink my gear as I stood and waited.

As soon the Garmin showed ready, I took off. I didn’t notice a woman who was running by my house and I almost ran into her. Had she been running on the left (correct) side of the road, that would not have happened. I could tell I was in for a good run and pushed harder than usual as I ran up the first long road. I ended up crossing paths with that same woman about a mile later and this time I saw her coming.

I had a tight morning schedule and capped my run at a little more than three miles. That was enough. I ended up doing slightly better than average, probably due more to the cool weather than anything else. The Emerging Runner family will be doing a video call with Adventure Girl on Sunday and I may hit the trails tomorrow in honor of that. While she’s tagging peaks in Montana this weekend, I’ll settle for some of Stillwell’s much smaller hills.

Hot and soggy but not too sloggy

On June 13, 2015 By Emerging Runner2 Comments

Mush!

Today’s run (street): 4.7 miles

The needle on my motivation meter was firmly in the off position this morning. I watched the temperature rise as the minutes ticked by. I couldn’t decide where to run and no option was particularly appealing. I went upstairs to change into running clothes, hoping I’d find some inspiration through that experience. I didn’t want to spend a lot of time on local roads so I headed over to neighborhood #2 for a slight change of scenery.

I’d watched the local weather report before my run and they made a big deal out of the low humidity. LIARS! The temperature was in the low 80’s making the soggy atmosphere feel like hot soup. There were many people packing up their SUVs with beachy gear as I ran by. They had the right idea. I compromised on my pace and floated my way south to the other neighborhood.

I followed an extended loop and stayed on the shady side of the street when possible. My easy pace kept it from being a slog but I regretted waiting so long to go out today. I ended up covering more distance than I’d originally planned and it turned out to be a decent workout.

When I looked at the map of my run, I thought (after rotating the map 90°) that it looked like a person driving a dog sled. I may have created a new category of artwork – design by GPS.

My Garmin lied and the truth hurts

On July 4, 2014 By Emerging Runner2 Comments

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

On April 12, 2014 By Emerging Runner2 Comments

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.

I swear I didn’t run through my neighbor’s houses

On December 8, 2013 By Emerging Runner2 Comments

I love data visualization

Today’s run (street): 4.2 miles

The sky is as white as paper and the temperature is dropping. We’re supposed to get two inches of ice and snow by late afternoon. Nothing so far, but I can tell it’s coming. For that reason, I made sure I got outside early to get in a few recovery miles before conditions got worse.

I had no intention of running as hard as yesterday and had to throttle my speed a couple of times. A recovery run is supposed to be done well under anaerobic threshold to help flush lactic acid from leg muscles. I used my heart rate monitor to guide my pace, averaging 75% of HR max throughout the run. It was a nice relaxing workout, although my (gloved) hands got surprisingly cold.

No actual yards or living rooms were entered

I’ve written a lot about the variability of GPS as a measurement tool and today’s margin of error was particularly egregious. Not only did the Garmin show me starting the run three blocks from my actual beginning point, the accuracy was laughably bad throughout the entire route. The Garmin route map (see above) makes it look like I ran through many people’s yards and houses.

Distribution of pace times through the year

Reflecting back on 2013’s racing season, I charted my race paces to see if there were any obvious patterns. The data doesn’t show any trends that would explain my performance, as times were all over the map. I’m hoping that next year will yield faster times and more consistency. At least I finished the season in a good place.

Lies, damn lies and Garmins

On October 30, 2013 By Emerging RunnerLeave a comment

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.

A good effort but the clock doesn’t lie

On August 25, 2012 By Emerging RunnerLeave a comment

Today’s run (street): 4.3 miles

I had an early appointment that delayed today’s run until mid-morning. The temperature at 10:00 AM was a reasonable 77°, but the sun was making it feel warmer than that. My plan was to go out fast and maintain the speediest pace I could, for as long as I could. I followed a route that would take me up and down the streets that run north of my house, and then head further south to round out the course.

I decided to check my watch at the half mile point to see what the Garmin was displaying for pace. The watch said 8:52, which seemed about right, and I figured that I could maintain that for 40 or 50 minutes. I didn’t feel too overheated and I thought I was in for a run that was close to, or below, 9:00 per mile.

As it turned out, I began slowing down after passing the first mile. By the time I reached three miles, I saw that my pace was 30 seconds off my targeted range. It bothered me that my performance did not match the level of effort that I was putting into the run. After downloading the Garmin and correcting for distance errors (the GPS accuracy has been abysmal this week), I saw that I’d run the first mile in nine minutes, but my pace had crept up into the mid-nine range until improving near the end.

The combination of heat and effort prompted me to cap my run at 40 minutes, for an overall pace of 9:23. I was disappointed with that result because I felt I’d pushed harder than normal. I wanted to break nine minutes, but I don’t think I did all that badly. I’m planning to go longer (and probably slower) tomorrow. It’s okay really. After the past week’s running, I know what I’m capable of doing.

Training slower but racing faster

On November 26, 2011 By Emerging RunnerLeave a comment

Today’s run (street) 3.55 miles

One thing that I’ve learned this year is that the speed I usually run isn’t the same as how fast I can run. This year I’ve observed two things that don’t seem to correlate. First, my average training pace (by observation, not by studying my running logs) has slowed down about 10 seconds per mile. The other observation is that my race paces have improved noticeably in almost every race this year compared to previous years.

I’m not sure what this means but it may have something to do with the quality of my training runs that may be a bit slower, but have more focus. The legendary running coach Jack Daniels said “Every run should have a purpose” and I try to follow that philosophy with my daily workouts. If I need to prepare for a hilly race I try to run hills. If I ran hard the day before, I look to run my next session easy to speed up recovery.

The true explanation for my slower training – faster race pace may be far more simple. Since I started using my Garmin FR210 GPS watch, my mileage is usually under-recorded between 2-5% which makes my pace look slower. When I bother to map my true distance using Gmaps, I see that variance. If I don’t, I tend to accept and believe that I’m running slower than I actually am.

I got out around 8:30 this morning after debating whether I should run or do a core workout and (possibly) an elliptical session later. My legs were tired so I considered the lower impact option. But the weather was cool and the skies were clear so I headed out the door thinking I’d take it easy and not worry about my pace.

The run was easy, in fact I slipped into a few periods where I was so lost in thought that I felt like I was sleep-running. I focused on opening my stride but I didn’t think much about my speed. When I finished my run I was surprised to see that I’d averaged slightly more than 9:00 a mile. That’s not particularly fast, but the pace was about :40 per mile faster than it felt. Perhaps all the racing I’ve done of late has helped in my daily training. That almost 9:00 minute pace was a nice surprise. Sometimes a slow run feels fast, and a fast run feels slow.

Garmin 210 – trouble keeping track on the track

On May 29, 2011 By Emerging RunnerLeave a comment

A shot of the track from this morning

Today’s workout (track): 8 x 400’s plus 3 mile run

Since I’m racing again next Sunday, I wanted to get in a little speed work before I taper my training next week. This morning I headed over to the local high school track to run some intervals. There were a handful of runners and walkers already on the track when I arrived but the lanes were fairly clear. I brought a stopwatch as well as my Garmin and I ended up using the FR 210 to record my runs and used the stopwatch to time my rest periods between intervals.

I didn’t run the intervals hard. My goal was to do mile-equivalents a little faster than my 5K race PR and I managed to average 8:06 across eight quarter miles. I hoped that would recruit enough fast twitch fibers to give me some speed when I ran the following three miles (5K actually) and it did. I averaged 8:45 for that run.

A clear margin of error

The Garmin did not do a good job capturing my route. The picture above is a grab from Google Earth using the imported KMZ file. I stayed primarily in a middle lane but the GPS interpreted that much differently. Even though the 210 is always a little off I still like it a lot. It’s great to be able to run without swapping the foot pod every time I change shoes. Especially in the case of the Hattori’s that don’t even have a place to attach a foot pod.

I’m really happy with today’s workout. While I’m still not speedy, I’ve proven to myself that I can run sub-9:00 paces when I need to. The Hattori’s were interesting to use on the track and they responded well when I took off in a sprint to begin each interval. I haven’t decided what I’ll do for tomorrow’s Memorial Day workout but I am hoping to fold in a bike ride or two before I return to the office.