Is the VO2 max takes elevation into account? How is it calculated? Thanks? If I'm the guy who does a lot of hiking, will it affects my VO2 max calculation if elevation is not takes into the account?
That is the tricky part, does F5 actually takes elevation changes into account while calculating the VO2 Max? Because I cannot find any official answer for that yet.
1. Vo2Max isn't calculated in the "Hike" app (or trail run for that matter) 2. My runs start at 5423 feet regularly. I did however run in Houston TX at sea level in the spring. While running at sea level was awesome, I didn't suddenly get a huge bump in Vo2 max. I received an increase, but it was no different than the increase that i usually get on a fast interval day (which tends to revert on a slow recovery day). The Vo2max calculation seems to have issues with detecting that my running economy sucks at recovery paces. Or i just suck at recovery paces... 3. I ran (using the run app) at 8500 feet this weekend on an out and back up a fairly long hill. My Vo2max didn't go down when looking at performance condition up the hill, nor really up at much faster paces while at lower HR coming back down. Basically it stayed the same.
So my thinking is 1. uphill/downhill are taken into account (elevation gain/loss) to an extent since my performance condition didn't change drastically going uphill or downhill this weekend. 2. absolute elevation must be taken into account or i would have seen vastly different numbers between sea level and 8500 feet 3. surface quality is not taken into account. I've seen drops from running soft sandy trails in the "run" app.
1. Vo2Max isn't calculated in the "Hike" app (or trail run for that matter) 2. My runs start at 5423 feet regularly. I did however run in Houston TX at sea level in the spring. While running at sea level was awesome, I didn't suddenly get a huge bump in Vo2 max. I received an increase, but it was no different than the increase that i usually get on a fast interval day (which tends to revert on a slow recovery day). The Vo2max calculation seems to have issues with detecting that my running economy sucks at recovery paces. Or i just suck at recovery paces... 3. I ran (using the run app) at 8500 feet this weekend on an out and back up a fairly long hill. My Vo2max didn't go down when looking at performance condition up the hill, nor really up at much faster paces while at lower HR coming back down. Basically it stayed the same.
So my thinking is 1. uphill/downhill are taken into account (elevation gain/loss) to an extent since my performance condition didn't change drastically going uphill or downhill this weekend. 2. absolute elevation must be taken into account or i would have seen vastly different numbers between sea level and 8500 feet 3. surface quality is not taken into account. I've seen drops from running soft sandy trails in the "run" app.
That is the tricky part, does F5 actually takes elevation changes into account while calculating the VO2 Max? Because I cannot find any official answer for that yet.
In running mode, it does. In hiking mode, VO2max isn't calculated.
Is elevation change taken into account by filtering out the parts where there is elevation change? Or is elevation change taken into account by actually calculating the resulting change in running effort when running on a slope?
In running mode, it does. In hiking mode, VO2max isn't calculated.
Then I believe it is a very poor implementation.
In evaluating VO2 max algoritm I look at the performance condition as an indicator on how the Vo2 would be calculated that is more fine-grained than only Vo2. But as a summary I belive they are very consistent.
When talking increasing/decreasing in next chapter i refer to the "me current level"
- Short steep uphill will lower performance condition heavily. (This is very significant) - Running tight trails without footpod with bad GPS data will lower performance will reduce heavily. (Since the GPS will cut corners and thus believe the speed is a lot less) - Interval training with fartlek, which involves parts with somewhat lower speed after a tough part reduces the performance condition. - Interval training with parts that are standing absolutely still is increasing performance condition. Since some parts after the rest the heart is without stress and still fast running. - Running without a foot pod increases the performance condition due to parts with too high speed from GPS without heart impact.
This is my conclusion after testing since day 1 it appeared on fenix 3.
Is elevation change taken into account by filtering out the parts where there is elevation change? Or is elevation change taken into account by actually calculating the resulting change in running effort when running on a slope?
Certainly the former. I doubt the later (although, I'm not 1000% sure). It would probably need to be a quite long (several minutes at least) climb at the same grade for it to even make sense to attempt such a calculation. As others have pointed out multiple times on this forum, there is some natural lag between changes in intensity and when your body, heart, lungs, etc catches up to actually represents the real effort aerobically.
