Option to exclude activity from stats like Vo2Max
-
Not sure where should I put this suggestion here or under Suunto 9 Baro.
A story about the issue: Recently I had an issue with my HRM - I forgot my belt and did a 45 min run on my regular easy pace, however, the wrist HRM tracked my HR averaging around my max HR. In the result, I got 5 point drop for my Vo2Max number just after this one faulty run. I already did some another 7-8 runs after that run (one includes 30-min lactate threshold field test with my new PR on 5km time down by 1.5min), but the Vo2Max still climbing back on very slow pace like 0-1.5 points per run. I also started a bit nasal breathing running, which theoretically could slow down Vo2Max getting back as I have slower pace vs effort, so this could play a role on slower climbing back also. On another note, there also could be a situation that someone can forget to switch off a watch or other technical issue and could impact these type of stats.
Potential solution: Add an option to exclude activity from all stats and recalculate efforts. As we can see, some technical issue can reflect on data for a much longer time.
Many thanks,
Gints. -
Sounds like a watch suggestion, because the VO2MAX is computed by the watch itself. So I’ll move the topic.
Maybe a menu at the end of the activity to ask of you want to exclude the activity just finished from the VO2MAX counting?
Watch: Suunto Vertical Ti
Blog: isazi's home
-
Hi,
The stats need the data and the reality is all the data you have. Let me explain, about the bad data of the HR could be a good idea to exclude, but the vo2max is an estimation and with that bad data maybe temporary wrong. I don’t know the period used to calculate the de Vo2max, but eventually will get right.
About the nose breathing, (good practice
) and the slower pace shows how flaw is this estimation/model. If you do polarized training, with not too much “tempo” run the algorithm of firstbeat tend to understimate your fitness, vo2max… if you do MAF is the same too… This is why I don’t like this estimations on the watch.Tu comunidad Suunto en Telegram: https://t.me/suuntocommunity (spanish)
-
@isazi yes something like this could work. I’m just not 100% sure about user experience if there are too many options after the workout together with ‘delete’ option. Another option would be to review Vo2Max calculation algorithm and make it less sensitive with some AI algorithms which could identify some anomalies and ignore, lower the weight on calculating overall number or waiting for one or two more similar efforts before taking so big adjustments.
-
Hey,
understandably this seems to be a problem. I had this many times when my Belt for example was out of battery.
However, the Vo2max is not a measurement that is affected per se in a cumulative way.
That means that on you next run vo2max will be calculated again correctly.
For example I did a run of 170bpm (due to OHR locking to cadence) and my vo2max fell 5 unitis. On the next run it went back to normal.
But this is a good feature suggestion to be honest. I only wanted to add some info here.
-
@Gints-Grinbergs I’m also not for cluttering the end of an activity
-
@Bulkan I actually do MAF for almost 1.5 years. I’m doing some training yearly periodisation with strick base (MAF) and some 80/20 during build periods. To be fear, at the beginning in November 2019 I did my metabolic + full Vo2Max lab test, literally in the weekend when I updated my Suunto 9 Baro with the new vo2Max feature. And surprisingly within ~2-3 weeks, it got my lab test number mainly doing MAF runs. But starting number was ~3 points under my lab test. And during that time I was at the beginning of my build period with 1 workout per week and the rest of my runs in MAF effort. This is the main reason why actually I opened suggestion on this as I had a pretty good experience with Suunto Vo2Max calculation since it was released and I felt that it’s kind of reflect ups and downs with some makes sense numbers. So, overall I can say only good things about Suunto Vo2Max algorithm. Suunto team did an amazing job here.
-
Also, when you run in 20cm deep snow or on ice, your fitness falls. It would be great to integrate stryd power data into calculating fitness rather than relying on gps data.
-
There should be a manual setting for fitness like in MC. Sometimes you do a
run. -
Work around is to have a 12min vo2 max run On flat road with clear sky view before activity, and hit lap and continue with you regular activity. That way FB algorithm will look for “Best performance” data and will not raise your fitness age like you are a time traveler.
