I should add that on the 2nd lap I did 2 reps on the climb at max effort hence the increased HR plot. On the first lap I did the climb once at normal pace, hence the HR plot doesn't look as it does for the 2nd lap.
website not handling elevation corrections at all in any browser. click either available button, nothing happens. I suspect it is as simple as no submit being issued when elevation correction button is clicked.
the button for enabling the corrections (which was/should be default) is now not working, leaving me with funky elevation data from my watch instead of the corrected data. At no point in my run was I 20 feet under sea level and I also did not climb over 400 feet on a flat 13 mile run...........
2/19 run right before Garmin Express update, it was enabled. Then on 2/20 after installing Express, run in the same area, the elevation is disabled, http://connect.garmin.com/activity/448528478, started at 300 ft, my area is all flat at ~160ft above sea level. Then for some reason the next run on 2/22, the elevation is enabled again, http://connect.garmin.com/activity/449646166
And I can not use the Enable/Disable button to change any of the runs in Dashboard.
There are a couple of threads discussing the elevation corrections issue. The Elevations Corrections says Enabled, but it isn't always, and clicking on the buttons can toggle you between Enabled and Disabled, even though the button display doesn't change.
I know for sure this one run I have (http://connect.garmin.com/activity/448528478), clicking the Enabe/Disable button doesn't change a thing. And I'm not just talking about which of the Enable/Disable text is highlighted. The elevation profile always starts at 300ft, even though I was on flat ground around 160 ft the whole time. So whatever is fixed for other people is not working for me.
