something wrong with CP estimate in last workout

[Jean-Joël Bataille]

The CP estimation worked well until the last workout (file attached).
The analysis of this workout shows a CP estimate equal to 0 w.
This workout was recorded on kickr snap home trainer and with GC.
Do you have any idea what happened?
Thanks in advance

[Ale Martinez]

It is not directly related to this workout in particular, as explained in the Wiki, model estimates are computed using last 6 weeks data, and CP Extended model needs workouts longer than 1hr. Likely your last >1hr workout is outside of this window now.

[Jean-Joël Bataille]

My last training session, three days ago, lasted 1h30.

[Ale Martinez]

El martes, 12 de abril de 2022 a la(s) 10:41:11 UTC-3, jj.ba...@gmail.com escribió:

My last training session, three days ago, lasted 1h30.

Another common issue is a wrong model name after upgrade, since model names have changed in v3.6.

Other than that, using a CP chart in activities view with 6 weeks date range allows better control to understand what can be happening. 

[Jean-Joël Bataille]

Thank you. After deleting ans reimporting the activity overview chart, the problem disappeared.

[Allan Bell]

Could I also ask for some advice on this please?

I have 5 activities all longer than one hour, all containing power from 11/04/22 to 17/04/22

When I select the activity 17/04/22 the function estimate(model, parameter) returns no parameter data (cp, ftp, w' or pmax)  for models cp2, cp3 or ext

When I select the activity 15/04/22 the function returns all values for all models.

If I import activity 15/04/22 and change the date to 19/04/22 then the estimate function works again for all dates.

If I delete the activity 19/04/22 the estimate function stops working again for 17/04/22.

Deleting and re-importing the overview chart did not work for me.

I also tried deleting 17/04/22 and re-importing the activity.

Version 3.6-RC1

Any help is greatly appreciated!

Allan

[Allan Bell]

Hi,

I just noticed the ride that gave me problems with the estimate function was on Sunday 17th, it was only when I uploaded another ride after 17th that the function started returning parameter data again.

I have uploaded another ride today, Sunday 24th and the same thing happens, the estimate function returns no parameter data for models cp2, cp3 or ext when I select todays ride.  If I select yesterdays ride or any previous rides the function returns data.

It may be a coincidence that the two problem rides were both on a Sunday, or may help point to where my problem lies?

Thanks in advance.

Allan

[Ale Martinez]

El domingo, 24 de abril de 2022 a la(s) 10:50:01 UTC-3, Allan Bell escribió:

Hi,

I just noticed the ride that gave me problems with the estimate function was on Sunday 17th, it was only when I uploaded another ride after 17th that the function started returning parameter data again.

I have uploaded another ride today, Sunday 24th and the same thing happens, the estimate function returns no parameter data for models cp2, cp3 or ext when I select todays ride.  If I select yesterdays ride or any previous rides the function returns data.

It may be a coincidence that the two problem rides were both on a Sunday, or may help point to where my problem lies?

Estimates are pre-computed by weekly using previous 6 weeks data, not for every day or ride.

If you can build from source, turning ESTIMATOR_DEBUG to true in https://github.com/GoldenCheetah/GoldenCheetah/blob/be1af0f6d640b38c66df8bb707d6ebc1e4edb7d2/src/Metrics/Estimator.cpp#L3 and running GC from a terminal or command prompt will provide detailed information.

[Allan Bell]

Thanks for getting back to me Ale,  I understand that the estimates are calculated based on previous 6 weeks data, it's just strange that the function stopped returning any parameters when I uploaded a ride on Sunday and selected that activity to view.  If I view Saturdays ride, I get the estimate parameters from the previous 6 weeks, but when I view Sundays ride I get zero.

I'm sorry but I don't have the ability to run the test that you asked for, but if you need any data from me please let me know.

When I upload another ride this week the function will work again so it's not a big deal, but at the moment it is returning zero.

Thanks

Allan

[Ale Martinez]

El lunes, 25 de abril de 2022 a la(s) 06:25:49 UTC-3, Allan Bell escribió:

Thanks for getting back to me Ale,  I understand that the estimates are calculated based on previous 6 weeks data, it's just strange that the function stopped returning any parameters when I uploaded a ride on Sunday and selected that activity to view.  If I view Saturdays ride, I get the estimate parameters from the previous 6 weeks, but when I view Sundays ride I get zero.

As I commented before estimates are computed by 7 days periods (aka weekly), not for every day or ride.

In this case, on Sunday you are seeing the estimates for a different week than on Saturday, what happens when you add a ride for Sunday is a new week -with just that ride is included in the calculation- and a full week -the one 6 weeks ago- is discarded, so at this point only the previous 5 weeks plus the ride on Sunday are used for estimates, when you add a ride on Mon/Tue/etc. they are added to the set until Sat.

This way the fact new rides change estimates for previous days is expected, you could get zero estimates if data is not enough to fit the models at some point in this process.

[Steve Edmonds]

--

I have built Estimator.cpp with ESTIMATOR_DEBUG true and now have an understanding now what is happening with Allan's data.
The 7 day period is defined by the first activity with power, even if that activity is 24 weeks in the past, so if that activity is on a Thursday the week is Thu. - Wed. and if the first activity is on a Sunday then the week is Sun - Sat.
In Allan's case with the first activity 7 Nov 21 the last week with estimates is for Sun Apr 17 2022 - Sat Apr 23 2022: and the activity Apr. 24th produces zero as expected.
When the first activity is 17 Mar 22  the last week with estimates is for Thu Apr 21 2022 - Wed Apr 27 2022: and so the activity Apr. 24th produces a value.

[Allan Bell]

Firstly a big thanks to Steve Edmonds for his help so far with this.

My week runs from Sunday to Saturday as we discovered.  But I don't think it is correct that the function "produces zero as expected".

When I upload a ride (>1hr with power) to "new week - day 1" (Sunday) - the estimate function on the overview page returns zero.

When I remove that ride and instead upload it to "new week - day 2" (Monday) - the estimate function on the overview page returns a value.

It's only when I upload a ride to a new week day 1 that I have a problem, this happens every Sunday in my case.

Is there a formula I can use to force the function to return a value based on the previous 5 weeks data if weekday = Sunday?

I appreciate your help.

Allan

[Ale Martinez]

El lunes, 9 de mayo de 2022 a la(s) 07:08:13 UTC-3, Allan Bell escribió:

Is there a formula I can use to force the function to return a value based on the previous 5 weeks data if weekday = Sunday?

Look for estimates and daterange functions in the wiki about formulas. 

[Allan Bell]

After much trial and error this seems to get over the issue for me!

if (metadata("Weekday")="Sun")
{daterange(Activity_Date-6,Activity_Date-1,round(estimates(ext,cp)/2,2));}
else
{round(estimate(ext,cp),2);}

I'm not sure if this is correct, but it seems to return the previous weeks estimated data instead of zero when I select a new week day 1.

Thanks for your help.