Training to train

This morning I did a 5 mile neighborhood run, including about 1.25 miles running around neighborhood #2. Considering the length of the run I am happy with my 9:17 overall pace although my target was to average under 9:10/mile and my goal was to stay under 9:00. I guess you could call that a stretch goal. Maybe if I did more stretching I'd have made it.

The Garmin 50 pulled a new trick, about 3 minutes into my run I noticed that while it was happily reporting time, speed, cadence and heart rate the distance stopped incrementing after .08 miles. I couldn't figure that out so my only recourse was to stop the timing and restart. Somehow it took that action as starting a new split but at least the Garmin was recording distance again. I felt really good throughout the run (gee maybe there is something to taking rest days) but in the final minute I experienced a reaction where I suddenly had difficulty breathing. This was hyperventilating and not related to being out of breath from the run. I had a similar experience the last time I ran over 5 miles. I recovered by forcing slow breaths and holding my breath until it re-regulated. I'm sure it's psychological. I just hope it doesn't continue to happen.

The reason I'm training hard this weekend is that I'm participating in a group run next week that's been organized by Adventure Girl to start her team's training for the Ragnar relay race in May. This relay is a 175 mile race from Woodstock to the Bronx with 12 members who each run three legs. I'm not participating in that race but I'm excited about this training run because it will be the first time I've run with people in over a decade. I have to admit I'm a little concerned about carrying a conversation while running but I'll do my best. My other concern is that I'm going directly to the office afterward without a shower. The run, which takes place in Central Park, is only 4K so if I under dress I might be abe to minimize the amount that I sweat.

I'm going to try some trail running tomorrow to take advantage of the weather and to exercise some different muscles.

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.

Quirks of the Garmin

I'm back to the work week routine and despite the residual fatigue that comes from rising at 4:00 AM I've settled back in to my running program. Although I am pleased with the Garmin 50 I've experienced some frustration with its operation, mostly due to its complex interface and its too simple instruction manual.

There are four buttons on the watch that do different things based upon the mode: time, training, intervals, etc. It is not obvious to the user which sequence of buttons need to be pushed to start an action, check a performance metric or calibrate the unit. The manual doesn't cover much of what the watch can do so I'm left frustrated knowing I'm not getting everything I can from the watch. In some cases the frustration comes from inconsistancies with the interface. For example, when in training mode, the usual default screen displays 0000:00:00 meaning "hit start and run." It then records distance, speed, cadence and pulse rate and will display any of those metrics by toggling with one button. That's great except when that display doesn't show up when you switch to training mode.

This morning I got going on the treadmill, brought the speed to my normal starting pace, switched the Garmin to "Train" and was annoyed to see that it did not give me my expected start display. So as I'm running at about a 6.5 mi/hr pace I'm jabbing at the watch in hopes of correcting this so I can record my run. Eventually I noticed a different display that seemed to be capturing distance so I left it alone and in the end it allowed me to save the run. The aggrevating part was that I ran at least .3 miles while this all played out and consequently none of that data was captured.

I'll see exactly what it did capture once the run is uploaded to Garmin Connect. I'm sure I'll eventually learn every aspect of the watch through trial and error but I'm puzzled by the lack of operational documentation. I wonder how many Garmin users give up on the features simply because the thing's so darn complicated.

The 20 minute challenge

The alarm went off at 3:55 AM this morning for the first time in over a week. I was surprised that I had some energy and I decided to run instead of elliptical (which I usually do on Mondays) because I hadn't yet recorded a treadmill run on the Garmin. Actually I had done that on Sunday but my lack of familiarity with the watch controls caused me to delete the run before it could be uploaded to Garmin Connect. That was annoying but it was only a mile so I didn't care. This morning I ran about 2 miles within my tight 20 minute window. Over the last nine days I became a little spoiled with the amount of time I had to run so I felt some stress to get my distance in today. I didn't get a chance to review my average pace or any other workout data because I had to move along but I'll do that tonight after I upload. I'm concerned that Garmin Connect will only accept the most recent run, unlike the Nike Sportband that would accumulate the runs and upload them in batch. That is until it stopped uploading at all.

Despite the short amount of time I had available this morning I'm happy with my run. Tomorrow I'll elliptical at resistance level of 10. So much for looking forward to easy workouts on elliptical days.

Training without straining

Graphic Copyright © 2008 Physical-Fitness-Trainer.com

After yesterday's long run I considered taking the day off from training. It's the last day of our vacation and it made sense to relax a little. I had a headache when I got up (due to a sinus condition) and my wife suggested that we take a walk around the neighborhood as a low impact activity. We set out with my daughter and walked for 40 minutes but, in the end, I still felt tired and my headache was still there. After lunch I decided to do a light workout on the elliptical using only the arms. I have discovered that by setting the resistance to 3 or 4 and standing in front of the unit (facing the back of the display) I can get a very good upper arm workout that's similar to the upper body effort of cross country skiing.

I did the upper arm workout for about ten minutes and then ran an easy mile on the treadmill, mostly to see how the Garmin distance tracking matched up to the treadmill's. After yesterday's long run I bumped up the Garmin's calibration slightly in hopes of reducing the 3% variance from actual distance covered. I was pleased to see that both the Garmin and treadmill were in synch with the Garmin running slightly ahead by a couple of 100ths of a mile. This is similar to what I experienced when comparing the Nike+ Sportband to the treadmill's distance tracking.

Today's walk, elliptical and run activities didn't add up to a highly taxing fitness day but after getting my pulse rate up on the treadmill, followed by a quick shower, I feel pretty good and ready to contend with the start of a new work week.

Nike Sportband - A farewell to armbands

This afternoon I decided to finally end my experiment with the Nike+ Sportband by returning it for a full refund. This was actually Sportband #3, the previous two had displays that failed and the current display just stopped exchanging data. As frustrated as I was with the Sportband I felt a certain loyalty to the device. After all it was with me throughout most of my return to running and it dutifully recorded over 180 runs with useful and accurate information. I had some initial problems with calibration and I called the Nike help line staffed by very engaged people who understood and solved every problem. In the end it came down to a device that didn't meet my needs. The woman who handled my return offered to do it as an exchange saying she knew nothing about the Nike recall and that they were still selling the units. I told her I couldn't continue the insanity and showed her my Garmin 50 saying I've moved on. She rolled her eyes and said "The credit will go to your Visa, have a nice day, next in line!"

So now I'm using the Garmin and I think I've figured out how to calibrate the distance despite a less than clear manual and less engaged support from Garmin. The Sportband was slick and the Garmin is sort of bulky. The Nike+ site has lots of fun features, challenges and community boards. The Garmin site has little of that but the data it presents is much better. The Garmin tells me many things as I run while the Sportband only told me a few. I'll miss the Sportband's simplicity but I won't miss the inevitable failure of its display or functionality. I still like Nike but I'll stick to their non-electronic gear from now on. Hey, after all I just bought my wife a pair of Air Zoom Vomeros.

No field of dreams

Yesterday I decided to try an alternative route starting with a run around the local middle school's field. The ground was still semi frozen and very uncomfortable for running. After about half a mile I peeled off and hit the service road that leads back into the neighborhood. I continued my run on the streets until I came upon the park that connects to the elementary school's grounds. These fields were also very bumpy so I exited back to the street for the remainder of my run.

I had hoped that the additional stiffness of the Kutus would balance the uneven running surface of the athletic fields but it wasn't a comfortable experience and I was concerned about turning an ankle. I was pleased that the Kutus performed well on the street, different from the Turbulence 13s but still good. I ended up covering 2.5 miles at an average pace of 9:09. The Garmin 50 under reported the distance by about 2.8% but I still can't figure out how to correct for that using the calibration feature.

Future trails and Garmin travails

Yesterday afternoon we hit the local outlet stores in search of a few needed items. My goal was to find some trail shoes and I tried on a bunch including the Adidas Kanadias, the Timberland Vaporate and the Nike Assail. Many runners I know eschew Nike and I'm not really sure why that is. I run with Nike Turbulence 13's and I find them to be very comfortable. I didn't really like the fit of the other maker's shoes and I ultimately chose a pair of Nike Tri-D Kutus which fit differently than the Turbs but feel very good. Later today we plan to do some running/hiking and I'll have a chance to test out the Kutus.

I did my first solo run with the Garmin 50 this morning covering 3.26 miles at an average pace of 9:00. It seemed accurate as I ran by my measured benchmarks and I liked how easy it was to toggle between distance and other real time metrics with a push of a button. I'll check the accuracy against Google Earth and adjust accordingly if necessary. I did have another negative experience with the Garmin software when I uploaded the data and it didn't hit the Garmin Connect site or show up on the dashboard. I wasn't upset because the watch retained the data but it seemed odd that the ANT wireless linking app didn't acknowledge the watch at all though I meticulously repeated the the TxPairing process a couple of times. I finally discovered the problem which is that the ANT app uploads the run to your PC but only sends the data if you are already logged into Connect. The work around (which took me a lot longer than it should have to figure out) was to pull the uploaded data from my file system and send it to Connect using the "Manual Upload" feature. Okay, I get it now but Garmin could be a little more clear about what the user should expect.

The good news is once Connect has the data the presentation is excellent. It shows a length of run graph that details pace, heart rate and cadence and even has a play feature that shows this combination of metrics at every stage of the run. I'm going to try to upload this file to MapMyRun a little later.

Back on track, literally

I began this Valentines Day with an early run at the local track. It was the first time I'd run there in over a month and it was a nice change from my other venues. I tried an experiment using both the Nike+ Sportband and the Garmin 50 on my run. I wanted to compare their relative tracking accuracy against a known distance.

It was 28 degrees but it felt colder. There was the usual strong wind for half the loop but I got used to it pretty fast. There were four other runners on the track including a couple I often see running in the morning. I passed the husband, which made me feel great until I was passed by another runner who must have been running about a 7 minute mile. The Garmin and the Sportband remained within a few 100ths of a mile of each other and, ultimately, both under reported the total distance traveled compared to the known distance. I varied my speed throughout the run and ran a total of 4.16 miles at 9:24/mile.

The Garmin vs. Sportband experience had its good and bad components. On the plus side, the 50 was a dream to operate. The HRM appeared to be accurate (yes - finally - a HRM worth a damn!) and it was easy to toggle between pulse rate, speed, cadence, elapsed time and distance as I ran. Finishing the run I simply hit stop instead of fighting with the overly sensitive Sportband button. Saving the run was easy too. Now for the bad part. After a run is captured into history you cannot review the metrics on the watch. The data must first be uploaded to Garmin's Training Center. The badder news is that you can't do this with a Mac even though they're touting new Mac capability on the Garmin website. I fell for it and installed the app and "uploaded" my run. The only problem is that the Mac compatibility only extends to the ANT USB link that allows for data transfer. So the data can be transferred but IT CAN'T GO ANYWHERE. Furthermore, the factory default setting is to delete history from the watch once data is sent so my run went away forever. Happily I also had the whole run recorded by the Sportband.

I installed the Training Center on my XP PC in my guestroom and was able to upload a test "run" to the system. I also switched the transfer program to "DON'T DELETE after sending" so I should be okay for tomorrow, fingers crossed.

Measure twice, cut one

Shortly before I left the office yesterday my wife sent me an email that said "Good News, I think your new watch thingy came today." I got home and was very excited to see that it had, in fact, arrived.

The watch thingy is a Garmin Forerunner 50 with data linking, heart rate monitor and foot pod. Theoretically, this watch has everything I need to capture the metrics from my runs and wirelessly transmit the data to my PC. Compared to my Nike+ Sportband it does quite a lot. That's partially due to the Sportband's tendency to self destruct, usually within two months of receipt. The Sportband's display has become increasingly difficult to read (apparently the design has big problems with corrosion) and it no longer shares well with others. By this I mean that when I try to upload my run data to the Nike+ site it refuses to acknowledge that there is any available data. For that last two weeks I've had to record all my run data manually.

Now that the 50 has arrived I'm anticipating the opportunity to capture my training information in all different ways. The 50 has a stopwatch so, at the very least I can accurately time outdoor running and compare distance from Gmaps for pace. The watch also calculates splits and times intervals. The HRM captures length of workout pulse rate and the foot pod captures speed, pace and distance.

So theoretically I'm set. But what about reality? Experience has shown that running technologies often sound better than they perform. I've had a continuously bad experience with the Sportband but yet I continue to use it because it does one thing very well; capture run distance very accurately. This weekend I plan to perform a faceoff between the Nike+ Sportband and the Garmin 50. I'll wear them both and compare the distance data they report. I'll then compare that data to the benchmark of Google Earth measurement.

One will win and the other will be returned. I really hope the Garmin's capability is more than theoretical.

Beating expectations

It was much warmer today than yesterday so I had no issues with the cold. The wind from the west was strong and the combination of wind plus hills plus 42 degree heat made for a rigorous run. Yesterday I Gmapped my run only to discover that my Sportband was off by 2% and I had actually run almost 4.5 miles, achieving a 9:13 average pace. I Gmapped today's run and saw that it was off by almost 3% of the actual distance. I'm pleased that I exceeded my weekend goal of 8 miles in two runs. I may go to the track later with my daughter who wants to run again. I have not been to the track since discovering it covered by ice and snow but the warmer weather should have cleared that by now.

After discovering that the Sportband was not only refusing to upload any runs to the Nike+ site and was increasingly off calibration I decided to buy a Garmin 50 with HRM and foot pod. The Garmin 50 does not use GPS, the foot pod works in a similar way that the Nike+ system works using RFID. I've had readers tell me that the Garmin 50 works pretty well and I've read similar observations on websites. The reason I didn't get a GPS enabled watch is that the Garmin 305 is just too bulky and the 405 (which is a great running watch) costs $400 including the HRM and foot pod.

So until I get the 50 I'll use the Sportband to record elapsed time and distance and adjust for the Sportband’s inaccuracy. I hope to have the Garmin by next weekend. The only issue with the Garmin is that the software does not work on a Mac so I'll need to use my wife's laptop that runs Vista (ugh) or our upstairs XP machine. No matter, I'm excited about this decision and I will report on my experience soon enough.

Nike+ Sportband, the definition of insanity

Albert Einstein supposedly said "The definition of insanity is doing the same thing over and over again and expecting different results.” If that's true then I am truly insane because I continue to use my Nike+ Sportband hoping that its display, like its two predecessors, won't corrode and fade away. I realize that I have been complaining a lot lately in my posts - runners with bad safety judgment, elliptical machine issues and again the Sportband - but I question why so many fitness technologies just don't work.

I am a technologist and those who know me will agree that I am passionate about the ways technology can benefit society. I say this to demonstrate that I am neither a Luddite nor "purist" when it comes to workout science. However, between my Sportband troubles, continuing problems with our elliptical machine's HRM and an earlier disappointing experience with Brookstone's Heart Rate Ring I am zero for 3 in terms of consumer satisfaction. Why bring a product to market that just doesn't work?

I applaud Nike for having developed a very affordable system that accurately tracks running metrics using an RFID sensor along with a lightweight watch that captures the information in real time. What bothers me is that Nike, an $18 billion company founded on the development of an innovative running shoe, seems to have given up on this idea because their original design was poorly engineered. If the problem is that the water seal of the display is flawed why not fix that and reintroduce the product? While there is an iPod based solution it's an irrelevant choice for those who don't have or want an iPod.


Yet, through this, as my current Sportband continues to degrade and fade, I hold out hope that the next one I get when I swap it out at Dick's will work better. That is if they still have them. Otherwise I will ask for a refund and consider my next technology decision: Should I apply my refund to the purchase of a Garmin Forerunner 50 with Heart Rate Monitor and Foot Pod or go all out and get the Garmin Forerunner 405 Black GPS Enabled Sports Watch/ HRM for three times the price but with everything a running techno-geek would ever want?

It all comes down to my earlier point. What if I bought the 405 and it doesn't work? Then I'll have nothing to aspire to. Maybe that will be the time to buy a stopwatch.

Nike+ Sportband recall

I am currently on my third Nike+ Sportband. My first two became unusable after the display failed. My current Sportband is beginning to corrode the same way. Yesterday I saw an article online that said Nike was doing a voluntary recall of the Sportbands due to display failure. It's really too bad that they introduced a product with such a bad flaw. I rely on the Sportband because it tracks distance whether I run indoors or out. I may end up getting a Garmin Forerunner 405 or Polar RS800 watch with GPS if my Sportband fails again. These are good watches but they are much more expensive than the Nike+ Sportband. Also, unless you invest in the footpod option (on the Garmin) you can only track outdoor runs.