Activity Tags & New ZoneSense (DDFA Index)
-
@The_77 agreed, and as alluded to in my OP you’ll note I make reference to ensuring from day 1 of having the watch all the zones across run and bike had been configured for HR, Pace and Power based on my known LT1 and LT2 metrics across each of those measures (HR, Pace & Power).
I’ve been using TP for a long time, and regular test (including having been lab tested in the past) so I know the values I’ve dropped into the watch for the zones are correct - the only assumption I had to make was where are Suunto drawing their line in the sand as far as LT2 is concerned, and through process of elimination (using TP as a reference) can confirm they’re using the upper z4 for HR, Pace and Power as TSS will match when I mirror those values. Note : rTSS is calculated against the upper z4 pace value based on the activities NGP.
What I don’t understand, is given these are clearly the correct inputs for the TSS calculation, how can a run in mainly Z1 and low Z2 be tagged ‘Aerobic / Aenarobic’? There must be something else being considered when the tag is generated in Suunto app, and that’s my question.
-
@Sebastian-Wagner-0 thanks - see response to @The_77 as applies to your reply too re: correct zones etc.
It’s an interesting topic and while it’s not a massive issue, I’m just interest to understand how they’re arriving at the tagged value as something doesn’t stack up for my activities despite me knowing (very precisely) my zones across all measures.
-
I am with you on this topic. I Like to understand the Development and Parameter of the Taggs a bit more. And Know how much They weigh the different zones and Parameter against each other to get the different taggs
-
@Grundy82
Realy cool that you have up to Date zones. How do you manage to keep them up to Date?
One more question what Test do you use to Define your pace zones in Running? -
@Sebastian-Wagner-0 slightly different for run and bike…but here you go :
Bike: I use Trainer Road and have done for a number of years. In the early days using TR, I’d do a 20 ramp test, which I much prefer(ed) than a 40min all out. In the last 18 months I now rely on their AI FTP detection feature, which I exclusively use to keep on top of my FTP. When that changes, I always update my power zones to ensure accurate TSS.
Run: while I’ve done a lab test (gas exchange) in the past, that’s not practical on a regular basis, so I now field test. I should do it more often than I do, but it will depend on my training goals and races. I use the well knowing 30min protocol that’s recommended by many coaches, so a warm up into a 30min consistent effort - I take my Avg HR for the last 20mins as my LTHR and same for pace.
I’ve found the more times I’ve done this test, the more accurate the results have become.
I also have a styrd pod, and have read up a lot on Mr Palladinos documentation around his approach to running with power. It’s very interesting, but I never took to it and now only use the pod for pace on the treadmill tbh.
What I would say, it I used my run CP from when I tested with styrd as the Z4 value on my vertical. Obviously the power values will not be like for like, so it might be that which is impacting the tags…I’ll have a look. I do think from when I looked at the suunto power values, they didn’t seem too dissimilar to those I used to get from the styrd for the same pace / HR
-
Cool. Thx for your insights.
I did the run Field Test with the Suunto + App. Aerobic threshold, it think it was the test you mentioned. There i found a Chart to get all my hr zones. But i found no Chart to calculate the pace zones. Do you have a Chart to calculate the pace zones from a Field Test?
I will try to do a power Test Protocol After my next Trail Ultra with the onboard power from Suunto. Maybe then i get better values
Stryd and Suunto power for me Are in the easy Running Similar but Not the Same . At the Moment i use the roughly estimate Chart from Steve palladino.Which tss do you let the Suunto App use? Automatically After a run i See the pTSS, now i Found out i Could Change that to the other versions of TSS and they differ a Little Bit. Of i Change the tss, Suunto App asks me if i will Save the Change for the Workout in the Future.
-
@Grundy82 said in Activity Tags & New ZoneSense (DDFA Index):
@The_77 agreed, and as alluded to in my OP you’ll note I make reference to ensuring from day 1 of having the watch all the zones across run and bike had been configured for HR, Pace and Power based on my known LT1 and LT2 metrics across each of those measures (HR, Pace & Power).
Yeah I skim read only HR, my bad
What I don’t understand, is given these are clearly the correct inputs for the TSS calculation, how can a run in mainly Z1 and low Z2 be tagged ‘Aerobic / Aenarobic’? There must be something else being considered when the tag is generated in Suunto app, and that’s my question.
That I don’t know, but for me at least it changed the mainly Aerobic / Anaerobic to Long Aerobic when I did the proper inputs (mainly correcting power). Beyond that, I couldn’t say, only that this has existed this way since these tags came in.
Now I see you didn’t mention running power in the OP, have you set that yet?
-
@The_77 for running power I’d used zones from an (old) stryd CP test - my logic was the suunto run power seemed to correlate pretty well based on what I’d seen. Having looked at some of my z1 / 2 runs with the vertical, where 100% of my time is in those zones for pace and hr, a significant % is in power zone 3 for those same runs. That may well be what’s causing the tags to report ‘aerobic / anaerobic’ - I’ve now adjusted the zone distribution, mainly where upper z2 ends, so will see if they makes any difference on my next run. Will report back - thanks.
-
@The_77 two runs both tagged ‘aerobic’ following me updating the zone 2 upper limit for power - the 2nd of those runs would’ve certainly been tagged ‘aerobic / anaerobic’ prior to the power zone change despite the HR and Pace being 80/20 (zone 1/2). I’ll keep a close eye on it over the coming weeks, but it would seem that was indeed the issue causing the incorrect tagging despite both HR and Pace being setup correctly (for me).
-
@Grundy82 glad to hear it! Just a quirk of the tagging I suppose that if one data point isn’t setup it defaults to the “hardest” interpretation of any data.
