Running Naked

Not that kind of naked...I'm talking about running without my Garmin!  (GASP!!)

After "the" race was over and Dwayne and I were back in the condo...I couldn't sleep.  You'd think after being up about 21 hours by the time we got back and having been swimming, biking and running for about 16.5 of those hours, that sleeping wouldn't have been a problem.  I don't know if it was all the Coke I drank on the marathon course (I am NOT a caffeine drinker)...or the simple fact I had just completed the hardest thing I've ever done in my life...but I just wasn't sleepy.  So I did what pretty much every data-junkie I know would do, I pulled out my Garmin and started looking through my splits!  In hindsight I wish I had downloaded it right then.  Instead I just started going through the data on the watch.

I think that's when IT happened.  The watch sounded a long sustained BEEEEEEP and, after what felt like forever, it showed me the information I wanted.  WHEW, I was afraid that BEEEEEP was a bad thing.  The main thing I wanted to know was what my max speed was, but that appeared to be in kilometers per hour (strange...).  I might have been awake, but I was NOT able to figure out math at that point.  I decided to charge the battery since it had been on for almost the whole time I was, so I put it on the charger, and started reading ("Training and Racing With A Power Meter"...you might think that would put me to sleep, but it's actually a really great book.  No, not in the "popular" sense of the word but in the "everything-you-wanted-to-know-about-training-and-racing-with-power" kind of way!)

Fast forward to the next day when I tried to upload my data...the watch looked like it was connecting and my computer looked like it was receiving data-and then the watch went dead.  I freaked out, turned it back on, found the race data, clicked on "more data" (or whatever it says to show splits)...and --BEEEEEEEEEEP...then data appeared.  Tried to sync and it went dead.  I did this about three times and gave up resolving to call Garmin when I got back home.

Well....long story short...I was not able to download my data, and I'm having to send the watch in to be replaced.  I was able to write down all the information the screens offered for every split of the race (thankfully I had it set to auto-lap every mile)...but 16.5 hours of data, which had to be in the watch because I could look at it, was locked in there.  (sad day)

Now...the sad truth is I have two other GPS watches (a Forerunner 405 and a Timex Global Trainer) but I have decided to run naked until my 910 is returned to me.  I realized I am seriously addicted to data.  I pour over it after workouts, analyze it, evaluate it, base my pleasure with the workout on it, and obsess over it MUCH more than is useful or even healthy.

The first run was very hard.  I kept wondering "how fast am I going?" "I wonder what my heart rate is?" "how many miles have I gone?".  But, the second run was AMAZING, until I was done and thought "that had to be a PR on that course...but I'll never know because I don't have a WATCH on!".  I stopped myself and said, "NO...that run was still AMAZING, no matter what the time was!"  Then...I got in the pool.  Although there is a timer on deck--I can't SEE it with my goggles on.  I had to make myself JUST SWIM without wondering how fast I was going.  I was thankful to run with some gals today who had watches so my thoughts on our pace could be verified.  I have to admit, when I finished up ALL of these workouts, I actually went to hit the stop button on my naked wrist!

It's taking some getting used to, but I think I like running naked.  ...but don't think for one minute this will be a habit I'll keep!!  In fact, the 405 is on the charger as I type.  I have a race tomorrow after all!  :D

Thanks for stopping in, come back soon...I'm working on a slide show of Lake Tahoe photos!  :D

Data

As I promised in the Long Version of my marathon recap, I want to talk more about Garmin data.

First of all...here's my data from the race

Not surprisingly, I spend quite a bit of time thinking about what information I think I'm going to want during a workout/race.  The Garmin is like any other tool, you have to know how to use it properly to get the results you want.  Some people use it simply as data collection, and that's fine, but ideally I like to use it to help me during my workout.

For running I use the Garmin Forerunner 405 ((oh Santa, please bring me the new Forerunner 910XT for Christmas!!)).  It has the ability to give me 3 screens of data with 3 fields each (plus a heart rate screen which I don't actually use anymore because my heart rate monitor doesn't seem to work like it's supposed to, and a virtual partner screen which I turned off for the race).

For the marathon here's what I decided to display and why:

• Screen 1
•  distance-I wanted to see how far I'd gone at any given moment
• time-I wanted to have my "chip time" for certain splits (10K, 1/2, 20 miles and 1 mile to go)
• Screen 2
• PACE (practically useless really since it seems to be off a good bit of the time, but I wanted to have some idea of how fast slow I was going at any given moment
• average pace-much more useful since this is the average pace over the whole distance
• lap time-this would give me an idea how close I was to the end of another mile time wise
• Screen 3
• AVERAGE PACE-I wanted this information on the bigger display even though I had it already on screen 2
• average lap-the average pace in my current lap, important when I set my watch after coming up with Plan B
• lap-how many miles I had already run

(When the screen is divided up into 3 fields, there is one large reading at the top and two smaller ones at the bottom.)  I had the watch set to auto scroll so I didn't have to touch it to switch to a new screen...which is why I had some redundant data (so I didn't have to keep staring at my watch to get the data I wanted at any particular time).

My experience with longer runs and races told me my brain wouldn't function as well toward the end (although I surprisingly did NOT have that problem this time as bad as I usually do-which was a testament to my success on fuel during this race) so I didn't want to have to think a lot about what my data was telling me which is another reason I had the watch display some redundant information.

If I had stuck with Plan B, I would have needed the data the watch displayed more than I ended up needing it with what amounted to Plan D (after mile 15 when I pretty much decided to just run by feel and not my watch).   Here's why....if I had stuck with my plan to start with the slower group for the first 3 miles and then speed up slowly over the next however many miles...I was going to want to know my average pace JUST FOR THE MILE I WAS ON to be able to make sure I was on track to increase SLOWLY and have a set pace for each mile that was slightly faster than the last one.  

For example...If I were going to run the first 3 miles at a 10:00 pace my average pace would be 10, my average lap would be 10 and my pace would be 10 (if it were correct).  If I were then going to run the next 3 miles 5 seconds per mile faster for each one.  My (current) pace/average lap (ideally) would be 9:55 (mile 4), 9:50 (mile 5), then 9:45 (mile 6).  My average pace would decrease with each mile and would (I think) be 9:55 by the end of mile 6.  (I'm not a mathematician and didn't do the calculations, but I think that's right.)  Hopefully you see why it is simply having pace or even  average pace wouldn't help me as much in the moment as average lap.

Now, if you are still reading, I think that means you have some interest in data collection....I want to know your thoughts.  What kind of watch do you use?  How do you use it?  I'm just starting to play around with the workouts feature (where you can set up the exact workout, complete with paces, you want to do and the watch will beep at you like a chirping coach!).  Does anyone out there use that feature?  What do you think?

As always...thanks for stopping in.  Come again soon!
:D