-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding ability to find time spent in a power or w/kg range #102
Comments
Hi @jstollvt I don't know a lot about sweet spot training so bear with me. Is the normal way this is tracked sort of like time in zones, except you only want to see the time in sweet spot? Or is it identical to seeing time in zones with just different percentages (i.e. not Coggan based zones). |
Hi, Justin - essentially, Sweet Spot is another zone - it ranges from upper
Tempo to just shy of FTP. There are slight variances in the zone's
boundaries, depending on which training plan/philosophy you are using.
TrainerRoad Sweet Spot range is defined as 88-94% of FTP (
https://www.trainerroad.com/blog/sweet-spot-training-everything-you-need-to-know/
)
Andrew Coggan apparently defines it as 88-93% of FTP (
https://www.bikeradar.com/advice/fitness-and-training/sweetspot-training/)
FasCat Coaching defines it as as 84-97% of FTP (
https://fascatcoaching.com/blogs/training-tips/how-to-sweet-spot)
Wahoo defines it as 86-95% of FTP (
https://www.wahoofitness.com/blog/ask-experts-sweet-spot-training/)
I'm sure if you asked some random person on a bike with a power meter,
they'd give you some other slight variance, LoL. :-). Thus, this
would probably be most useful and flexible to allow the user to define
their own range. Further, it might be best to name it something generic
('custom zone' or such), so that anyone curious about how much time then
spent in *any* zone during a ride, would be able to figure that out. That
having been said, I'd say it would likely get its most use for people using
Sweet Spot training - it's quite often the case that a training plan will
say, "Get as much Sweet Spot zone training in as you can today.", and Sweet
Spot is a training darling these days. (
https://www.velonews.com/training/sweet-spot-training-is-hyper-efficient-for-getting-faster-on-the-bike-but-how-much-should-i-do/)
(ie, it's not just me who'd probably be interested in this type of a
feature :-)
Thanks for considering this, and Thanks a Bunch for the really amazing
plugin!
If you decide this feature is possibly worth moving forward with, and if
there is anything that I can do to help, don't hesitate to holler.
Thanks!
Jim
…On Sun, Mar 27, 2022 at 4:40 PM Justin Mayfield ***@***.***> wrote:
Hi @jstollvt <https://github.com/jstollvt>
I don't know a lot about sweet spot training so bear with me. Is the
normal way this is tracked sort of like time in zones, except you only want
to see the time in sweet spot? Or is it identical to seeing time in zones
with just different percentages (i.e. not Coggan based zones).
—
Reply to this email directly, view it on GitHub
<#102 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASNCP54QN4MHENWOTHDEN63VCDBU3ANCNFSM5RYEQLPQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I do a fair bit of Sweet Spot training, and it would be helpful to know how much time in a ride was spent in the Sweet Spot range. The exact boundaries of Sweet Spot can vary depending on whose definition you're following, so it might be better to just allow a user-defined range (ex, 84%-97% FTP, or whatever range the user specifies) - this would make this capability a lot more versatile, as it wouldn't be limited to just Sweet Spot.
The text was updated successfully, but these errors were encountered: