Do you feel like your running pace and HR threshold values are set properly? It sounds to me like maybe your running threshold pace values are set too low—that’s a very high rTSS for a one hour walk that can’t have covered much distance.
OwenFW
Forum Replies Created
-
OwenFW on June 23, 2021 at 7:55 am · in reply to: Replace Running with Cycling in Cardio training #55060
Unfortunately, fitness developed in both of these activities will transfer poorly to mountaineering. Can you hike? That’s what mountaineering is, so do that.
OwenFW on May 25, 2021 at 5:49 pm · in reply to: Improve AeT with 1 hour extra Zone 2 running every day. #54316Depends on your fitness. For most people properly scaling the training plan (ie making it hard), this would interfere with your recovery each day, reducing your results and increasing the risk of injury and overtraining. More rest and recovery is usually better than more volume for most people on demanding training plans. But obviously I don’t know you or your history.
Following.
Also really interested to hear some answers to this question.
OwenFW on January 2, 2021 at 11:53 am · in reply to: Fasted training vs training longer with fuel #48747My understanding has been that fasted training past about 90 minutes is unlikely to yield any real additional benefits. Probably just make you slower.
Basically, it wasn’t that big day that made you a high-70s athlete, it’s been all the days since then.
If you can maintain that level around 70, your question becomes less relevant every day. The impact of past workouts fades quickly because of the exponential weighting, and after 45 days they are irrelevant to your CTL. Just keep up the good work and don’t worry about it.
It sounds like you’ve confused aerobic threshold and anaerobic threshold. In the threshold settings in training peaks, it is expecting your anaerobic threshold. Your TSS numbers are based on 1hr max HR, pace, or power efforts not on the AeT number that UA focuses on so much.
You just use AeT in setting the upper end of zone 2 in your zones.
Fitness (CTL) is a rolling 42 day average of your daily TSS.
Fatigue (ATL) is a 7 day average of your TSS that accounts for the workouts you have done recently.
Form (TSB) is the balance of TSS equal to yesterday’s fitness minus yesterday’s fatigue.When you take rest days, your CTL will always drop off by a similar amount as a proportion of your total CTL, but when you’re working with bigger numbers (ie CTL of 60 vs 20), the absolute numerical drop will be larger. I.e. 5% of 60 is more than 5% of 20, just to pick some numbers out of the air.
You can use any Bluetooth HR monitor without a watch. The added functionality of a watch is that it’s easier to look at the display without needing to carry something in your hand, which is annoying. But if you’re on a treadmill, a watch truly does not offer anything a phone app doesn’t. Well, maybe cadence but watches aren’t great at that anyway. The Polar Hr monitors and accompanying apps are pretty great.
@trygve.veslum unfortunately, I don’t find that that works well for climbing. On a recent 14hr day, Strava thought I was only moving for 28 minutes. Perhaps if I turned the GPS accuracy for my mountaineering profile on the watch all the way up, it might work a little better, but generally I haven’t been impressed by autopause or Strava’s moving time when a lot of the motion is slow and vertical.
Thanks, Scott.
OwenFW on June 5, 2020 at 7:26 pm · in reply to: Weird result from heart rate drift test (w/ chest strap hr monitor) #42440From the test instructions: “Hold that pace for an hour or so and notice if your heart rate begins to climb.” While Scott is right that the math of comparing the ratios will still work if you measure decrease of pace rather than increase of HR, you will be getting less data: you will only get your AeT and not the associated pace. While this isn’t as big a loss as not knowing your anaerobic threshold pace, which TP uses for calculating rTSS, it leaves you with one less piece of data for planning runs and races. How far will you get in one hour of running at AeT? If you do your test with a steady pace, you’ll know the answer to that question.
The steady pace version of the test is also likely to return more logical results, since *any* starting HR chosen with your steady HR procedure is likely to yield extremely low pa:hr numbers since you may spend no time during the test above AeT, where nonlinear change would start. You could be within one beat of AeT and see next to no drift downward since it would all be linear drift. In the normal steady pace test, you just have to start at or just under AeT, and then some of the 5% will come from nonlinear-increase time above AeT. You could even use a steady-pace test to suss out an AeT that is above where you started the test. Maybe after your warmup you settle on a pace that keeps you at 143 bpm and then find that during the test your increasing HR stabilizes again at 150 and then you end at 1hr with only 2% drift. You probably just discovered that 150 is the number you should have started with.
Finally, it’s really hard to keep a constant HR, but a constant pace is dead simple, especially on a treadmill.
I’m no coach, though, and only have my own results and logic to guide me, so I could be dead wrong!
OwenFW on June 4, 2020 at 8:53 pm · in reply to: Weird result from heart rate drift test (w/ chest strap hr monitor) #42414Farley, it was unclear to me reading this whether or not you are maintaining a constant pace throughout the workout. It sounded like you are maintaining a constant heart rate. I’m pretty sure the math of the pa:hr function wants a steady-state effort, i.e. constant pace (or power for pw:hr). Not quite sure how measuring a change in pace while maintaining a steady HR would mess with the results.