8,160
edits
Changes
From Fellrnr.com, Running tips
no edit summary
|[[File:Supercompensation-fatigue-small.png|none|thumb|x300px|Without sufficient recovery time, the fatigue builds up until injury or [[Overtraining Syndrome]] occurs.]]
|}
=Quantifying monotony=
One approach<ref name="OTMonotony"/> to measuring monotony is statistically analyze the variation in workouts. The first stage is to work out a measure of the daily [[TRIMP]] ([[Training Impulse|TRaining IMPulse]]). From this daily [[TRIMP]] it's possible to calculate the standard deviation for each 7 day period. The relationship between the daily average [[TRIMP]] value and the standard deviation can provide a metric for monotony. The monotony value combined with the overall training level can be used to evaluate the likelihood of [[Overtraining Syndrome]].
=Monotony Calculations=
The original work<ref name="OTMonotony"/> on training monotony used [[TRIMP]]<sup>cr10</sup> and [[TRIMP]]<sup>zone</sup>, but I substitute [[TRIMP]]<sup>exp</sup> for [[TRIMP]]<sup>zone</sup> because of the advantages noted in [[TRIMP]]. From the daily [[TRIMP]] values for a given 7 day period the standard deviation can be calculated. (If there is more than one workout in a day, the [[TRIMP]] values for each are simply added together.) The monotony can be calculated using
Monotony = average([[TRIMP]])/stddev([[TRIMP]])
This gives a value of monotony that tends towards infinity as stddev([[TRIMP]]) 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=
A similar calculation can be used to calculate a value for Training Strain.
Training Strain = sum([[TRIMP]]) * Monotony
The value of Training Strain that leads to actual [[Overtraining Syndrome]] would be specific to each athlete. An elite level athlete will be able to train up much higher levels than a beginner. However this Training Strain provides a better metric of the overall stress that an athlete is undergoing than simply looking at training volume.
=A simple [[TRIMP]]<sup>cr10</sup> based calculator=
This calculator will show the [[TRIMP]]<sup>cr10</sup> values for each day, the Monotony, the total [[TRIMP]]<sup>cr10</sup> for the week and the Training Strain.
i = numArr.length,
v = 0;
while( i-- ){
v += Math.pow( (numArr[ i ] - avg), 2 );
return getNumWithSetDec( stdDev, numOfDec );
};
function doTrimp(dur, cr10, trimp)
{
}
</script>
<form style="font-family: Helvetica,Arial,sans-serif;border: solid 2px #40a0c0" id="MonotonyForm">
<table style="text-align: left;" border="1" cellpadding="1" cellspacing="1">
</form>
</html>
=TRIMP<sup>exp</sup> Examples=
For these examples we will use just a few simple workouts. Let's assume a male athlete with a [[Maximum Heart Rate]] of 180 and a [[Resting Heart Rate]] of 40, giving a [[Heart Rate Reserve]] of 140. Let's assume our hypothetical athlete does his easy runs at a 9 min/mile pace and heart rate of 130. We'll use only one of the type of workout, a tempo run his easy runs at a 7 min/mile pace and heart rate of 160. This gives us some TRIMP<sup>exp</sup> values for some workouts
{| class="wikitable"
!Type!!Miles!!Name!!Duration!!TRIMP<sup>exp</sup>
|-
|Easy ||4||Easy 4||36||11,13279
|-
|Easy ||6||Easy 6||54||16,699119
|-
|Easy ||10||Easy 10||90||27,831198
|-
|Easy ||20||Easy 20||180||55,662396
|-
|Tempo||4||Tempo 4||28||17,421|-|Tempo||8||Tempo 8||56||34,84162
|-
| Tempo
| 8
| 56
| 123
|}
Here is a sample week's workout with three harder workouts, a 4 mile tempo, a 10 mile mid-long run and a 20 mile long run with four mile easy runs on the other days. This is 50 miles, a total TRIMP<sup>exp</sup> of 145K, Monotony of 1.35 and a Training Strain of 197K50 miles.
{| class="wikitable"
|-
|Tuesday||Easy 4||11,13279
|-
|Wednesday||Easy 10||27,831198
|-
|Thursday||Easy 4||11,13279
|-
|Friday||Easy 4||11,13279
|-
|Saturday||Easy 20||55,662396
|-
|Sunday||Easy 4||11,13279
|-
|<span style='color:#FF0000'>Stdev</span>|<span style='color:#FF0000'> </span>|||15,353<span style='color:#FF0000'>113</span>
|-
|<span style='color:#00B050'>Avg</span>|<span style='color:#00B050'> </span>|||20,777<span style='color:#00B050'>139</span>
|-
|Total| |||145,442972
|-
|Monotony||| |1.35|-|Training Strain||||196,82423
|-
| Training Strain
|
| 1,191
|}
If we give our athlete a single day's rest on Sunday, we reduce the mileage by 4 miles to 46 miles, total TRIMP<sup>exp</sup> goes down 9K to 134K79, but the Monotony of drops more significantly to 1.14 04 and a Training Strain to 154Kdrop 260. So the mileage has dropped about 9%, but the Training Strain has dropped by 2822%.
{| class="wikitable"
|-
|Tuesday||Easy 4||11,13279
|-
|Wednesday||Easy 10||27,831198
|-
|Thursday||Easy 4||11,13279
|-
|Friday||Easy 4||11,13279
|-
|Saturday||Easy 20||55,662396
|-
|Sunday||Rest||0
|-
|<span style='color:#FF0000'>Stdev</span>|<span style='color:#FF0000'> </span>|||16,780<span style='color:#FF0000'>122</span>
|-
|<span style='color:#00B050'>Avg</span>|<span style='color:#00B050'> </span>|||19,187<span style='color:#00B050'>128</span>
|-
|Total| |||134,310893
|-
|Monotony||| |1.14|-|Training Strain||||153,57404
|-
| Training Strain
|
| 932
|}
A further rest day on Tuesday drops the Training Strain by a further 2722%.
{| class="wikitable"
|-
|Tuesday||Rest||0
|-
|Wednesday||Easy 10||27,831198
|-
|Thursday||Easy 4||11,13279
|-
|Friday||Easy 4||11,13279
|-
|Saturday||Easy 20||55,662396
|-
|Sunday||Rest||0
|-
|<span style='color:#FF0000'>Stdev</span>|<span style='color:#FF0000'> </span>|||17,955<span style='color:#FF0000'>130</span>
|-
|<span style='color:#00B050'>Avg</span>|<span style='color:#00B050'> </span>|||17,597<span style='color:#00B050'>116</span>
|-
|Total| |||123,178814
|-
|Monotony||| |0.98|-|Training Strain||||120,72390
|-
| Training Strain
|
| 730
|}
If we compare this with an extreme example of a monotonous training plan, we have a slightly lower mileage (46 v 50), and a considerably 57% lower total TRIMP<sup>exp</sup> (128K 414 v 135K927), but the monotony is remarkably high at 4.7 and the training strain is more than three times 1.6x higher (601K v 197K). In practice, there would be greater day to day variations, even within the same 6 mile easy run, so the results would not be quite so dramatic.
{| class="wikitable"
|-
|Wednesday|Tuesday|Easy 6||16,69954
|-
|Thursday|Wednesday|Easy 6|10|16,69990
|-
|Friday|Thursday|Easy 6||16,69954
|-
|Saturday|Friday|Easy 10|6|27,83154
|-
|Sunday|Saturday|Easy 6||16,69954
|-
|StdevSunday|Easy 6|||3,89554
|-
|Avg<span style='color:#FF0000'>Stdev</span>|<span style='color:#FF0000'> </span>|||18,289<span style='color:#FF0000'>13</span>
|-
|Total<span style='color:#00B050'>Avg</span>|<span style='color:#00B050'> </span>|||128,025<span style='color:#00B050'>59</span>
|-
|MonotonyTotal| |||4.70414
|-
|Training StrainMonotony| |||601,0924.69
|-
| Training Strain
|
| 1,944
|}
=References=
<references>
<ref name="variabledose">Variable dose-response relationship bet... [Med Sci Sports Exerc. 2003] - PubMed - NCBI http://www.ncbi.nlm.nih.gov/pubmed/12840641 </ref>
</references>
[[Category:Advanced]]
[[Category:Science]]