Inaccurate lactate threshold results continue in 21.19

Beta tester here and lactate threshold detection has been incredibly inaccurate in all betas, including 21.19. This has been a known issue over the last 2-3 betas, so I'm not sure why they would release 21.19 without fixing it. My LTH jumped from 8:33 to 7:33, and then, despite a dismal 14% execution score on another threshold run, it went up further to 7:29. Now each threshold run execution score is 0% without an adjustment back down. What's the use of the beta program if they don't fix known  issues before final release?

  • No matter how much they call it an improvement to LTH, I have only been able to see deteriorations.

  • Hi All,

    with 21.19 LTHR is completely wrong also for me.

    I have 5/6 year of LTHR history created with LT test or hard interval trainings. The values has been always around (167 4' min/km) now during an Trail running activity without the HR band my estimation goes to 182 3'20 min/km completely no sense.

    Probably if you do all your run in a flat ground with the HR band this feature is ok. But in my case with a lot of Trail running and some runs with Optical Heart rate sensor the values detected are completely wrong. 

    Same for Max heart rate.

    The results is that all Garmin metrics are completely broken.

    Please give again the possibility to accept detected values after run, for example if the run is not a good candidate for LTHR detection

  • Garmin, this is ridiculous. Get accept button and test back.

      

  • I am unsure if I fully understand it after looking at the graph. It does look dramatic, but It is all marginal "gains." - a few seconds shaved off the pace?
    -and the heart rate drop at the end (on 9 Dec) is a single heartbeat 

  • The point is that pace improved, while treshold decreased. Makes no sense.

  • I understand, but the incremental data on the graph are all within around 0.3 % (and over 12 weeks). Not even medical lab testing comes close to that, not to mention the accuracy of GPS, etc.

  • 170 to 167 change is actually 1,7% decrease. If change is in the error range, value should stay the same, anything else is just confusing. This is one more example why Accept Button is needed. 

  • I do not see it as an error range—I see it very much within an acceptance range. Thus, these values should be shown so you can act on them. Minor changes over a 12-week training block can hold valuable information.

  • I have the same opinion like RockBastard (like in all those accuracy threads) at the end you have a chep device around youre wrist.

    Cheap is not ment for you as private individual but in terms of medical sensors... The whole watch costs nearly the price of a calibration of a professional sensor.

    This may not mean it's should be tolerated that the supplier can add wrong calculations or bugs etc. but one should at least match the idea of accuracy and measurement uncertainties with reality.

    More over when the watch let you make the choice which result is valid you only get biased to take the "good ones".

  • Either it is

    • a variation due to an error margin / device imprecision - than such a change should not be shown.
    • or- it is an error in the algorithm, because it simply does not make sense that calculated lactate threshold decreases for 3 beats (which is not so trivial), while a the same time pace increases/stay the same.