Recently I’ve been at the pointy end of SSB2 and have had cause to take a few recovery pauses, eg.
in the latter intervals of Spencer +2 I needed a mid-interval break so back pedalled briefly;
prior to the 3rd and 4th intervals in Lamarck I needed a longer recovery valley so paused the workout during the 2min recovery valleys, while I kept pedalling, to give me an extra minute or two at 40%.
The “problem” is that these recovery pauses aren’t captured by TR, meaning the plot of work performed does not actually represent what happened, leading in turn to my Personal Records being overstated…
For example, my Personal Record chart now shows a localised peak at 46 minutes, formed by 4x 10mins at 100% FTP + 3x 2min recover valleys during Lamarck, but as stated above, that’s not what actually happened.
The reality was that I had a 1x 2mins recovery valley and 2x ~4mins, and hence the 40 total minutes I did at 100% FTP was performed within a longer overall time period (~50 mins) than Personal Records says I did it in (46 mins).
Any time a workout is paused this issue will arise. I could exclude these paused workouts from Personal Records, but that’d be a shame, as even taking account of the pauses some records were likely set and it’d be a unfortunate not to be able to see them.
Is there a good reason (other than some added programmatic complexity) why TR cannot capture these pauses and make use of them in PR calculations? Ideally, the plot of the workout would show, both in realtime and afterwards, where pauses occurred, by extending the x-(time-)axis for the duration of any pause, so there was maximum clarity of what work was actually completed during the session. Without taking account of these pauses the PR data from (indoor) TR rides will be inaccurate and overstated, materially so in some cases.