Garmin

2 lurkers | 223 watchers

SPR Sep 2020 1:31pm, 11 Sep 2020 31,271 posts	SPR So looking at my run yesterday, I only had 5 mins above 67% according to Runalyze which shouldn't be enough to trigger a recalculation unless the rules have been relaxed. If I look at the week that I posted above, it's easy to see how the 10 min rule could have triggered a calc on Monday, Friday and Saturday.
SPR Sep 2020 1:35pm, 11 Sep 2020 31,272 posts	SPR This is the page I'm looking at BTW. support.garmin.com
larkim Sep 2020 3:28pm, 11 Sep 2020 11,900 posts	larkim Mine has never shown on the watch, it's only ever shown on a website (the Garmin page until they shut it down, and now RA). The value stored in the fit file for me is definitely an updated value derived from previous runs excluding the one that's just been completed. But that may well differ for newer watches.
larkim Sep 2020 3:31pm, 11 Sep 2020 11,901 posts	larkim Good support page btw. Interesting then that if I do a really effective Z1/Z2 run it won't show up any change in VO2Max. It does point up a flaw in my testing that I did a while back though as I don't think I did any tests where HR / duration would have fitted their criteria, so I would have expected a static VO2Max readout from them.
SPR Sep 2020 3:33pm, 11 Sep 2020 31,275 posts	SPR How are you sure it excludes the run just completed? All you have is a number, not anything that tells you where it comes from? I guess that would make sense if it wasn't being done on the watch for you, but then it wouldn't be on the file if it was done elsewhere.
larkim Sep 2020 3:48pm, 11 Sep 2020 11,902 posts	larkim Just by correlating the runs where it moves significantly, like the one I linked to before. With a high degree of consistency, if a run is marked with an up arrow on RA, the subsequent run shows an improvement in the .fit file VO2Max. If the run is marked with a down arrow on RA the subsequent run reports a fall in VO2Max. I'd have a high degree of certainty that my data proves that with my combination of watch etc.
SPR Sep 2020 5:14pm, 11 Sep 2020 31,276 posts	SPR It would be interesting to ask the question as it's an odd way to do it. Certainly the watches that display it calculate based on the run. I actually got Runalyze because my VO2 Max was behaving oddly on my 230 in the last month before I got the 245 and I'm now wondering whether they updated to calculate pretty much every run instead of what it did previously. It coincided with a period where most of my runs were easy, but previously this wouldn't have affected VO2 Max based on the rules in the support doc.
SPR Sep 2020 5:15pm, 11 Sep 2020 31,277 posts	SPR Re your test, are you saying you didn't do any easy runs as part of your testing?
larkim Sep 2020 10:43pm, 11 Sep 2020 11,904 posts	larkim No I just did short runs I think, not long enough to trigger a calc. I guess I couldn't face doing a decent run without uploading it
larkim Sep 2020 8:52am, 12 Sep 2020 11,905 posts	larkim Just took a look back to two weeks ago where I did three compliant runs without uploading in between, and the reported VO2Max did change between each one, so it is being calced on the watch after all. But that pattern of the reported value being delayed by one activity is definitely still there. Do you have a public RA page SPR?