Jason McGhee
Statistics
Run (Intermediate)
Triathlon (Beginner)
Adventure Race (Beginner)

Jason McGhee

Dallas, TX
Taken, Male, 35 years old

About Jason McGhee

I took up running in the fall of 2006 to enforce my decision to stop smoking. I ran my first half marathon, White Rock, in December of 2006 - it hurt. I ran my first full marathon, Berlin, in September of 2007 - it hurt more. I have since run 10 more full marathons (last was the Cowtown in February 2009) and many half marathons.

I got involved with the DRC shortly after I started running and directed the 2007 and 2008 DRC The Loop 15K/5K races. I am now the DRC Race Management Director for 2009-2010 and enjoy working with everyone to put on the DRC's great and rapidly growing monthly races.

Sign in to post a comment

View Comment Wall

Recent Activity

Run

Run

Jason McGhee ran 8.23 mi in 1h 11m 27s
Run

Run

Jason McGhee ran 4.14 mi in 34m 20s
Nelson Prater
Jason - Chris's group runs!  =)
Run

Run

Jason McGhee ran 14.85 mi in 2h 29m 53s
  Jason McGhee and jonathan annis are now friends.
Swim

Swim

Jason McGhee swam for 45m
Jason McGhee wrote
Jason McGhee
Hey Michelle, it was so dark last night I could hardly see my feet, but I thought that was you.

The Austin half went better than expected. I was just a couple minutes off my PR despite little training and a very difficult final 3 miles. I felt like I needed a sherpa on one of the hills.
Michele Lindsey
Hey Jason.  That was me that yelled hello last night right before the Bath House!!  How did your run go in Austin?
Run

Run

Jason McGhee ran 6.22 mi in 50m 41s
Swim

Swim

Jason McGhee swam for 30m
Run

Run

Jason McGhee ran 3.98 mi in 31m 57s
Run

Austin Half Marathon

Jason McGhee ran 13.13 mi in 1h 47m 10s "Not quite a PR, but better than expected."
Jason McGhee wrote
Jason McGhee
This is a good explanation of how courses are measured and why your Garmin won't match the race distance from Ken Ashby, who measures and marks all of our races:

As a course measurer, I am often asked about the distance. If done by USAT&F certification procedure (http://www.usatf.org/events/courses/certification/manual/), it is highly accurate. Two wheeled measurements must agree within 0.08%. The wheel calibration is checked before and after on a steel-taped calibration course, and lengthened by 0.1% to insure records are valid. Running on the outside lanes of curves might add another 0.1%. It turns out that present-day GPS technology is not nearly this accurate.

The DRC 15 km (9.32 mile) race course was measured exactly, run correctly, and timed precisely. Your Garmin Forerunner measured a distance of 9.45 miles, which accounts for the 7 sec/mile discrepancy. That is an error of almost 1.5%, which is typical over a 9-10 mile distance (shorter distances vary more).

Garmin customers, myself included, are disappointed to learn about this. Retailers often claim the watches are "very accurate," which means typically within 5%. Here is what the Forerunner 205/305 manual (http://www8.garmin.com/manuals/984_OwnersManual.pdf) says in Product Specifications (page 64):

<  Update Rate: 1/second, continuous
<  GPS Position Accuracy*: < 10m 50%, typical
<  GPS Velocity Accuracy*: < 0.05 m/s
< * Accuracy depends upon view of the sky.
<  99%-clear view; 95%-typical.

In other words, it measures within +/-1% under ideal "clear view" conditions (no trees, buildings or hills on the horizon), but more typically within +/-5%. Note that your 1.5% error is equal to the ideal maximum velocity error of 0.05 m/s at an 8:00-per-mile pace (0.05m/s X 480s/mile X mile/1600m = 1.5%). Also, the Product Warranty (page 71) states, "This product is intended to be used only as a travel aid and must not be used for any purpose requiring precise measurement of direction, distance, location or topography."

An anecdote: My wife purchased us identical Forerunner 201's in 2004. We noticed the measurements would vary greatly from day to day on the same course. One day, as an experiment, I wore both watches side-by-side on the same arm. Throughout my run, the displayed distances and paces were different!

Bottom line: Present-generation GPS signals are too weak to be reliably triangulated by a wrist-sized device in motion under typical conditions. High-accuracy position measurement requires the device be stationary and average many samples over time. High-accuracy instantaneous velocity measurement requires the device move fast enough (auto, plane, fast bicycle) that the position errors are relatively insignificant. You can expect distance and average velocity to measure within +/-1% only under the very best of conditions.

LK Pierotti wrote
LK Pierotti
I did. I parked to run with the couch group at 7a and it wasn't bad - I got my usual spot in the first lot. Then when I came back around 945-10a or so, it still wasn't terrible. Hope that helps.
Run

White Rock Lake loop

Jason McGhee ran 9.41 mi in 1h 17m 42s "Surprised that I felt so good tonight."
Run

Easy

Jason McGhee ran 3.11 mi in 25m 53s
Other

Recumbent bike machine

Jason McGhee logged a Other activity "Just a little time to keep loose"
Swim

Swim

Jason McGhee swam for 30m
Run

Base run

Jason McGhee ran 7.06 mi in 59m 50s
  Jason McGhee and Valerie Sewall are now friends.
Training

Jason McGhee has not logged any workouts in the past 7 days