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

FR 945 Series: Training effect calculation is wrong

The training effect is Tempo for a pure "blue zone" run. Are you kidding ?! All stats are affected...

  • Buongiorno, a mio modesto modo di vedere le cose devi settare bene le zone 2 zone 3 zona 4 perché 151 battiti corrisponde al 88% del 171 che hai impostato come soglia e di conseguenza ti dà come allenamento di tempo. Spero che sia giusto e ti sia stato di aiuto. Ciao 

  • Do you mean hitting the "green" zone for probably 1-2 seconds within 1,5 hours of running is enough to get a "tempo" status of training?!

    Ridiculous! 

  • appears that that is exactly what it does. I've even had Threshold as a primary benefit where there was not even 2% of zone 3 touched. It's totally broken and very very annoying.

  • Do keep in mind that that Training effect label has nothing to do with your custom setup training zones, it compares your heart rate during run based on maximum and maybe also your vo2max... noticed your zones are def not the default skewing what you and others responding at quick glance might see/say... based on your max effort zone 5 of 171+... (point to a lower max HR of maybe 190? if using 90%+...)... but then other zones are quite high compared.  Did a quick test zone based on 190 max... gives a expected ranges of :

    Zone 1    95-114
    Zone 2    114-133
    Zone 3   133-152
    Zone 4   152-171
    Zone 5    171-190
      
    Your run you skewed zone % even more... by pegging exactly to top of zone2 as a limit, and avg HR was very near that as well.  So really entire run was esentially high zone 3... for a LONG run ....so guessing that it barely got you into Tempo.  
    Mine has been working well in 12.1 firmware, but on my 31k race on saturday got a 5.0 aerobic score and a Tempo result, even though clearly you can't run a "Tempo" workout for 4.7 hours!  but... my HR was high aerobic for a long time!... which 'tempo' is just that!  Now if it said Threshold, that would be a different story!   Your 3.9 aerobic score looks like it was probably appropriate for a 1:45 run at ~75-80%+ of max HR.  (hard to look at just the average and maximum HR values, doesn't often tell the whole story (like if you had a 20-30min low HR warmup and/or cooldown shifting avg down... but then pegged at 149-152 all of the middle time..)
  • Nick, this doesn't make any sense. Results should be based on custom zones (people usually pay significant money for an advanced medical test to get their EXACT zones) - and naturally, it is expected that suggestions will be based on custom (e.g., real, medically tested) zones of a particular individual, instead default settings based on some dump and unprecise common formula.

  • yeah I get that, however the average person doesn't know F about zones or reads some articles and wants to have their zones presented a certain way so their graphs are pretty... but.... Firstbeat/Garmin needs a common program/platform.    Lactate threshold for instance is "typically" a percent of maximum HR... it is NOT however a % of some mythical training zone (which is also different per coach or training plan... *** some don't have the same # of zones!)

  • Do keep in mind that that Training effect label has nothing to do with your custom setup training zones, it compares your heart rate during run based on maximum and maybe also your vo2max...

    That's right! This is one of the things few Garmin users understand. The watch calculates all its metrics off a % of VO2 Max, NOT from the zones the user established. If the user has set up zones (standard or not) that are not aligned with the VO2 Max model the watch establishes, then everything will be skewed: training effect, training load, recovery, VO2 Max, suggestions and predictions, etc.

    instead default settings based on some dump and unprecise common formula.

    In the world of life sciences, a standard error of 5% is excellent. The VO2 Max model average error is 5% (published by Firstbeat). The EPOC model (used for training load, effect, recovery) is around 10-15% (not published in % by Garmin, only in absolute values). So no dumb or unprecise model to be seen here.

    it is expected that suggestions will be based on custom (e.g., real, medically tested) zones

    Nope, it is based on your VO2 Max model and the qualified HR/HRV/Movement/Pace data relationships that fed it.

    If there is a disconnect between your lab or standard zones and your suggestions, predictions, it is most likely because of common user issues highlighted here:

    forums.garmin.com/.../suggested-pace-far-too-high

  • I've contacted Garmin support and got an reply to factory reset the watch ,delete all connections and delete the app and then re-install everything. So I did and when the watch asked to sync data settings I choose not to. I also deleted the running profile before reset.

    So now it has to build up VO2 max and threshold again. I did give in my max HR and Threshold indication of a few months back. Now I state 2 things after 2 runs. My VO2Max is set on 50 like it was before. The runs are logged in the zone that I ran in so I can normally run basic runs again. Also I stated that the watch reacts faster again when I flip through the widgets.

    A bit before I bought a nice watch face called EASY Round but it gave the watch a severe battery drain when using it. That seems fixed now too and battery depletion seems less steep.

    So first experiences after reset are positive. When somethings changes.....I'll post it.