Pete Plan Cycle 2 Week 1 Day 6 Recovery

Ac-Nov-4th-sunrise

Today’s Plan session was designated as recovery, steady distance of from 8K to 15K.  I chose 8K, with pace the highest priority target.  The pace target was 2:20.5, which was the midway point of UT2 (relative to my most recent 2K TT). Second priority was HR less than 75% HRmax.  Last priority was rating 22-25.

By making pace the first priority, it was most certain that the desired recovery level of effort would not be exceeded.

Second priority of HR never exceeded 60% HRmax.  Last priority of rating was rather sloppy but all in all I was happy with the session.

I was trying to keep today’s recovery session in the UT2 zone, as mentioned in the first paragraph.  If the first part of the definition (see the Rowing Lingo page/tab on the home page of this site) of UT2 which is a percentage of power relative to a person’s recent 2K TT is used, I succeeded. But if the second and less commonly interpreted part of the definition for UT2 is used (65% to 70% of the number arrived at by adding a person’s HRR+RHR) then I was rowing too hard.  I consider the first and more commonly used definition of UT2 to be the valid one.  At least, it felt “right” in that I wasn’t working hard enough to sweat but wasn’t working so ultra easy that it was extremely boring. If I’d rowed at an effort level that would have kept my HR at 65-70% HRR+RHR, that would have been in the range of 97 to  104, which would have been a much more boring effort level, to my experience.

Ac-Nov-4-steady-8K-finish
8K finish screen
Ac-Nov-4-steady-8Krpt
8K session report
Ac-Nov-4-steady-8Kchrts
8K charts. I operated the tv remote control a few times after the session started and that was probably the biggest reason for large variations in pace.

RowPro 5 for the Mac (beta) note:  I had a difficulty getting the custom session programmed to be subdivided into 20 splits, so that the distance would be equal for all splits including the final split and the glitch earlier noted could be avoided.  (If the last split distance is not the same as all the previous split distances, the displayed pace for the last split is wrong, because RowPro 5 for the Mac uses the previous split distance value to calculate the pace for the last split). I finally managed to force it to be 20 splits by editing the previous 8K which had been automatically subdivided into 27 splits and instead of choosing to “save” it, I clicked the button to start rowing it immediately.

Happy trails to you.