This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Programming error in Garmin Connect that causes inaccurate HRR calculations when running a HIIT program

Building a HIIT program in GC allows for a warm up, x number of work/rest sessions and a cooldown. This is ok except when doing a HIIT routine and wanting the watch to calculate Heart Rate Recovery.

The problem is that GC allows one to assign a set # of cycles for work/rest and no way to edit this. Why is this a problem? Well, first, if you do x cycles of work the program should assign x-1 cycles of rest. The only reason to have a rest period after a work period is to get ready for the next work period. If there is no 'next' work period there should be no rest period. The problem comes in when doing the workout by delaying the end of the workout for the period of the rest. I use a 90 second rest. Heart rate recovery recovers the most in the first two minutes after stopping the workout. By losing 90% of that critical time any calculated Heart rate recovery is going to be woefully off.
There is no way in GC to change the last rest period so one is stuck with the program running for that 90 seconds. One has lost the most dramatic drop in those first 90 seconds.
When I do a workout and calculate manually the HRR I get something on the order of 45. While the watch, following the program, will calculate 15. HRR is an important data point to track and needs to be accurate. But GC, with it's fixed programming of the # of rest cycles causes this glitch or error in HRR calculations.
The solution is to make the rest periods x-1 of the work periods or to allow a person to edit the length of the last rest period. I would set it to 0 and have the program end right there so it would start calculating HRR. I assume HRR, which shows up under Heart rate under Stats in what gets saved after doing a workout, is used in other calculations like Body Battery or health age, etc.
The easiest and fastest and least expensive fix is to simply get rid of the unnecessary last rest period which can easily be created with a cool down period, if need.
Would really appreciate this being fixed, quickly, as it is so central to the whole process of tracking health.