Elevation Gain and Elevation Hysteresis
Kevin Sharp
When I created a set of video-sync workouts I copied the details of each from the Overview tab in Activities into a spreadsheet so that I can later select a workout based on distance, elevation gain, maximum gradient etc. I noticed that the elevation gain calculated by Golden Cheetah is considerably less than the elevation gain I had previously recorded for the workouts. A bit of digging revealed that this is due to the Elevation Hysteresis. So I duly set the hysteresis to zero in Options/General and was surprised to see that this made no difference. Examining the code I see that if the hysteresis is <= 0.1m then the default value of 3m is used.
I can see why you would want to discourage the use of zero hysteresis with noisy GPS recordings or even barometric elevation, but I'm using heavily smoothed elevation data. I would suggest that the code is removed to test for hysteresis <=0.1, or at the very least Options/General/Elevation Hysteresis does not accept a value <= 0.1m.
Ale Martinez
When I created a set of video-sync workouts I copied the details of each from the Overview tab in Activities into a spreadsheet so that I can later select a workout based on distance, elevation gain, maximum gradient etc. I noticed that the elevation gain calculated by Golden Cheetah is considerably less than the elevation gain I had previously recorded for the workouts. A bit of digging revealed that this is due to the Elevation Hysteresis. So I duly set the hysteresis to zero in Options/General and was surprised to see that this made no difference. Examining the code I see that if the hysteresis is <= 0.1m then the default value of 3m is used.
I can see why you would want to discourage the use of zero hysteresis with noisy GPS recordings or even barometric elevation, but I'm using heavily smoothed elevation data. I would suggest that the code is removed to test for hysteresis <=0.1, or at the very least Options/General/Elevation Hysteresis does not accept a value <= 0.1m.