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

Readiness and Recovery Time History and Constantly Crazy Numbers

I've had my watch months not, perhaps 6 months and every single day my Training Readiness is 80+ hours, my training advice is 'Rest', every single day or so it feels like. 

Is there a way to export the readiness hand recovery time history or to view it so I can see the trend.

I upgraded from a Venu manly for Training Readiness and associated metrics but it has just been a mess, even if I just do a zone 2 ride it still wants 90+ hours recovery time with a readiness of 1. This is for a person doing 15 hours training per week and zone 2 is a recovery day acording to all my other training analysis tool.

I've tried reducing my sleep hours in settings but still hasn't helped, Garmin thinks I should permanently rest do nothing.

  • i turned off all the auto things now and i will see (until now i left all ON but this auto maxHR and the FTP detecions with false heavy underestimations makes me sick) . but i doubt that my maxHR is much higher than 184-185, so there is no 10-15-20bpm higher ...

  • i left all ON but this auto maxHR

    For a long time I left this off because it was suggesting crazy high numbers. What worked/works for me quite well is to use my latest 5k peak HR and add 5bpm. Recently, based on the positive feedback from users here, I turned it back on and it gage me really good estimates (1bpm off). So I could recommend to leave it on unless you are comfortable with "real" maximal efforts and/or you are well trained. As always, you'd have to consistently used a chest strap to get good HR data.

    the FTP detecions with false heavy underestimations makes me sick

    I 100% agree with you here. In my experience, the FTP/Pace (cycling or running) auto-detected is consistently under-estimated, in particular if you do high intensity short interval training. However, if the workout is more like a progressive ramp with intervals of at least 4 to 5mn, the auto-detection works as well as the built-in tests, which are quite good.

  • EPOC is a bogus data in the garmin ecosystem. 

    Training Load is based on EPOC as well, still, it is heavily incentives shorter exercises: if you have a 30 mins exercise, and you record it in 2 sessions (2 pieces of 15 mins sessions) then the sum of Training Load will be much higher in the case of 2x15 mins, versus 30 mins.

    Maybe it does to motivate potatoes who have short sessions, but it makes Training Load is a joke for everyone else - so basically for everyone who thinks that garmin is a serious tool.

    But it is not: it is designed for the masses, who wants to be fit just by buying a watch - if you are really doing exercises, well then, it is not for you.

  • Recovery time is useless. By not logging my high intensity rides I got my recovery time down to 2 hours. Did 5x5 deadlifts with a total training load of 16.... Recovery time up to 28 hours. For someone who's weekly average is around 1.2k training load.

    It doesn't make any sense at all.

  • By not logging my high intensity rides I got my recovery time down to 2 hours

    LOL

    Did 5x5 deadlifts with a total training load of 16.... Recovery time up to 28 hours

    If you do strength training with the WHR you will/may get false high HR spikes. The workout may even be classified as "anaerobic".The impact on recovery will be high and may be over-estimated.

    If you do strength training with a chest strap, the HR data will be correct but the training effect will still be, unfortunately, underestimated because the watch cannot estimate the "true" anaerobic effect. Your recovery needs will be under-estimated.

    For running with GPS and cycling with power however, provided your HR Max and rest HR are correct, and assuming your wear a chest strap for good HR data, your recovery will be based on EPOC which has ~8% error rate.