Running dynamics zones zones differ from mobile to desktop

4855060 said:

In the web version vertical oscillation graph is missing.

It is not:

4855060 said:

Vertical ratio for mobile has different zones compared to web version.

My GC Web shows the same ranges as on the app:

Perhaps try reloading the page, or clearing browser's cache

Interestingly, the Epix Gen 2 manual shows 2 different vertical ratio ranges, depending on whether you use a chest strap or RD-Pod (which is positioned at your waist.) The numbers that you show from the app are the same as the chest strap ranges, while the numbers that you show from the website are closer to the waist ranges, but not quite the same.

(I checked the manuals for a couple of other currently supported devices, such as FR955 and Fenix 7, and they all show the same numbers.)

https://www8.garmin.com/manuals/webhelp/GUID-E5C62F3F-DCE3-4197-8CA5-E419B2A55D12/EN-US/GUID-E2728EFE-C7BC-418E-A31D-D44FD12D1A4C.html

I wonder if you used an RD-Pod and if so, whether the website actually showed you the appropriate the help for that sensor. Regardless, if you are seeing different help for the same activity in the app and the website, I'd call that a bug (or an inconsistency). 

EDIT: of course vertical ratio can also come from the watch itself, on the wrist, but there's no ranges for "vertical ratio at wrist" in the manual. Maybe what the Connect website is showing you is supposed to be "vertical ratio at wrist" zones

For me personally, I see the same ranges in the Connect website whether I'm looking at an activity where I wore a Garmin chest strap or not (the ones which start with "<6.1%")

Thank you, yes I was using a RD-Pod actually.. in that case the metrics differ

Thank you, you're right!

4855060 said:

Thank you, yes I was using a RD-Pod actually.. in that case the metrics differ

Oh interesting so I guess the Connect site is deliberately showing you the "waist ranges" (or close to them) because you used an RD-Pod. (I never owned one.)

If you look at the *same* activity in the app, and it shows the "chest ranges" instead I'd say that's an inconsistency. At the end of the day it doesn't really matter but it's kinda interesting.

I didn't know of the different ranges, but it's for sure an inconsistency.. at least. One is right for the device used, one is wrong. So it's more like a bug I would say. At the end of the day data is the same but the interpretation of it is wrong for one of them. Can be confusing 
I hadn't considered the possibility of different ranges for wrist and waist because I assume that both of them should measure the same datum. We can say one is more accurate than the other maybe, but the absolute value is always the vertical oscillation. At the wrist must be interpolated more than at the waist or chest but the outcome should be ideally the same and therefore - because we are measuring in both scenarios how much my body oscillates vertically - the ranges must be the same

4855060 said:

I hadn't considered the possibility of different ranges for wrist and waist because I assume that both of them should measure the same datum.

No, the data from the waist differs slightly from the data from the chest (normally measured by a chest strap, though the wrist RD comes certainly closer to the chest strap data than to the data from a waist located sensor). And it cannot be simply converted from one type to the other, because the difference is individual, depending on the biomechanics of each person. It is explained here: Running Dynamics Pod: Vertical Oscillation and Vertical Ratio Accuracy | Garmin Customer Support

The Running Dynamics Pod (RD Pod) measures vertical motion at the waist, which can be slightly different from the vertical motion at the chest as measured by an advanced heart rate monitor strap. This is the result of biomechanics and the amount of difference in vertical oscillation (VO) and vertical ratio (VR) depends somewhat on the runner. 

Still, I agree that the tables should be the same on the app and on the web. In my case it is indeed always so, but on the other hand I only use either a standalone watch, or the HRM-Pro strap, hence only chest-based data. The question is whether your tables from the app and from the web really come both from the very same activity using the rd-pod. If each of them comes from a different activity (RD Pod on web, and no pod on the app), then the tables are correct, and there is no bug.

If both tables come from the same activity, then I suggest reporting it to the Support, sending them both screenshots and a link to the activity.