StravistiX
So I decided to do some more playing around with StravistiX numbers. Previous post found here (
link). At that time, I actually tried to pre-predict the TRIMP score of upcoming workouts based on my own past history and it was actually quite predictable. So if it's predictable and one measure of how training is going (both from a Fitness standpoint, Fatigue standpoint and the balance between them), then it'd be nice to see how my newly designed training plan for Dopey may play out.
The first step was to accumulate all of the data. We've got the following columns:
Week Date
Week TL - which is the Total TRIMP from the week's workouts (Monday to Sunday)
Week TL/HR - which is the Total TRIMP divided by the Total Time spent training from the week's workouts
Date
TRIMP - which is a measure of difficulty of the workout based on HR data and time
Workout
WO Code - which is a categorization of different types of workouts
Fitness - 42 day average of TRIMP (in theory)
Fatigue - 7 day average of TRIMP (in theory)
% Fit Chg - The amount Fitness changed because of this particular workout
% Fat Chg - The amount Fatigue changed because of this particular workout
Total Time
TRIMP/HR - which is the TRIMP divided by time for that workout (essentially bang for your buck)
Description
This is an example of Daniels 10k Training
This is an example of Lakefront Marathon Training
I categorized these workouts to determine the average TRIMP score and more importantly the average TRIMP/HR score:
So from this you can glean the following:
-an easy workout provides roughly 81 TRIMP per hour. If I run for 30 minutes easy, then I get a TRIMP of 40.
-a LR workout provides roughly 112 TRIMP per hour. If I run for 120 minutes at LR, then I get a TRIMP of 224.
Outside of a few blips here and there the values are relatively consistent for different types of workouts.
So not surprisingly, the LR, LR FF, MP, Progression and HMP intervals are some of the more bang for your buck workouts. I found the most surprising was the R+T from Daniels training had the highest TRIMP/HR. So why would that be? Well because you're essentially running faster than HMP intervals with even less recovery time between them. They're very difficult workouts. So not terribly surprising, but still somewhat that they landed on top.
So by having a general idea of TRIMP/HR for workouts I can use that to determine TRIMP scores for future Dopey 2018 workouts.
Black number is predicted TRIMP, Red is Weekly TL, and Green is Weekly TL/HR
This helps me get a visual on the difficulty of the training plan comparatively to the previous two cycles (Daniels and Lakefront).
Dopey will build slowly because I'm coming off the marathon resting period. The other two training plans had lead-ins with no resting period. By week 4, all plans converge similarly. By week 6 of the Dopey plan the Fitness will have "flushed out" the recovery week and will be the true Fitness score relative to just this training cycle. Just in time in Week 8 the plan will near it's peak. In the Lakefront training I had 3 weeks over a Week TL of 900 (with a peak of 909). Dopey will have two weeks over 900 with a value of 918 and 961. So if this works out correctly, then this plan will indeed be more difficult than Lakefront at the back end.
What about pre-predicting the peak of the Fitness score?
I looked at the Weekly TL and divided by 7 to get an average TRIMP for the week. Then I took the average of the previous 6 weeks (waiting until week 6 to start) to get a predicted Fitness score. While not spot-on, these were pretty close to reality. Daniels peaked at 110 theoretical (in reality 102 on 4/23) and Lakefront peaked at 116 theoretical (in reality 114 on 9/21). So the Dopey plan predicts a peaking of 122 in the last week or so right before the 10 day taper. It'll be interesting to see whether that comes to fruition.
Just another tool in the tool box to play around with in an effort to keep getting better!