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

Lactate threshold interpretation

Hello guys. I bought my Fenix 3 one month ago and made the garmin connect account the same day. First of all, I like a lot the way garmin connect let's you customize the fields. I've added the ones I'm interested in and checking them every day. Under reports, I've also added Lactate Threshold. While for the past month, the VO2max went from 51 to 52 and now to 53, the lactate threshold graph shows 2 lines, one for the HR and one for the pace. Reading the literature, I find the lactate threshold measured as mmol/l and would like to know how to interpret the 2 lines. The HR line started at 165bpm and went to 164 and now 163. The pace line went from 4:21 to 4:20 and now 4:19 . I suppose both mean an improvement ? How to relate these to lines to the international measuring unit ? Thanks !
  • Hey.

    Improvement on the pace, but not on the heart rate.

    Is estimates you can hold a faster pace and not run over your lactate threshold.

    As for heart rate it estimates you need to run with a lower heart rate in order to not run over your lactate threshold.

    I would presume over time that the pace will continue to decrease, but the heart rate should increase.

    But all in all your running economy must have increased.
  • Thanks. Don't know how accurate the pace is as Fenix 3 is reading lower distances which means worse pace. For example for a 6km run on my Iphone 6 + Strava (checked by me at home on the map editor), Fenix 3 is reading about 5.85km which generally means a pace about 8-10sec/km lower than real. As for the pace, I do run at a lower pace this time of the year because it's cold here and I wear a mask on my face which restricts airflow a little bit. During spring/fall, when temps are much better, I can keep a pace of 4:00min/km for 5kms with a slight increase of my bpm which means I'm a bit over my threshold. Probably a 4:10min/km would be realistic as threshold now !

    PS : I'm correcting the distance in Garmin Connect but is there any way to send this new value of the distance to the watch also ?
  • Don't use Iphone + Strava. Connect GarminConnect directly to your Strava?

    I normally allways wear my 920XT, so I will allways use it on my runs. And it transfers everything directly to Strava.

    I would guess that the Iphone has much worse distance calculation then your Fenix 3.

    https://support.strava.com/hc/en-us/articles/216918057-Uploading-from-a-Garmin-device-#automatic

    I use my phone to upload the activites, so I have connected the Strava app and the Garmin app together.

    Works great!
  • Back when I used a MAP60 on my bike along with a wheel based bike computer they would always be within a 0.1 miles.

    But when I would upload the file from the MAP60 to Strava it would always come up a 0.3-0.6 miles different. If you read through the Strava forums and information pages you will see where they indicate that they do their own millage calculation.
  • Don't use Iphone + Strava. Connect GarminConnect directly to your Strava?

    I normally allways wear my 920XT, so I will allways use it on my runs. And it transfers everything directly to Strava.

    I would guess that the Iphone has much worse distance calculation then your Fenix 3.

    https://support.strava.com/hc/en-us/articles/216918057-Uploading-from-a-Garmin-device-#automatic

    I use my phone to upload the activites, so I have connected the Strava app and the Garmin app together.

    Works great!


    No, it's exactly the opposite. My Iphone 6 is spot on with gps accuracy while the Fenix 3 always reads a lower distance. At a 10K training which was verified by my on a sattelite map with the course created by myself, the Iphone 6 showed exactly the same distance as what I've created, while the Fenix 3 said 9.77K which is 230m lower and a much worse pace !
  • Former Member
    0 Former Member over 8 years ago
    LTHR - the effort u can sustain for 45-60mins in terms of heart rate.

    HR on its own as a metric is ill advised since u dont win races for having the best HR.

    Which is why its complimented with pace.
    U may get a better pace and a lower HR over time which shows ur heart is getting more fit capavle of sustaining a faster pace using less beats.
    Both dropping however shows u are putting in less effort during ur LTHR tests or ur HR based training is being performed incorrectly somehow (since hr training is supposed to increase ur pace - all training for is)
    HR rising and pace rising - who cares ur going faster (but really ur heart is getting fitter too)

    Disable the automatic calculation since there are plenty of training activities that will muddy the waters giving eroneous results....

    Eg
    Intervals with rest periods where your hr doesnt completely return to zone 2 and u are stopped to catch ur breath or thereabouts.
    These really really mess with ur pace and lthr on a garmin watch, even if u manage a jog during the rest stage.
  • No, it's exactly the opposite. My Iphone 6 is spot on with gps accuracy while the Fenix 3 always reads a lower distance. At a 10K training which was verified by my on a sattelite map with the course created by myself, the Iphone 6 showed exactly the same distance as what I've created, while the Fenix 3 said 9.77K which is 230m lower and a much worse pace !


    The only way to verify the actual distance is to use a measuring wheel. Creating a course on a map online is no indication of accuracy. The fact that your iPhone agrees is no indication of the GPS accuracy of the iPhone, rather it's indicative of the post-processing used to map the iPhone GPS to the map.
  • Ok, what about running laps on a 400m track (inside lane) then ? The phone also agrees with the real distance while the watch shows lower values for the distance !