Inaccurate lactate threshold results - "Improved" Lactate Threshold Measurement Feature 19.41

Yes, several users have reported similar issues with inaccuracies in the improve LTHR algorithm. From the few posts across the models, LTHR is now higher than before.

In some cases, users have seen awfully wrong estimates. In my case, I see a 5bpm increase in LTHR. I cannot say it is wrong: my Edge 1030 gave me the same value a couple of years back before I started relying on the Epix.Some users have a lab result that show a large error in the watch estimates.

The detection can happen with easy runs, which is an indication of a significant change in the model and algorithm being used.

Wrt to LT Pace, my new values are consistent with my recent 5K performance (5k pace about 108% of LT pace).

Although the following might not be only related to new threshold models, in my case the pace targets for easy runs are now 30" faster. At the same time, the new targets are more consistent with models from other apps that I use (Stryd, Runna). Similarly, my race predictions are now very accurate for the distances I recenlty run a race for.

I confirm  +10BPM and -20"/k bump in my LTHR since 19.41 update on my epix gen2 + HRM Pro. I don't think it is accurate as it is now at about 95% of my max HR instead of 88% before which seems very high to me. It's concerning as it was consistant for a year and I was relying on LTHR to set my HR zones which are now completely off. I don't know what credit I should put in this new value nor what type of test I should do to get a more realistic value.

Thanks for the input. I'll try different steady paces for 30mn, starting with the new LTHR from Garmin just to check how long I can hold it, worst case I fail, best case I'll hit my PR on 10K...

Yes, it could  be an option, what you suggested, but not easy, I thiink I should try several time before find the right pace to get to the end and to get at the end exhausted as you said. With the old Lactate Threshold Guided Test function was much easier.

I  don't understand why they removed. 

Someone knows if is possible to to something similar with other apps ?

Thanks

Hi Edoardo. Has this improved now with later updates or is it still bad? I bought my Epix Pro In December, and after that watch lactate threshold values became totally wrong, 174 to 183 BPM and pace from 4:39 - 4:12. I turned off the Threshold auto detection and adjusted LTHR back to 174. I looked around for this Lactate Threshold Guided Test, but found out that it was gone And that it measures automatically. I turned on auto detect again, and it measured totally wrong again. This is totally broken for me. My last watch was an Fenix 7X

Yep, i have been in contact with Garmin support explaining this issues, they dont understand what i told them, i finish the conversation saying, that the engineers sais the algortithms is fine, but its not! i cannot rely more on this feature, 1 year ago was spot on! now is a mess, giving values of 10+ bpm more in maxHR and LTHR, i test few times, none of them was near! my last atemp was in a half marathon race, where the watch have enough data to work, but no... its gaves me a maxHR of 185 and LTHR of 167, and my real values are -10bpm in both, 175maxHR and 157LTHR, the real problem is that them dont realize the algorithms is wrong

Same here +10bpm in maxHR and LTHR, so there is something wrong in the algorithms because its repeating more users...maybe its a incompatibily between maxHR and LTHR auto-detect feature

Garmin-Laurie we have been reporting this issue since months, can the engineers take a look in the algorithm of auto-detect feature of maxHR and LTHR, maxHR by alone works fine, but both features enabled together are resulting in +10bpm in the data calculation, so there is something about this number in the algorithm that is causing wrong calculations, thanks in advance.

I cannot speak about LTHR estimate, but max HR automatic adjustment is a joke. 

Six days ago I recorded a max HR of 188 at the end of a long "sprint" on my indoor bike. At the end of the ride the watch suggested max HR of 189, which was actually a reduction from the previous figure, but not entirely unreasonable. 

Yesterday, following another indoor ride, the watch suggested max HR of 184. Well that's preposterous, given an actual max of 188 recorded just four days earlier.

Not only that, but the watch set up a "cycling HR" set of zones for my. I do not use individual sports profiles for HR zones, but the watch added one. You can imagine my confusion when the watch recommended a "base ride" today with lowered HR target. I had already corrected my default max on the watch. I had not realised that I now had cycling specific zones created for me by the watch, with a max of 184.

How f...ing stupid! 

Anyway, no more automatic HR detection for me. It's rubbish.