Suunto ZoneSense

[halajos]

@marcrie I only use customized support modes and ZoneSense works with them. But if multiple S+ are selected, then the ZoneSense app may not work properly.

[Antoine]

question which is not directly linked to Suunto ZoneSense:
does anyone know if using the heart rate belt and the Suunto+ Suunto ZoneSense application reduce the autonomy of the Suunto vertical significantly ?
(I want to use it for a long trail)

[halajos]

@Antoine I don’t think it has any significant effect. Regarding belt vs. wrist based HR, I think the latter may need more power than the former. Whether the computation required by ZoneSense is significant, I don’t know, but I doubt it needs significant excess power.

[Brad_Olwin]

@Antoine said in Suunto ZoneSense:

question which is not directly linked to Suunto ZoneSense:
does anyone know if using the heart rate belt and the Suunto+ Suunto ZoneSense application reduce the autonomy of the Suunto vertical significantly ?
(I want to use it for a long trail)

No, in fact the belt should improve battery life but will not make much of a difference. The Solar version should go 90h so your long trail is indeed long:)

[jussim]

Alright, I get the frustrations with no ZoneSense data appearing on app. A recent personal example: I finally got to do a decent workout. I did it three parts - warmup, threshold workout, cooldown - because of shoe change. After syncing with the phone, to my dismay, only warmup appeared to have ZS data. But then I also noticed that the two other activities didn’t have “…” option on activity listing, i.e. I wasn’t able to edit them. I don’t know the ins and outs of Suunto’s cloud but I reckon it might be the case of those activities being queued up for analyzation. Lo and behold, some hours later the ZS did appear.

Just one experience, I know that obviously this isn’t the case for everyone

[Danny poleg]

I couldn’t find the topic that’s why I’m asking
Do you notice a relatively long response time to changes in zonesens.
I will give an example of changes in pace and heart rate changes, the watch immediately reacts but ZONESENS takes more time to react to a change in the transition from aerobic to anaerobic or in the transition from anaerobic to vo2max

[Mff73]

@Danny-poleg
as far as i understand it (and i am far from being an expert) : zonesense zones are not HR zones.
Zonesense zones are computed from HR RR and, to my understanding, re like full body situation in regard to aerobic/anaerobic/vo2max factors
My understanding : when HR is reaching some HR anaerobic zone or VO2m zone or back, Zonesense will not switch to the same zone as well (it would have not sense), it is taking time to “accumulate” enough anaerobic/vo2m or other time to “discharge” as well.

[Danny poleg]

@Mff73
First of all, I’m not such a great physiologist, but I enjoy the product and ask to understand
When you perform an analysis of zonesens in the app, for example aerobic & anaerobic threshold appears.
And a certain pulse appears - for me, aerobic threshold is 125
When I pass the 125 heart rate shown on the watch I expect the watch to jump from green to yellow but it doesn’t happen right away sometimes the heart rate goes up a bit more until it changes
It is possible that it is slow to change is because every training session changes the range data???

[Mff73]

@Danny-poleg
i am neither physiologic, and maybe i also totally misunderstand all this.
But,
it is said that zonesense is : not something for instant management not for quick/shot intervals.
Plus, it is said that zonesense is analyzing live RR data, thus from current workout, and thus trying to calculate current thresholds --> if you are not fit that day, tired, or not, etc… this context of current workout cannot be related to zonesense previous “indication”.
So, to my understanding : “you” should see globally now and in the future what zonesense is “suggesting” to you, and adapt (or not) your HRzone accordingly (if you still need/want to use those HRzones).

And, again, i would like to be corrected by any experts, as it is just my own understanding of all this new thing.

[Danny poleg]

@Mff73
The truth is, now that I’m reading what you wrote, it seems that you are indeed correct
What I will do now is write down the threshold data that appears in today’s training data and compare it to the next training I will do.
I, like you, would love to learn from the members here on the forum.

[Christoph13]

@Mff73 I do not have first-hand insight into the actual algorithm used but ZoneSense much like other methods that try to make sense from a noisy input integrates over a certain timespan and thus requires some burn-in time and somewhat independently from it there is a response delay.
The figures at the moment are 10 minutes burn-in and a 3 minute time window mid-activity.

The watch itself will discard the 10 minute burn-in data because it needs these to begin to find a pattern in the beat-to-beat interval data and again needs some time to adjust to major changes during the workout. It will not stop displaying data once it has tuned itself in but don’t expect strictly real-time responses. After three minutes or so at the new intensity the data will start making sense. Shorter intervals will trend in the correct direction (harder efforts will display higher ZS zones) but where you land precisely on that scale in absolute terms is computed more reliably on a minute and longer timescale.

[duffman19]

@Christoph13 Thank you for this explanation. Where did you come across the 3-minute window? I’ve read through some of the documentation, but hadn’t seen this figure yet.

Anyways, it matches perfectly with what I have observed. I’ve been running short hill repeats recently of about 4-5 minutes each. I’ve noticed that ZS doesn’t start to spike until I’m almost at the top of the hill (3-4 minutes in). This now makes sense if it needs that 3 minute window to start throwing out the effects of the easier downhill and start building in the uphill effort.

I know ZS isn’t meant for these short intervals, but the simple idea that it’s calculating effort over a 3-minute window has made it easier to interpret the results I’ve seen.

I think Suunto is going to need to do a better job of explaining exactly what ZoneSense is and what it is not, how it works, and what users should expect from it. I know there’s documentation out there, but the average user isn’t gong to pour over any of that. I don’t know that I have any suggestions on how to do this. Simplifying such complexity is a challenge in itself.

[halajos]

@duffman19 there’s a nice video lecture from Suunto about ZS: https://youtu.be/bD3O4BZ9vIc?si=7CPMIx6Slnj79Q-i

[Brad_Olwin]

@Danny-poleg said in Suunto ZoneSense:

@Mff73
The truth is, now that I’m reading what you wrote, it seems that you are indeed correct
What I will do now is write down the threshold data that appears in today’s training data and compare it to the next training I will do.
I, like you, would love to learn from the members here on the forum.

To add to what @Mff73 said, ZS is not HR and is not meant to function as HR. Instead it is a real-time feedback on your effort if you have a newer watch. For example, if you did a long hard workout or intervals the day before your AT threshold in ZS is likely to be lower than your typical threshold. ZS is not necessarily meant to set thresholds but depending on the number and intensity of workouts should give you a good idea of where your zones are.

The power of the real-time feedback is to help you achieve the desired intensity for a workout or monitor intensity for a Race. ZS is already proving a game changer for me, my training and my racing!

[Brad_Olwin]

@duffman19 Suunto have done this very clearly in the video @halajos linked.

[duffman19]

@halajos @Brad_Olwin Yes, I watched that. I’m (somewhat) interested in the new metric and I barely made it through the video. That might say something about my attention span, but I’m gonna guess the average user isn’t going to sit through that.

I am aware there is a delay in the analysis, I just didn’t recall hearing the specific 3 minute window mentioned. That goes a long way to help my understanding of the post-activity graphics.

On the other hand, the ad produced by Suunto to introduce ZS does nothing to explain how the metric is derived. This is the video most users might see, if anything at all. My point above was that Suunto has a lot of work to do if they want ZS to be a selling point for their products. And this is evident by the many puzzled reactions from users in other forums.

[Mff73]

Maybe a graph bug.
One this graph, limit between aerobic and anaerobic seems to be at 150bpm

But on this one it is at 160 (same activity ofc)

And correlated with AT proposal

[Ze Stuart]

@duffman19 I’m with you: I love that they put the effort into explaining the new metric, unlike Garmin who might put together one page, somewhere, maybe… but the reality is very few people will watch one of those videos, let alone all of them. Case in point:

We are a species that worships little devices designed to support the attention economy, with the optimum length of a YT video being something like 12m.

Regardless of what point is made, somewhere, in a 54m video, it’s going to be unavailable most.

[mlakis]

@Mff73 I don’t think that the ZS axis (on the left) is to be correlated with the axis (on the right) of the second metric selected (here is HR, it could be something else, elevation etc).

[Mff73]

@mlakis
Omg, but you are right , I feel stupid now. .