You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: