i doubt it be likely for anyone to have under 100bpm… could this be an easy fix to do?
FWIW, on rides I can get as low as 85bpm (cycling, freewheeling). It’s not planned, but rather just a part of the ride where I’m chilling at the back of the group ride after spending my time on the front.
Wow. I might be 120 with some freewheeling. But as a coach you wouldn’t prescribe that HR for a workout right? Even Pogi’s Z2 HR is likely way more than 100 right?
TDF riders <100bpm at >40kmh
Not structured of course.
Exactly, we are talking planned Garmin workouts based on HR here. I wouldn’t have thought anybody’s Z2 is below 100bpm, even a recovery zone I doubt it. Is this an easy fix @david for this to be implemented into intervals.icu so it reads correctly? Because at the moment I don’t think I am getting the correct load reading because of it?
Zone 1 would be prescribed for a recovery ride, more as a way to ensure the ride is executed as easy as it should be. So that’s about 50-55% of max, which would be 94-103 for me.
Load is not based on the target. Load is calculated from the HR recorded and from your LTHR/HRmax/HRrest, depending on the load calculation method.
It’s only compliance that will be off.
I have deployed a workaround for the Garmin bug. If the high end of a custom HR range would be 80 or less with 100 subtracted and there are no high ends of 250 or more then the values are used as is i.e. 100 is not subtracted. This is only applied if the file manufacturer is Garmin.
Hopefully this doesn’t break any correctly encoded workouts.
amazing, thank you for the quick fix!