Sorry the blog sucks lately, but well… Winter sucks for running. Sure there’s ways around it… there’s some enjoyment in the brisk cold runs… but for the most part it just sucks. And it’s not even really the temperature so much as the short days. I remember getting back from summer runs at 9pm sometimes and there’s still daylight left to burn. Not so now as its getting dark about 5:30ish.
But … things are looking up. Despite snowing the other day and continually frigid temperatures … its going to be 65 today! Even if just for a day I’ll take it. And now, a month after the Solstice – days are getting longer finally. I suppose at the 39th latitude I can’t complain too much anyway – could be worse!
Ok… well enough about the weather. Good news: injury free, been running.
I went out the other day when it was high 30s… actually felt fine for running.
My beloved Garmin 405 had actually completely discharged, and as a result now showed the wrong time. Not important really other than the only way to get the time right is to have it talk to a satellite – easy right? Well I headed out on a short, easy, normal route (3.5 miles) – and completed it pretty easily! I would have liked to go further (I was just getting warmed up – literally) but I was pressed for time.
I was surprised to see however nearing the end of my run that it wasn’t at 3.5 miles because I was used to that route being almost exactly 3.5 miles… which made it nice for comparing runs quite easily.
The difference may have been partly attributed to a firmware upgrade that the Forerunner 405 has had since my last runs from 2.1 to 2.3. Not sure on the exact dates, but my last run (and looks to be all runs actually) prior to Jan 17th was on October 28th. During that run I had firmware 2.1, and this – the most recent run firmware 2.3… ok still with me?
Here’s some changes from 2.1-2.3 that could affect mileage:
- Increased trackpoint resolution when turning or changing speeds.
- Fixed issue where low or zero speed could be recorded at turns.
- Fixed issue where poor GPS reception could cause an incorrect distance in the track log.
- Made adjustments to instantaneous pace filtering
There were a few more, but those look like the relative changes for this concern. Here’s an animated image I made superimposing 4 runs that are the same route. You’ll see they are very similar… with the 3 2.1 firmware runs all 3.5 and the 1 2.3 run 3.4. It will take more runs to get a better feel for it – but I only welcome product updates to increase accuracy!
3.5 Mile Route.
The beginning/end does change a little… but I usually just try to run a little longer or shorter and stop right on 3.5 to account for tiny discrepancies during the run such as dodging traffic or wildlife.
Well this post has rambled long enough. I’ve hit the streets, I’ve hit the treadmill and once again I feel good. I was thinking for a goal… hmmm maybe I can run Hospital Hill in under 1:45? I’ve just made friends with Hospital Hill on facebook too – looks like its going to be a good year for running… I can feel it!
Be the first to like.