Latacte Thresold pace from garmin

I'm assuming you mean Half-Marathon in 1:36? If so, then that 7:44 min/mile LT is probably fairly accurate

I'm assuming you mean Half-Marathon in 1:36? If so, then that 7:44 min/mile LT is probably fairly accurate

Yes, it’s a half marathon time. I thought LT pace is the max pace you can hold in 40 to 60 minutes. 7:44 seems to be more inline with my Marathon pace.

I thought LT pace is the max pace you can hold in 40 to 60 minutes. 7:44 seems to be more inline with my Marathon pace.

Scroll down to the LTHR section of this Garmin info page https://www.garmin.com/en-US/runningscience/#vo2-max The LTHR is somewhere betweenn10km and half marathon pace. So the value yo are getting seems about right.

Your lactate threshold is that specific level of effort or pace when fatigue accelerates. For a well-trained runner, this usually occurs when they’re at about 90% of their maximum heart rate corresponding to a pace somewhere between 10K and half-marathon race pace. For a less experienced runner, the lactate threshold is often below 90% of maximum heart rate.

For best accuracy complete a LT test.

TrippyZ The guided LT test may help detecting the LT if the watch fails to detect it during normal run activities, however I doubt the test will give you better accuracy if LT is already detected.

Yesterday I ran a 6 minute max distance test. My HR went from 120 to 180 in 120 seconds, finishing at 185. I got an LT detection of 173bpm. I hit 173bpm after 60 seconds. I don't think these conditions were ideal for a detection.

Completing a proper test would involve steady progressive increase to speed and hr and be ideal conditions for a detection - not a burst from zero to near max in a short time frame.

You might be correct, but I think maybe LTHR and LT Pace are (kind of) two different stories.

From what I understand LTHR is based on changes in HRV, which is detected by measuring very small changes to the electrical signals from your heart. I'm not an expert, but I don't think the speed of HR increase or decrease would affect that too much.

I don't know exactly how LT pace is detected, but I assume it looks at which pace you hit your LTHR, and in that case I agree that the accuracy of the LT Pace detection may be more sensitive to testing conditions. However - I have experienced to get an updated value of my LTHR, without getting a value for LT Pace at the same time, so I guess there are some evaluation of data quality as well in order to exclude false results - i.e. due conditions not fulfilling testing criterias.

I happened to come across this thread today just as I was about to post a similar question.

I just bought a Fenix 5x and ran the lactate threshold test this morning. I warmed up for 12 minutes then began the test. The watch guided me though 3 four-minute bouts of increasing running intensity. Afterward, it alerted to a detected lactate threshold of 88 BPM and 6:54 min/mi.

The heart rate value is obviously erroneous. Has anyone seen something like this? Should I re-run the test or just do a long tempo run and let it auto detect?

That heart rate value does seem very off. Before doing the LTHR guided test, had you already set your correct max and resting HR in the watch settings and completed a few runs to get a stable VO2 Max? The LTHR test relies on all these numbers, so if any one is off or not stable it could well lead to a duff output (like any algorithm; rubbish in equals rubbish out).

I've been running consistently with a Vivoactive 3 since May, so I do have a good VO2 max measurement and resting and max HR in my Garmin profile. I believe physiological true-up moved those values on to this watch after setup.

I did see a temporary HR drop during the warmup period, but I can't imagine that would affect the result. Here's the test.

ciq.forums.garmin.com/.../1424375.png