Suuntoplus Decouple
-
I tried to use the decouple aerobic efficiency app on a 20km run yesterday, activity set to custom based on Trail Running. From the app description, the first 10 minutes of the activity are ignored, the next 10 minutes establish a baseline, then the app displays current efficiency compared to the baseline. My HR was in the low 130’s for the baseline period, more or less stayed there for an hour, then moved up to high 130’s, just into low 140’s by the end of the run. So aerobic efficiency decreased, but not by a massive amount, and not until a good 40 minutes after the baseline should have been calculated.
Whenever I checked the app display it was “-- %” with “High” in red. At no point was a percentage displayed. Have I misunderstood how this is meant to work? I was expecting a low percentage, gradually increasing, but no more than 10% even at the end of the run. -
@ianharding
this app doesn’t work for me either. I guess it’s either under further development, fine tuning or fixing -
@ianharding I tried yesterday, this is my result. It was a z2 run, but not a long one. Does this mean that I can go faster during those kind of runs?
-
@ianharding Do you have a general idea of where your Aerobic HR is? It sounds as if you went out too fast. The app has worked fine for me with a 9 Peak Pro. If you go too hard during the baseline, you will not get an estimate. My LT anaerobic is ~165 and my aerobic threshold is mid to high 140s, which is high as tested with blood lactate. To test this your baseline pace should be low enough that you can talk in full sentences. I can sustain my aerobic threshold for most of a 100 mile race. I just finished a 50k with an average slightly above this at 149 bpm average.
-
@Likarnik This is telling you that your Z2 level is below your aerobic threshold. If you were at the top of Z2 it is probably set to low. It depends on the avg HR for your run.
-
@Brad_Olwin my LT HR is 180bpm, yesterday’s run was at an easy long-distance pace of 7:00/km, on a level trail, virtually all in the 130-140bpm range.
-
I have tried this app a few times, and have had results about 50% of the time. I suspect that if your pace (or power) drops to zero after the warm up/baselining period (e.g, pausing the exercise) it causes this problem.
It could be a ‘divide by zero’ issue in the algorithm?
-
@Brad_Olwin thanks, I was thinking in similar direction too. My avg for this run was 141, and max 151. Upper Z2 limit is set to 145 (tested in lab exactly 1year ago), maybe (hope so) I’m fitter now and I can set the bar higher. If I understand correctly, around 0% should be just about right?
-
@althaea35 said in Suuntoplus Decouple:
I have tried this app a few times, and have had results about 50% of the time. I suspect that if your pace (or power) drops to zero after the warm up/baselining period (e.g, pausing the exercise) it causes this problem.
It could be a ‘divide by zero’ issue in the algorithm?I had auto-pause enabled, which activated twice while I waited to cross a road at 00:10:00, and 00:10:02, which would be at exactly the point the baseline calculation started. Maybe that confused the algorithm.
-
@ianharding Don’t use autopause, as I am sure the pauses will affect the calculations.
-
@Likarnik Indeed, I would try again closer to 150. I found that mine had improved at the last race I did, Ran 6h in Z3, which I should not be able to do……
-
@Brad_Olwin so you think that you can not run 6h in Z3? My last race in august (50k, 2400m verical gain) was also 6h, with 160bpm avg, that is deep into current Z3. Same race last year (before lab test) was 6h20min with 163bpm avg. Was my test not accurate? I think I should do it again…
