So, I was thinking about this a bit while doing the “travel thing” as I head back to the glorious heaven of Colorado.
Let’s say I do a 10 mile run at an AHR of 150. A run I did here earlier this week is an example of that.
This is not the most perfect example because two things happened in this run above: 1) some natural drift, and 2.) I stuck more to a pace than a particular HR (these are sort of saying the same thing). In other words, I could have looked to have held the HR tighter to 150, but for the sake of the thought experiment I am going to kick around here … this run works. 10 miles, AHR of 148 bpm for 78 and 3/4 minutes.
Here’s is where I start picking at this a bit. 148 bpm times 78.75 means this run took me: 11655 beats.
Question: do all 10 mile runs take me about 11655 beats? In other words, if I go faster, and hence at a higher heart rate, will I finish sooner but with a higher heart rate that still multiplies to a product of 11655? (I am pretty sure the answer to this is no, particular at the top end, but it is an interesting experiment to consider). And what about mix speed (interval) runs?
Here is run over Green Mountain, down Bear Canyon and the Mesa last week. Very different run. 10 miles but with close 2700 feet of climbing and at elevations five to eight thousand feet higher than the run above. AHR was 139 over 122 minutes. 16958 beats of the ticker.
Okay, hugely different. Maybe it does not work to compare sea level runs to altitude runs, or ones where I climb versus flat runs. Maybe it is better to compare runs that are more similar. Where could do that?
Here is the HR data from Pikes Peak Marathon 2010. 4:30:55 or we can call it 271 minutes at an average HR of 170. 46070 beats to take that round trip.
Here is Pikes Peak from 2009. That was 4:53 effort. Average HR was 166. 48639 beats. So a lot closer. Could be coincidental I guess.
It is hard to make comparisons, and all measures are flawed, but I think there might be something to consider here that the number of beats as a measure of work. Clearly I performed better in 2010 as measured by the result time, but the HR data also shows that. I was able to maintain both a higher HR for the distance of the race, but by executing more quickly and being more fit, it was a less amount of beat work.
Or something like that. I might mull on this a bit more. Your thoughts?
Optimal races generally minimize heartbeats, sure. And, sure, heartbeats are one measure of work. To a small degree, you could improve pain/discomfort threshold to run at a slightly higher heart rate, but most of the goal of the training effect is to run faster at a given heart rate, right?
ReplyDeleteYou mentioned intervals. Another thought experiment: race a 10k, and then immediately race 20M (instead of a steady marathon race). Both of those examples, versus running steady, were run at an unsustainable pace for the planned distance, leading to unnecessary early and accumulative stress.
You've heard people say, if you go out seconds/mile (or heart rate) in a race, you'll pay for it <2x> (or pick your multiplier) in the second half, etc.
The *advantage* of planned races and the human ability to understand (and overthink!) them -- as opposed to running from a mountain lion for survival -- is precisely the ability to plan the appropriate pace to minimize effort for the distance.
I am not a physiologist.
ReplyDeleteBut one unit of Work is Calories. So to look at this from a 'how much work does it take' is 'how many calories did I burn in this workout'.
The more fit you get, the lower your heart rate will be at a given speed for a given workout, and the fewer the number of calories you will burn. All things being equal.
So if you did 2 Pikes Peak Races at the same average heart rate but got done 25 minutes faster in one of them, it took less work for you to do it because you burned energy at the same rate but for less time.
Or something.
Or not.
Ask Lucho. My heart's not in it.
ReplyDeleteYou lost me at "heart rate calculations" ;)
ReplyDeleteUmm...I think all of that travel may have fried your brain - could you first please explain why the total number of heartbeats really matters?
ReplyDeleteTo be a total geek I will point out that Brett is technically incorrect. You do the same work (work=force*distance) independent of how long it takes for you to go up and down Pikes.
Cyclists are fortunate, a power meter is great for measuring absolute work performed (if you care about such things).
ReplyDeleteIt might be interesting to see/chew on the respective TSS values for your Pikes examples.
http://home.trainingpeaks.com/articles/running/running-training-stress-score.aspx
If you upload the Garmin data to TrainingPeaks it will calculate for you.
Jim and Jill - well said.
ReplyDeleteChris, I have used TSS in the past. Very similar concept.
Nick, of course I know that W=Fd, (or perhaps better stated as the more simple W=mad), I guess when I said that I was thinking that the heart muscle moves some distance from initial velocity of zero. :)
Mike, Brett - yeah, ultimately all the HR mumbo jumbo means nothing ultimately. All about the watch at the end of the day.
Brett - Mike Morton is going to be interviewed on the next talk ultra podcast!
Not sure if you have looked at this training effect (TE) software and the associated white papers.
Deletehttp://www.firstbeat.fi/consumers/heart-rate-monitors/firstbeat-intelligence-in-heart-rate-monitors
(see white papers on EPOC and Training Effect)
Looking at both the integrated HR data and the recovery rate for a given training session allows for a reasonable calculation of the effect of the session. Monitoring this TE for feedback in your training progression planning helps ensure that your recovery days are, in fact, recovery, and that your hard days are, in fact, hard. Most focused athletes have no problem producing for the hard days, however, as you know, the recovery days are very important and it can be mentally difficult to actually go that slow. Monitoring the TE during those L1-L2 sessions really helps to ensure a proper workout progression and the likely resultant high performance on race day.
I ran into this software when I bought a Garmin 610 and it was included in the watch firmware. Having been a coached competitive endurance athlete in my younger days I resonated with the utility of knowing what the training session yielded as far as effect on base training. This was always difficult to determine in the pre-gadget days of the late 70's-early 80's. Many of us would inadvertently over-train leading to non-optimal performances and, for some, debilitating periods of lethargy. I started a planned 3-year base-build-up and periodization scheme to try to attain a high level of fitness and competitiveness now that I have retired from my profession. Having used this software-firmware with the watch for the past year has really helped keep my training on track. Ramping up to a 750 hr training year and keeping the hard workouts hard and easy workouts easy has led to enjoyable racing and some success. You might take a look at this (or other similar analytic approaches) to monitor your training and planning.
Roland - thanks - I will check these out and post back on them.
ReplyDelete