avondale
DIS Veteran
- Joined
- Oct 24, 2017
- Messages
- 1,987
Easy Run Analysis
I started using plans by @DopeyBadger starting December 2017 through November 2020. After that time, I started focusing more on trail running, and I've been working out my own training plans with helpful discussions with him.
For those of you that have used DopeyBadger's plans, you know that he has easy runs termed EA and EB. For me, at least, each of these types of runs had specific paces that were supposed to be met, within +/- 10 sec. In December 2018, I started adjusting these guiding paces to account for the effects of heat and humidity using a T+D scale DopeyBadger had referenced at some point.
I have another goal in mind for this analysis, but first I wanted to demonstrate that the T+D adjustments really did bring my EA pace back in line with the guiding pace. From this training log, I pulled out all of my EA runs and their info. Between Dec. 24, 2018 and Nov. 21, 2020, this was 179 runs. Below is a graph of the date vs the average pace of each run, adjusted for the T+D.

My EA pace was 11:56 min/mi and the guidance was to try to be within +/-10 s of this pace. You can see that this was generally successful! There were some points that have much higher (that is, slower) average paces, and these are very hilly routes that therefor had slower average paces. There is a trend in the graph, and that is that the average pace was increasing (that is, I was getting slower) over time - this is somewhat distressing.
The real goal of my analysis was to see how my training has been going since I switched to trail running. Since trails have a lot of varying surfaces and typically a lot of hills, I couldn't really run for to a set pace. Instead, I was running by effort: I used my HR as an indicator of my effort level.
I should mention that DopeyBadger's plans also indicate that each training run type should fall within a certain effort level, but I will be honest that I aimed to hit my pace targets rather than an "effort" target.
When I started trail running, I started to term runs as "easy", meaning at an average HR at 140 BPM or less; "LR (long run)", meaning at an average HR of 153 BPM or less; and "tempo", meaning at an average HR of about 160 BPM.
However, looking at the average paces for my trail runs would not be comparable to the data in the graph above because as stated just above, trails are hilly, rocky, etc. So I extracted my "easy" training runs that were on paved trails - all the same trails as I ran for the runs in the previous data set. These were generally mid-week runs - there were 77 of these runs. I had noted the T+D for these runs, but did not run to meet a target pace - I ran to keep my HR below 140 BPM.
The graph below shows the Date vs Average Pace Adjusted for T+D for both the previous runs and the runs where I ran by HR level. The blue points repeat what was in the previous graph, and the orange points are the runs by effort.

This is actually really exciting! The graph shows that my average paces for my runs (on the same routes) are getting lower (that is, faster)! This is the case even though a lot of these runs occurred during hot summer weather.
These runs have a lot more variation in average pace - clearly the vertical scatter is a lot more for the orange points than the blue. I interpret this as indicating that some runs are at higher or lower effort, even with the same weather conditions and route - I was more or less tired, for instance, or perhaps it was the time of day. I am not sure that I have enough data to try to pull out specific effects like that.
I am very happy with the overall meaning of these data: my trail running training, which focuses on running by effort level, is paying off with a speed increase!
I think what I will do next is look at the average pace adjusted for T+D for trail runs on specific trails to see if my speed is increasing. I run on a variety of trails, but there are three trails that I tend to run on most frequently. Even so, I'm not sure if I will have enough data for a meaningful analysis, especially since some of the runs will be "easy" and some will be "LR".
I am encouraged from this to continue with my trail running and training, which is good, because I am really enjoying it!
I started using plans by @DopeyBadger starting December 2017 through November 2020. After that time, I started focusing more on trail running, and I've been working out my own training plans with helpful discussions with him.
For those of you that have used DopeyBadger's plans, you know that he has easy runs termed EA and EB. For me, at least, each of these types of runs had specific paces that were supposed to be met, within +/- 10 sec. In December 2018, I started adjusting these guiding paces to account for the effects of heat and humidity using a T+D scale DopeyBadger had referenced at some point.
I have another goal in mind for this analysis, but first I wanted to demonstrate that the T+D adjustments really did bring my EA pace back in line with the guiding pace. From this training log, I pulled out all of my EA runs and their info. Between Dec. 24, 2018 and Nov. 21, 2020, this was 179 runs. Below is a graph of the date vs the average pace of each run, adjusted for the T+D.

My EA pace was 11:56 min/mi and the guidance was to try to be within +/-10 s of this pace. You can see that this was generally successful! There were some points that have much higher (that is, slower) average paces, and these are very hilly routes that therefor had slower average paces. There is a trend in the graph, and that is that the average pace was increasing (that is, I was getting slower) over time - this is somewhat distressing.
The real goal of my analysis was to see how my training has been going since I switched to trail running. Since trails have a lot of varying surfaces and typically a lot of hills, I couldn't really run for to a set pace. Instead, I was running by effort: I used my HR as an indicator of my effort level.
I should mention that DopeyBadger's plans also indicate that each training run type should fall within a certain effort level, but I will be honest that I aimed to hit my pace targets rather than an "effort" target.
When I started trail running, I started to term runs as "easy", meaning at an average HR at 140 BPM or less; "LR (long run)", meaning at an average HR of 153 BPM or less; and "tempo", meaning at an average HR of about 160 BPM.
However, looking at the average paces for my trail runs would not be comparable to the data in the graph above because as stated just above, trails are hilly, rocky, etc. So I extracted my "easy" training runs that were on paved trails - all the same trails as I ran for the runs in the previous data set. These were generally mid-week runs - there were 77 of these runs. I had noted the T+D for these runs, but did not run to meet a target pace - I ran to keep my HR below 140 BPM.
The graph below shows the Date vs Average Pace Adjusted for T+D for both the previous runs and the runs where I ran by HR level. The blue points repeat what was in the previous graph, and the orange points are the runs by effort.

This is actually really exciting! The graph shows that my average paces for my runs (on the same routes) are getting lower (that is, faster)! This is the case even though a lot of these runs occurred during hot summer weather.
These runs have a lot more variation in average pace - clearly the vertical scatter is a lot more for the orange points than the blue. I interpret this as indicating that some runs are at higher or lower effort, even with the same weather conditions and route - I was more or less tired, for instance, or perhaps it was the time of day. I am not sure that I have enough data to try to pull out specific effects like that.
I am very happy with the overall meaning of these data: my trail running training, which focuses on running by effort level, is paying off with a speed increase!
I think what I will do next is look at the average pace adjusted for T+D for trail runs on specific trails to see if my speed is increasing. I run on a variety of trails, but there are three trails that I tend to run on most frequently. Even so, I'm not sure if I will have enough data for a meaningful analysis, especially since some of the runs will be "easy" and some will be "LR".
I am encouraged from this to continue with my trail running and training, which is good, because I am really enjoying it!