Showing posts with label GPS. Show all posts
Showing posts with label GPS. Show all posts

Sunday, January 3, 2021

First 2021 run at Bethpage

Sunny and lonely at Bethpage

It's a new year and everyone seems pretty happy about that. There's reason to be optimistic: vaccines will get Covid under control this year and this country will (hopefully) unite under its first real president since January 19, 2017. If 2020 taught us anything, it's that democracy cannot be taken for granted. In the meantime, we can manage through any of life's negatives with a really good run.

My running in 2020 had its ups and downs. I ran a total of 962 miles (a personal record) and 33% more distance than in 2019. I averaged over 80 miles a month and averaged 3.2 miles per run. My overall pace in 2020 improved 5% over 2019. On the other hand, I only had ten runs greater than 4 miles and only one longer than 5. SIOR maintains that my pace isn't going to improve much until I incorporate a lot more long runs into my schedule.

I'm ambivalent about changing up my regular routine since it seems to work for me. My attempt to move the needle on my performance last fall yielded some improvement, but it was more high effort than foundational. There's an argument to be made that longer runs and (shudder) hill training are the best ways to deliver gains. I was thinking about that on Saturday on my way to Bethpage State Park to run with the Runsketeers. We had planned to participate in the annual Hangover Run at Eisenhower Park on New Years day, but it was cancelled due to Covid.

The Runsketeers decided to kick off 2021 at Bethpage, a venue that seems to work for everyone and happens to be close to a Starbucks that has outside seating. Our post-run Starbucks time is as essential as the run itself. Unfortunately SIOR and Professor Mike had medical afflictions and had to cancel that morning and TPP had to work. I went it alone and planned to run at least 4 miles.

Conditions were good, low 40's and sunny. I felt strong and thought I was running pretty well. The paved path at Bethpage has distance markings every tenth of a mile. As I went along, I was puzzled to see that my Garmin was showing less distance compared to the marked path. I thought it was a GPS error. I ended up running 3.8 miles thinking I'd actually covered four. Later, I Gmapped my route using the exact turnaround positions from my Garmin's download. Despite my perceived performance, I ended up running a less impressive pace.

Out 'N Back x 2

I think I've figured out why the north trail markings differ from my GPS tracking. The first tenth of a mile (position .1 mile) that you encounter isn't actually .1 mile from the trail head. It's actually .05 miles. The marker is, surprisingly, the distance from the top of the steep trail that comes up from the lot to the .1 marker on the north trail. It turns out that four times back and forth from the trail head to the one mile mark is - wait for it - 3.8 miles.

Me and the Runsketeer recruits


So lesson learned. I still had a very pleasant run, although I missed my buddies. When I returned to the lot at the end, I encountered four women who were getting ready to head out for their run together. I asked them to take a picture of me that I could send to the Runsketeers and one of the woman asked if I wanted them in it. I said, "Sure, you can be temporary Runsketeers!" I'm sure they had no idea what I was talking about, but I'm used to that.

I did my third run of 2021 this morning before the rain came. It was cold and windy and only about 3.4 miles, but it was nice to know my Garmin is working.

Sunday, July 14, 2019

SIOR and I hit the Massapequa trail

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

Friday, October 23, 2015

After the treadmill, any outside run is good

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.

Saturday, June 13, 2015

Hot and soggy but not too sloggy

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.

Friday, July 4, 2014

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.

Saturday, April 12, 2014

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.

Sunday, December 8, 2013

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

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.

Wednesday, October 30, 2013

Lies, damn lies and Garmins

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.

Saturday, August 25, 2012

A good effort but the clock doesn't lie

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.

Saturday, November 26, 2011

Training slower but racing faster

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.

Sunday, May 29, 2011

Garmin 210 - trouble keeping track on the track

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.

Monday, August 31, 2009

Technical recovery


I have been operating without any personal information management device since Wednesday when my iPhone shut down and refused to come back up. I had been trying to get a satellite fix so I could track a family hike using one of half a dozen GPS apps that I'd downloaded to the phone. The iPhone flat-lined in the middle of that attempt and despite my IT support team's best efforts it would not come back to life. I still have a Verizon feature phone that I've been using when the iPhone can't get a signal (which is much of the time) so at least I am connected. However, without the iPhone I can't reach my business email any time that I wish and, most importantly, I'm unable to use GPS apps to track my runs.

After almost five days without an iPhone or Blackberry I feel pretty good. Funny that when these devices aren't available you can really focus on other things. My wife surely appreciated that I wasn't constantly staring at a 3" screen all week while on vacation. Now that I'm back in my office I have a legitimate need for mobile connectivity and I just found out that IT has resurrected my iPhone. I'm rather shocked since I tried for hours to get it to restart. They still don't know why it failed and they suggested that wiping it clean and starting over might be the best course of action. I'm unwilling to reload all the apps and content I'd put on it so I'm getting it back as is. I hope it doesn't fail again.

I'll use it tomorrow to track my morning run. Yesterday afternoon my daughter and I covered a couple of neighborhood miles which I tracked using my Garmin 50 that I'd calibrated at the track earlier in the day. I had some frustrations over the weekend when the Garmin Connect website coughed and sputtered and refused to upload one of my runs. The run appeared to upload but then disappeared from the site. I was thrilled when I went onto Connect yesterday and saw that the 'technical difficulties' notification had been removed and I was further amazed to see my 5.25 mile Saturday run magically appear in my log. So despite the clumsy way it happened two running technology issues are resolved. Well at least for now.

Monday, August 24, 2009

Et tu iPhone?

What my iPhone looked like when it was alive

My frustrations with the iPhone as a tool for tracking activities using GPS were further aggravated yesterday when I finished my run but could not shut off my tracking app. The process of unlocking the iPhone was difficult enough with the glare of the sun obscuring my view but when I finally got to the application it appeared to have stopped on its own. It turned out that it didn't stop and later, when I went to relaunch the app, I saw that it had continued to run and so any hopes of getting an accurate accounting of my race speed and distance were gone forever. Happily the race used timing chips because my backup, the Garmin 50, was over counting distance by about 5%.

We're on vacation this week and we decided to go for a hike at Cold Spring Harbor. It's a great trail, very rugged with lots of elevation. I turned on my iPhone, switched to AllSport GPS and selected "Hike" but the GPS would not acquire. I pushed the power button on the iPhone and did a soft shut down hoping that after rebooting it would do a better job with GPS. When I hit the power button to restart nothing happened. I tried holding it down for different lengths of time but that resulted in nothing but the same blank screen. No power. We headed home after the hike (which was fun) but I had my mind a little too much on my iPhone problem. I went online to see if this was a known problem (it is) but the remedy they suggested, holding down both the Power and Home buttons, did not restore the unit. I plugged it into wall power, connected it to my iMac, tried to restart in every combination, but nothing is bringing this iPhone back to life.

A call into my company's IT service desk has started an investigation but I don't hold out too much hope that I'll have a working device this week while on vacation. My wife will probably be happy because I tend to check business email two or three hundred times a day (an exaggeration but just barely). If that was my only use I could easily work around it but I've come to depend on my iPhone for so much more now. I'll recalibrate the Garmin for my runs this week and table the GPS apps until this is resolved. We are thinking about looking for trail shoes for my wife a little later today and although I love my NB 460's, yesterday's experience is making me think I also need a new, higher end pair for long runs. While we're out I may take a look at pricing on the Garmin 405's although everything I'm reading about them makes me worry that I won't get much more accuracy than on the iPhone. Maybe I should take a break from technology for a day. It certainly hasn't helped much lately.

Friday, August 21, 2009

Good running apps can be worth the money


I'll give it to the folks at Trimble Outdoors (creator of AllSport GPS) in terms of helping users understand their product. I'd mentioned to them that the accuracy and rest detection with the AllSport GPS app were off the mark and they gave me some good feedback (rest detection can be turned off) and told me that are working to improve some other features. I know it's funny to say this but, even with some of the issues I've encountered, but I'm glad they charge $10 for the app. These utilities are valuable to runners and to other athletes who wish to track their performance. These are applications that should be differentiated from lesser apps that cost far less or are free. Software companies will only invest in optimizing applications if there's a real opportunity to monetize the result. In a world of free or $0.99 iPhone apps there exists great choice but little practical value. I like MotionX a lot, it's priced low for what it offers (but it's not $0.99 either) and it does as good a job as it can with the limits of the iPhone and GPS.

There's a lot more functionality that can be added to these applications to benefit the runner. The accelerometer within the iPhone can be better leveraged to help gauge effort. The GPS can sync with a database of prior runs to provide comparisons to past performance. I have not used Running Gypsy but I noticed it has a feature for automatically capturing 1 mile splits. Why don't they all do that? There are many things I'd like to know when I'm running like temperature, humidity and real time elevation. I have a terrible time reading the display while I'm running due to factors like sun reflections, screen locking and angle of the unit. I'd like to have the option of listening to my metrics in real-time and on demand. As the iPhone and other mobile devices add more capabilities related to user needs and actions it can get very interesting. In the meantime I struggle a bit with the fact that the best apps are still limited by the technologies they need to leverage. I still think about the Garmin GPS watches and wonder why, with the same GPS tracking signal, they would be more accurate than an iPhone.

Wednesday, August 12, 2009

Luddite technologist rant

I am feeling very grumpy about technology today and I felt I needed to do something so I deactivated a Facebook account I'd created some months back. Nothing personal about Facebook, as a technology it's been fine and if I'm ever reincarnated as a 19 year old female, alcoholic, exhibitionist, college student I'll reconsider joining. But like I said, I'm grumpy. I never check the site or contribute to it. At least once a week I received invites from people (many of whom I actually like) but finally decided that accepting them was disingenuous because I'll never check the site. I have an Emerging Runner Fan page that (ironically) I can no longer access. I wonder what will happen with that. Thanks to everyone who fanned it. Sorry to disappoint!

The reason I'm grumpy about technology is that it often doesn't work like it should. I'm not talking about technology that we depend upon daily like elevators and traffic lights, I'm talking about running technologies. Especially those that run on my iPhone. I love my iPhone. It's much more fun than my Blackberry that I gave up with some real misgivings. But when compared to the Blackberry as a business tool it's not very fun at all. Okay, I'll accept that as long as it still does the job. It's annoying to switch from Verizon to AT&T, I liken it to taking a step back in time to the mid 1990's when getting a usable signal on your phone was an unexpected surprise. I've put some GPS apps on the iPhone to help track my running metrics and so far I am not impressed. MotionX GPS, that I paid for ($2.99), has great features (lots of data elements captured: photo utility, interactive maps, iPod integration, etc.) but I'm at about 50% in terms of successful outcome when using it. The other apps I've tried, iMapMyRun and RunKeeper Free, have less capabilities (they're both free) but clever enough. I just bought AllSportsGPS (the company gave me a promo code for a comp version but I managed to screw that up (technology!). I'll see how it works. For $10 I'm expecting a lot.

The performance of these GPS utilities is often undermined by the inherent inaccuracy of public GPS. Despite its potential for getting to an inch of your location it misses greatly and often. If you have to remap on Google Earth every time you use these apps what's the point? I'll try the AllSport app on Friday and see how it performs. So many other running technologies have disappointed. AG tried to use the Qstarz on a 6 mile run recently and it failed to capture any data. What's annoying about that is there's no way to tell with that unit if it's working or not. The original running technology that I used, the Nike+ Sportband, failed so often that I needed to replace it three times before I returned it and bought my Garmin 50.

In truth the Garmin 50 has been a great technology and I won't disparage it although it does consume batteries and each time they are replaced calibration gets out of whack. Running technologies don't all run on batteries either and I'll give due credit to Nike, Adidas and other clothing makers who have perfected the art of sweat wicking technology. But for today I'm just a bit grumpy.

Wednesday, August 5, 2009

iMapMyRun Mobile is free and worth every penny

The great GPS experiment continues with addition of two running apps on my iPhone: iMapMyRun and RunKeeper Free. Both of these apps are free and have fewer capabilities and features than MotionX GPS that cost $1.99. I plan to download a few more of these apps and later do a comparison on Runner's Tech Review. For now I'll talk about my experience with iMapMyRun yesterday and today.
One difficulty I've encountered with MotionX is GPS signal acquistion. This problem is more pronounced in the city than on suburban Long Island but even there it can take a few minutes to get an accurate read. I was able to get a green indicator very quickly with iMapMyRun but that might be related to threshold. iMapMyRun considered the GPS signal viable at an accuracy of 162 ft. where MotionX prefers to get closer before it glows green. Or in the case of MotionX, blue. I went out this morning and selected "Start recording" on the iMapMyRun interface. It was still white when I was ready to start my run but within ten seconds after I left my driveway it turned green. I liked that it had large numbers that showed distance covered along with average and current pace and I thought, hmm, maybe this will work. The darkness helped me see the display as I ran, unlike during the day when the sun reflects off the plastic armband cover. About a mile into my run I looked at the display and everything said 00:00 despite the fact that I'd hit the start button as I left my house. I fumbled with it as I ran and succeeded in getting it working but I knew I'd only recorded half my run at best.

I ended up running 2.25 miles at a 9:06 pace according to my Garmin and the iPhone recorded just 1.1 mile of that. The route map it created showed a similar margin of error to the MotionX routes, again making it look like I cut lots of corners and ran through homes. A Runner's World Loop blogger told me that the Garmin GPS watches are much more accurate than the iPhone location apps. If that's the case I'm back to considering the Garmin 405 because I suspect Run Keeper will perform in a similar way. I did have a little fun with iMapMyRun last night. I set it up to record a run as I drove home from the train station. I covered a little over 2 miles at a 3:15/mile pace. The amazing thing is that many elite runners would have given me a run for my money despite my 300 HP advantage.

Tuesday, August 4, 2009

Motion(X) sickness

I promise that I'll eventually stop complaining about the GPS functionality of the iPhone but this morning's experience made me wonder if the whole concept needs a few more years to develop into a viable technology. I got off to a good start today in terms of timing, I was dressed and ready to make it out the door by 4:00 AM. This was important because that extra ten minutes would give me more time to run and I really wanted to work on distance as I train for my August 23rd race. If I'd ignored the iPhone on my way out I would have been much better off since it added to my setup time and - therefore - took away from my run time. That would have been forgiven if the result was even remotely accurate but the GPS app did not come through. More on that later.

Yesterday, instead of doing my usual elliptical workout, I decided to work on my upper body that I've sorely neglected over the last month. I started with 20 minutes of arms-only elliptical and followed with 15 minutes of free weights. I didn't want to overdo it so I stopped there. I worked up quite a sweat in the process, something I'll attribute in equal parts to hard work and oppressive humidity. Today I was anxious to get back out on the road and after having a carb-rich lunch and small but well balanced dinner I woke up feeling ready. As I mentioned above I started a few minutes early and even with the extra work stuffing the iPhone into the armband I was outside stretching by 4:09 AM. I turned on the MotionX application and was disappointed, but not surprised, to see that the GPS wasn't acquired by the time I was ready to leave. I started off anyway and switched on the app knowing it would start tracking eventually.

I got a little confused along my course because so many of the streets look the same, especially in the pitch dark and saw that I was on a different street than I'd expected. I figured that the MotionX map would show me where I went wrong when I reviewed it post-run. I felt great and could have easily gone on well past my time imposed limit. I ended up covering 2.6 miles at a 9:09 pace. This was good considering that I wasn't really thinking about speed as I ran. The MotionX was completely off with the path showing me running through people's homes and across lawns and through back yards. I thought in the early morning there would be far fewer things that would interfere with the signal. While the Garmin (accurately) showed 2.6 miles traveled, the MotionX showed 2.09 miles. It did show me where I veered off onto a different street so at least it keeps a true, if sloppy, record of my course.

Friday, July 31, 2009

The great experiment

One reason I enjoy running is that the sport allows me to indulge my interest in technology. From my first few months using the Nike+ Sportsband to my switch to the Garmin 50 I have tracked my performance and progress and studied the results. Technology isn't limited to sports watches, I started a site within emergingrunner.com called Runner's Tech Review to provide feedback on every type of fitness technology I use. To be sure, some of this technology is battery powered but much of it isn't. Sports drinks, running shoes and energy bars are all technologies in their own right.

I've just replaced my Blackberry with an iPhone and I'm learning to deal with it. In many ways it's a step down from its replacement but it offers some capabilities to runners that the Blackberry cannot match. For one thing I can finally look at comments posted on my Runner's World Loop blog without being tethered to a PC. I thought I would have better tools for mobile posting using Safari but Blogger doesn't really work right. There may be issues with Flash or Java. I can post simply by sending an email to a special address so I've found a good solution for that. The big exciting technology opportunity is leveraging the GPS capability of the iPhone. I mentioned MotionX yesterday and put it to the test walking a few places in the city. The system had a difficult time acquiring a signal but that could be related to the many tall buildings in mid town NYC. Today I will try a run with the iPhone using MotionX to track my speed, distance, elevation and route. I'm hoping that it works better than the Qstarz Sports Recorder.

To hedge my bets, I'll have my trusty Garmin as backup and it will be interesting to compare results between the two. The only concern I have is the weather. Storms are expected and I don't want to soak the iPhone.

Saturday, December 20, 2008

Nike+ without the Nike part?


I saw this interesting post on MIT's Gizmodo technology blog. The Gizmodo article states that:
"Apple wants to take Nike+ to a different new level to perform precise, real-time tracking of runners' performance and offer location-based information and advertising. Their latest patent not only details how they will get rid of the current RFID sensor and add a series of force sensors instead—as well as GPS support—but also how they are contemplating other "authorized" shoes. Does this mean they are abandoning their relationship with Nike?"
Interesting idea to put the entire sensing system into the shoe itself. With all that plus GPS I imagine it would be a very expensive pair of shoes. Given that most established runners replace their shoes after about 350 miles I'd hope that the electronics can be detached and moved to another shoe. The article also says that the GPS will be able to serve location based advertisments to the runner through an iPod so maybe consumers can get a break on the price if they agree to accept ads.
 

blogger templates | Webtalks