Trail Zealot

Colorado hiking, Appalachian Trail thru-hiking, and more...

Feb. 1, 2020, 4:14 p.m.

Comments:
Pushed the morning run into the afternoon to avoid the worst of the wind. Wasn't interested in braving a 20 mph steady headwind with even bigger gusts, even though I laid out the run to stay in the wind shadow of the foothills.
Felt good running by feel, but HR was low relative to normal. I'd be huffing and puffing and see a pretty chill number. Decided not to use that data on the run. Something I heard in a podcast this week (On Coaching? Science of Ultra? I forget.): "When a measure becomes a target, it ceases to be a measure." I knew I was running in the right ballpark of intensity based on feel and pace. I decided to ditch all the data and run by feel. I'm glad I made that choice, rather than rejecting my feelings and targeting an "ideal" HR. Even if I were running at a slower pace than usual, I think I'd rather target an exertion level than a pace.
Caught an incredible sunset. Really interesting clouds were parked right overhead (thank you wind storms), and they lit up as I ran home. I couldn't have had a better view. In an uncharacteristic lowering of defenses, I looked at the sky as much as I looked where I was going. That was a great finish to the run. Downhill, running by feel, bright orange wispy clouds overhead. Exhilarating. I wooped as loud as I felt comfortable on the homestretch.
Chose to do one continuous segment with an "average" IF, which is just a downgraded google intensity factor to account for its noisy data. I learned today that the trails in the wonderland area fall into a region of downright wrong elevation data in my high-quality dataset. It's comical. The dataset is so precise and accurate that I can see the footprints of individual houses, but there's a region of absolute garbage data. And guess what, I run there all the time! I'll figure it out. Not gonna change where I run just for the data.