I use DSW, based on HR, for my running and I feel that it often underestimate the TE from the given workouts, especially threshold or tempo workouts (mening I get a higher TE than expected).
For instance, a few days ago I was supposed to run 10 min zone 2 warm up, 2x18 min at 4 BPM below threshold HR with 5 min zone 1 in-between and 10 min zone 2 wind down. I think it was supposed to be about 4 TE aerobic. It came out at 4.9 TE aerobic and 2.3 anaerobic, 67h recovery time and no workout the day after (changed me to rest instead of base). Any reasons for this? I have to admit that I sometimes for short periods of time went up to threshold HR (172 BPM) but the mean HR for the first interval was 170 and the second 168.
My LTHR pace is, according to the watch, 4:05/km, LTHR 173 BPM. This is also a bit strange - I ran at between 3:48-3:53/min at the HRs above.
My maxHR is the same as always (186 BPM) and is set to auto update. Today I ran a maxHR-test and it came out to 186 BPM.
I did the DSW-change from %maxHR to %LTHR 4 months ago (after a LTHR-test in the watch). I was really happy when it upped my target HR by 4 BPM - it meant I could run a bit faster. Another strange thing is that is has tried to downgrade me ever since, by a second/beat or so. In the same time, I've improved my 5 km time from 21 min to 19 min at the track (and the watch thinks I can run it in 17:46 - haven't tried that yet, 19 min was during a threshold run).
I found a table for average %maxHR mapped to training type:
Average % | |
%maxHR | |
Rest | 58.50% |
Recovery |
67.87% |
Base | 74.70% |
Tempo | 83.72% |
Threshold | 88.32% |
VO2Max | 95.19% |
However, my base target HR is 143 BPM, which is 76.88% maxHR.
Any ideas as to why there's this mismatch between DSW and TE?