Hey there,
There appears to be a difference between what the site analysis thinks about buckets fill status, and what the on-road magic buckets datafield calculates.
Is this because of a more complete analysis that happens on the site, similar to when the garmin datafield tells you that you have a breakthrough but psych you actually didn’t, when the site has time to analyze it all?
I’m seeing something similar. Would be good to understand what is going wrong.
It’s pretty much every non-endurance workout. Have received no answer on this through support request. I’m assuming it’s the difference between head unit calculation vs actual engine calculation.
Second by second analysis on XO server will always be more accurate than what the apps can do on their own (EBC or Garmin data fields).
I don’t see a significant variance that would throw off the intended training effect.
134 vs 132, 26.1 vs 24.1, 9.2 vs 8.1. Or 120 vs 120, 19.2 vs 18.7, 10.0 vs 9.4.
IOW close enough.
While it could mean I rode to a different focus target and difficulty rating than the original goal, it was HIT regardless. For me that was the goal.
If the numbers are significantly different it means I had a BT during the activity and the app used my pre-BT signature to estimate XSS while XO analysis applied my new signature.
yeah of course, just something to think about if you wanted those checkmarks
