or for an ad-free Fetcheveryone experience!

Garmin

4 lurkers | 220 watchers
larkim
larkim
Sep 2020
10:30am, 11 Sep 2020
11,890 posts
  •  
  • 0
larkim
Fair enough - if you look back through my Runalyze data you can see the movements with big shifts - e.g. 27th Jan 2020 I ran this fetcheveryone.com/t-17088618 with the nonsense HR data for the first half, wihch caused a drop from 57.1 down to 55.6 instantly.

Since I no longer get that sort of nonsense, the data / progress is cleaner.
SPR
SPR
Sep 2020
10:43am, 11 Sep 2020
31,264 posts
  •  
  • 0
SPR
The Garmin algorithm is supposed to be able to ignore dodgy data, and that looks like a great candidate for being ignored. Of course your watch isn't technically supposed to be doing VO2 Max anymore so there may be an effect there.
larkim
larkim
Sep 2020
10:47am, 11 Sep 2020
11,891 posts
  •  
  • 0
larkim
The thing is, that first section isn't so horrendously "spiked" that it could be valid too. In profile it looks reasonably ordinary, so I can see a "computer" looking at that and thinking it's fine.
SPR
SPR
Sep 2020
11:03am, 11 Sep 2020
31,265 posts
  •  
  • 0
SPR
But the drop in the second half for the same pace shouldn't fool a computer.
SPR
SPR
Sep 2020
11:05am, 11 Sep 2020
31,266 posts
  •  
  • 0
SPR
There could be a debate about which bit is valid but a computer shouldn't think both sections are valid so should probably ignore that specific run TBF it could have been ignored. Just because we can see a raw value against the run, doesn't mean it would have used it in Garmin Connect.
SPR
SPR
Sep 2020
11:09am, 11 Sep 2020
31,267 posts
  •  
  • 0
SPR
Actually, I think I'm wrong there given how my 230 was recording. There's no way each run has the same precise VO2 Max value so when it keeps the same value it must be ignoring that run for measurement purposes?
The_Saint
The_Saint
Sep 2020
11:37am, 11 Sep 2020
6,594 posts
  •  
  • 0
The_Saint
I have chipped in on the Garmin forums about the 245 optical HRM and the latest firmware
forums.garmin.com
larkim
larkim
Sep 2020
12:39pm, 11 Sep 2020
11,892 posts
  •  
  • 0
larkim
@SPR - I'm definitely intrigued by how it operates. In the main I do see small adjustments run by run, my sense is that that value that we see in RA is the output value after the previous activity. So for example on Tuesday I ran a faily bland, but mildy higher HR run (stressful day at work - 8m18 pace, 140 avg), but the figure went up. The previous run was a better one - 7:43pace 142 avg). VO2Max from file went from 55.82 to 56.03 (RA's own calc gave a VO2Max figure of 50.2 and 46.8 to the two runs, which matches my description of them).

That implies to me that the the calc is done post-run either on the watch in the background or on the server. I think it must be on the watch, if I remember correctly, because I experimented with doing a few runs without uploading them and the VO2Max value did actually change between them. I am sceptical about my own conclusion there though because the processing to read back through a HR trace and identify the valid and invalid data feels quite complex compared to the capabilities of my watch - not impossible, but it feels unlikely.
SPR
SPR
Sep 2020
1:11pm, 11 Sep 2020
31,269 posts
  •  
  • 0
SPR
Larkim - It's definitely on the watch. The watch tells you VO2 Max after a run. Obviously yours doesn't do that anymore. The value you see on RA is definitely the value from the current activity as it tracks with what I see on my watch (when it moves enough to change on the watch). Remember the VO2 analysis by Garmin isn't necessarily based on the whole run, in fact in many cases it can't be as needs 10 mins continuously (15 on vivoactive) to measure VO2 Max (at least that's what the Garmin guidance says).

Typical week on the 230



I need to look at the data further TBH though. It could be simply that I'm spending more time above 70% in runs recently hence move frequent changes and that just happens to coincide with getting a new watch.
SPR
SPR
Sep 2020
1:12pm, 11 Sep 2020
31,270 posts
  •  
  • 0
SPR
*Remember the VO2 analysis by Garmin isn't necessarily based on the whole run, in fact in many cases it can't be as it needs 10 mins continuously *ABOVE 70% MAX HR* (15 on vivoactive) to measure VO2 Max (at least that's what the Garmin guidance says).

About This Thread

Maintained by fetcheveryone
For all questions and comments about Garmin devices, including importing to Fetch.

Related Threads

  • garmin
  • gps
  • tech








Back To Top

Tag A User

To tag a user, start typing their name here:
X

Free training & racing tools for runners, cyclists, swimmers & walkers.

Fetcheveryone lets you analyse your training, find races, plot routes, chat in our forum, get advice, play games - and more! Nothing is behind a paywall, and it'll stay that way thanks to our awesome community!
Get Started
Click here to join 113,936 Fetchies!
Already a Fetchie? Sign in here