So here is what happened today:
when I started my ride, Magic Buckets told me to do an endurance ride with a certain amount of low XSS.
I checked the data field a few times, nothing special to see, however, 2 hours in and I open the Magic Buckets screen again (I hardly look at it in endurance mode since I just complete my planned ride and I don’t really care about the real-time numbers) and what do I see? It decided to tell me it’s time for intervals!
Low XSS was still accumulating (so I didn’t lose anything), but now I had high and peak XSS targets. Needless to say I didn’t start doing them 2 hours in to my ride.
I know Xert syncs the data field when the unit is in pause, but it might be a good idea to add some code that avoids switching between endurance and intervals mid-ride?
Hi @ir_fuel , thanks for the feedback. Hard to know without seeing the specifics in your account. Generally best to check the Recommended Training in the Xert Web App, which should correspond with the training you’ll see in Magic Buckets.
There was a bug we identified in the production Magic Buckets data field where the previous days targets could be fetched. This has been resolved in the beta version of the data field - those changes will be pushed to the production version soon
Sort of the same thing happened to me today. I had an endurance day something like 70xss as a goal, I did that ride and got the numbers magic buckets wanted, saved it, turned the garmin off, did the coffee stop after the group ride. On the way back home, magic buckets had interval targets for me. Where did these new ride goals come from?
I think it happens when your high/peak fatigue level drops below a threshold and the system could prescribe you an intervals workout.
Example:
You start ride at 10am, Xert still considers your high/peak systems as fatigued, you get an endurance ride prescribed.
At 11am the fatigue curve for high/peak drops below the level where Xert would give you intervals (imagine you didn’t do a ride yet that day and you were to start riding at 11:30am. Xert determined your high/peak systems are no longer fatigued from 11am onwards and will give you intervals).
Somewhere after 11am Xert Magic Buckets resyncs with the Xert server to get the targets (this happens when the activity pauses or a new one is started). The new target will be intervals, while you are already doing endurance.
Could be that the original goal was 200XSS, all low, and that you did 100XSS, and the system changes its targets mid-ride to 150LXSS, 10HXSS, 3PXSS. (random values as an example), and you’ll immediately see the 3 buckets where the first one will already contain 100XSS.
What you describe should not be possible unless the Garmin unit is paused and restarted which triggers a new fetch from XO.
Are all of you running the production release (version 2.7) or the BETA (v2.2 released today).
The Garmin unit was paused several times. I have auto pause enabled + if I stop to open some food I usually push on the pause button on the device.
But even in this case, can’t you check that there is an activity going on and not overwrite the targets set at the beginning of the activity?
I suggest you install the BETA and confirm if same issue occurs.
Or you could wait for an update to the production release (when BETA is retired).
In the meantime avoid any manual pause which will trigger a refetch. I believe the BETA handles that but keep in mind if something on XO changes while you are out on a ride a refetch will reflect that change.
Another issue is if you have Auto-Sleep enabled on the Garmin which is going to retain yesterday’s targets. If in doubt visit XO Training page to confirm today’s target match and if necessary restart the Garmin.
Another issue is a commuter ride with a scheduled workout later in the day. That will definitely throw things off.
I guessed this is off topic, but isn’t it better to let the recording run even if you stop? The rest is part of the training. Auto pause is one of the first things I turn off. I only pause my computer if I take a ferry to not inflate my distance/speed metric. But for shorter stops it is nice to see how the HR drops.
It doesn’t matter for the end result. The FIT file contains the gap in the data anyway, but you don’t get all that speed and gps noise in the file because you were moving your bike around at the shop or whatever. It’s not as if it doesn’t take that pause into account and artificially increases your average power for that ride.
To give another example: Strava has PRs for different distances (e.g. 100km), that’s always elapsed time, not rolling time.
