8,153
edits
Changes
m
no edit summary
The original work<ref name="OTMonotony"/> on training monotony used TRIMP<sup>cr10</sup> and TRIMP<sup>zone</sup>, but I believe that TRIMP<sup>exp</sup> is more appropriate. From the daily TIMP<sup>exp</sup> values for a given 7 day period the standard deviation can be calculated. The monotony can be calculated using
Monotony = (average(TIRIMP<sup>exp</sup>)/stdev(TIRIMP<sup>exp</sup>)
This gives a value of monotony that tends towards infinity as stdev(TIRIMP<sup>exp</sup>) tends towards zero, so I cap Monotony to a maximum value of 10. Without this cap, the value tends to be unreasonably sensitive to high levels of monotony. Values of Monotony over 2.0 are generally considered too high, and values below 1.5 are preferable. A high value for Monotony indicates that the training program is ineffective. This could be because the athlete is doing a low level of training; an extreme example would be a well-trained runner doing a single easy mile every day. This would allow for complete recovery, but would not provide the stimulus for improvement and would likely lead to rapid detraining. At the other extreme, doing a hard work out every day would be monotonous and not allow sufficient time to recover. The Training Strain below can help determine the difference between monotonous training that is inadequate and monotonous training that is excessive.
=Training Strain Calculations=