Ever since I’ve gotten my Garmin Forerunner 945 (FR945), I’ve had a minor problem. Minor in that it basically doesn’t affect tracking for any of my training, but that one of the included Garmin Connect metrics doesn’t appear to be working properly (at all, really) because of it.
The FR945 comes with temperature and altimeter readers, which allows Connect to track Heat Acclimation and Altitude Acclimation using tech and code designed in conjunction with a company called Firstbeat.
The heat acclimation function works fine. Las Vegas becomes hell during the summer, and Connect has readily noted my high percentage of heat acclimation after many of my walks and runs in the 100°F+ heat. My calculated heat acclimation only dissipates to zero towards winter as the temperature finally dips and stays below 60°F.
However, the altitude acclimation hasn’t really worked as described. Garmin per their manuals tracks altitude acclimation at as low as 800 meters, 2620′.
The Vegas Valley metro area is a giant bowl surrounded by mountains that varies in altitude between about 1600′ and over 3000′ depending on where in the Valley you are.
I work in Summerlin near the western edge of town, and the altitude at my workplace is about 2720′, above the minimum measured threshold. I train nearby, and most of my running is in a neighborhood that sits between 3050′ and 3200′ in altitude. Any running I do in this area should (per Garmin’s description) count towards altitude acclimation, and most of my running is at this altitude.
I live and train on weekends at a lower 2300-2500′ on another end of town. I don’t expect this to count, but again most of my training by time/mileage/incidences/whatever you want to count is near work at the higher nominally eligible altitude.
However, other than after a long weekend trip to Flagstaff last May, Garmin has never shown I have any altitude acclimation. After the Flagstaff data wore off, my acclimation has always shown up as 0.
According to their documentation, however, all my tracked run training over 2620′ should have triggered an altitude acclimation reading. It’s not happening.
Is something broken? Are there other disqualifying parameters Garmin’s support materials do not spell out? I had no idea.
Continue reading