Garmin

7 lurkers | 224 watchers

Badger Sep 2020 11:25pm, 21 Sep 2020 12,807 posts	Badger For a random file I pulled off my account from last week, 140 and 79 give different values. 79 is the value I see against that activity in Runalyze, 140 the value I see against the next activity in Runalyze. Which hints that one of them is the value at activity start, the other the value at activity finish, which matches up with what larkim was saying about reckoning the number was from the previous, not current, activity. More complicated than that. The numbers are not the same in any file I've looked at. If 140 has a non-zero value, that's what you see. If not, you see the value from 79. 79 is the same for four activities in a row, Run, Trail Run, Cycle and Run - which I can't quite get my head around, unless the first run was too short to alter whatever that number actually means (I can see the trail run and cycle (no power) not changing it. The position in the file does imply that 79 is calculated at the start & 140 at the end.
SPR Sep 2020 11:47pm, 21 Sep 2020 31,569 posts	SPR Trail running doesn't contribute to VO2 Max trend, although having used it to test that specifically on Friday, it does seem to calculate (RA showed a new value by file) but my next run on Saturday, which was easy, used the value from the last run mode. Cycling either has it's own VO2 Max or doesn't contribute to the VO2 Max which is specific to running as I understand it. Are there different fields for cycling? The run can be long but my testing indicates you need 4 mins above 70% for a new calc (not sure how that shows on the file (blank in 140 presumably)?
flanker Sep 2020 1:35am, 22 Sep 2020 19,426 posts	flanker 140/7 is spot on for my file value. I've got a month of the file value not changing for any event - these are all trail run or walk. This might also explain why the watch reports "no status" for training status - maybe that needs to be a "run" activity specifically, rather than one of if offspring. Badger - my SDK version is 21.38, from a week ago.
SPR Sep 2020 8:14am, 22 Sep 2020 31,572 posts	SPR Walking does contribute according to Garmin but has the same 70% HR max rules. Presumably that means the 4 mins I've tested for running rather than the documented 10 mins but would need testing.
SPR Sep 2020 8:16am, 22 Sep 2020 31,573 posts	SPR And yes it explains no training status as it's all based on what's happening with your VO2 Max and for you, there's no data that is valid for a month. I presume it still has training load though?
larkim Sep 2020 8:17am, 22 Sep 2020 12,032 posts	larkim At least we know fairly definitively where to find the data now, so there's potential for Fetch to scrape that data into our training entries. It feels like recalculating a value is an inherent part of the post-activity (or mid-activity) code running on all (or at least most) Garmins which makes it all the more galling that they enable / disable it on specific watches so that it can be a "feature" on some only. But that's the commercial market place I suppose.
Badger Sep 2020 8:21am, 22 Sep 2020 12,808 posts	Badger There was a hint from Garmin a while back they were working on VO2max for trail runs, and as I recall VO2max values started showing up in trail runs in Runalyze about then. Maybe we’re part of an experiment for now. So flanker, you’re seeing values in 140/7 for trail runs? The trail run I looked at had zero in that field.
SPR Sep 2020 8:27am, 22 Sep 2020 31,574 posts	SPR That's interesting Badger, not sure how they'd do it. How do they account for the terrain slowing you down? My VO2 Max on the 'trail' run (it was actually a short commute run on pavement) went up slightly up which surprised me as expected a drop on tired legs (it was short though and may HR didn't have a chance to catch up with speed or dodgy data)
SPR Sep 2020 8:59am, 22 Sep 2020 31,575 posts	SPR Just checked that 'trail' run. Beats per mile was 1260. When fresh, I'd be mid to low 11xx, so that type of run shouldn't increase VO2 max (only by 0.12 but it should have been going down). I also had a bag on as it was after race. That makes me feel like the trail experiment is trying to account for difficulty somehow. In my race warm down, my beats per mile was 1218 and it knocked 0.3 off my VO2 Max.
larkim Sep 2020 9:17am, 22 Sep 2020 12,035 posts	larkim In the fit4ruby code there seemed to be fields that were tagged as being vo2max for running specifically, so it would make sense if there were equivalent fields for cycling etc too.