-
Notifications
You must be signed in to change notification settings - Fork 177
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
Using RSS ahead of HRSS for specific runs #912
Comments
Pinned. And for cycling:
Link: |
Thanks for picking up Thomas, and thanks again for all the hard work! I see a few other people have had similar requests (apologies, I did try and search to see if there was already an open ticket, couldn't find any!). I'm not too clear on the status / resolution though, may have missed it in one of those other tickets - is the ability to chose RSS over HRSS for specific runs something that you are planning to introduce? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it didn't had recent activity. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it didn't had recent activity. |
I have a similar request. My power meter died halfway through my ride, so I have an inaccurate PSS; there should be an option to choose HRSS instead. |
Hi,
I'm just wondering if it's possible to get elevate to use RSS ahead of HRSS for specific runs?
I've done a couple recently for which I didn't wear my HRM strap. My watch has a built in HRM, so HR is still recorded, but ti's totally inaccurate when running (far too low), leading to totally inaccurate HRSS. In these cases the RSS would be a much better approximation.
Would be great if there's a way to do this - it's annoying to know that my fitness trend is incorrect because of this.
Thanks
Aidan
The text was updated successfully, but these errors were encountered: