Hello
Back after a long summer, but I found a very strange bug today when doing a workout.
The total time of it was 44:00, but it seemed to lose seconds throughout, so it became increasingly off, and it was done at 43:40.
Attached are some photos from when doing the workout, towards end, an image from the workout editor, and then the ending power graph from Strava. All intervals where had the same power targets.
It might be this :20 problem. We need to check this. We use decimal minutes instead of seconds (long story) and converting to seconds with rounding/flooring can lose 1 second. We had fixed this but maybe it came back. One other user seems like they mentioned this. We will check.
When analyzing the file in Golden Cheetah it seems like the total length of each of the 5x40/20 seems to be correct, but they are off by 5 seconds each (first one on time, second one starting and ending 5 seconds earlier, third one 10 seconds and the fourth one 15 seconds). So it seems like it’s the 3:00 rest that are five seconds shorter than defined.
That’s odd but thanks for doing this, can you send me link to the original workout?
See below. So some how this is relate to your specific devices but don’t ask me why. I still need to research more. I also go 1s extra.
Did a 40/20 4x6min workout just now, and tried to do some on-the-fly analysis.
It seems like it’s the 20 second part that gets shortened about one second each time and this makes the whole workout shorter. Additionally, the interval timings (lap times) are still ”correct”, so the lap times gets one second off each time a 20s interval is ended. So the app does shift the power, but it doesn’t add lap times according to the shifts but according to the workout file. So one part makes a rounding error, whereas the other part doesn’t. So you seem to calculate timings based on the workout file in two different ways.
I’d say this incoherence is more annoying than the rounding error, although both are still a nuisance.
I use a Tacx Neo Bike, first version, and the app is running on a 8th gen iPad.
Yes, this is a problem that we use decimal minutes (early design flaw based on how ERG files work). Some how we fixed this and it came back. I know what the issue is. Instead of rounding it is converting to an integer. This is on the list to get fixed next.
Oh we had another thread on this and actually resolved the 20 second issue and then another user @amsgator felt like it was back again. I will add him here so he can help. I say that because I just tested it and a 4 minute workout turned into 4:01 added a second at the end but actually was correct.
So it’s some more complicated scenario or device specific some how. If you guys share workouts I can try to reproduce it.
workout
Trainer Day.
completed activity
https://app.trainerday.com/activities/691592f65320e35d939d8eba
One other user felt he saw seconds being dropped possibly related to switching from erg to slope mode. Probably not related but just mentioning it here.
The workout on mine was the correct total length as well, but the intervals were not. The issue is present in your screenshot as well. On each successive interval, the power curve moves sooner and sooner than when it should be (compare your actual power line to where it should be on the graph). Yours is behaving exactly like mine was.
If you hover over the power line, each interval is only 19 seconds.
First starts at 0 and Ends at 0:19.
Second one starts at 0:59 (instead of 1:00) and ends at 1:18.
Third starts at 1:58 (instead of 2:00 like it should) and ends at 2:17.
Fourth starts at 2:57 (instead of 3:00) and ends at 3:16.
It’s losing 1 second each time from where TD is controlling the power/intervals.
Oh I see. Now I get it. Thanks for clarification.
Here is a link to yesterday’s activity
https://app.trainerday.com/activities/6914ca7f5320e35d939a2b61
And the actual workout
You can clearly see the drift in the activity, as well as the difference in total length.
Yep, the drift is exactly what it does to me also. I’m on iOS. I’m not sure if it’s limited to the iOS version or if Android is also affected.
Fixed, thanks guys. Next release coming in a couple days. @amsgator you will see it today in the beta version.
Oh yes, that’s brutal.
Ok this fix is available now.
Did the same workout today, and the timings were spot on!
https://app.trainerday.com/activities/692f27305ada592cf79a7767
