Skip to content
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

Auto-detect Critical Power parameters #14

Open
alex-hhh opened this issue Oct 16, 2017 · 0 comments
Open

Auto-detect Critical Power parameters #14

alex-hhh opened this issue Oct 16, 2017 · 0 comments

Comments

@alex-hhh
Copy link
Owner

It is tedious to manually setup CP trend plots and update the CP data with the resulting values. This workflow is indented for determining current CP values, or ones for an entire season and does not work well if there is already a large amount of historical data present in the database.

A mechanism could be added to quicly estimate historical CP parameters. This could work as follows:

  • the algorithm should be given a date range and sport as input.
  • get the sessions, group them by week
  • for each week compute the aggregate best avg for the sessions in that week
  • do a rolling best avg aggregate for the past 4 to 6 weeks, and estimate CP on these.
  • need to re-check if the W'Bal becomes negative for any of these sessions. What to do about it?

All this should be given some GUI which would allow updating the CRITICAL_POWER table. Think about erasing/restoring previous data.

The algoritm could also run on import and monitor any potential CP changes, prompting the user to update them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant