I’ve noticed that the pace ranges synced to my Coros are often excessively wide, making them almost useless for precision training.
I asked chat to regenerate the workout specifically to fix this, and after some insistence, it produced a much tighter range.
My question: Is this a Coros-specific syncing issue, or is the algorithm defaulting to these wide buffers?
Comparison:
Original workout:
Corrected one:
So there’s two ways the chat (or backend agent) can create structured workouts: by specifying the zone (Endurance, Tempo, Threshold, …) or by giving exact targets, which I think it did in it’s second attempt.
If it’s by zone we have some pretty big ranges if the zone is specified as ‘Endurance’ since after all the important thing for Endurance Runs is that you stay below the upper limit.
Could you give me an example of a date where you have a run with such a wide margin? I can then double check for you
I erased it. But it’s the exact situation you mention. Good to know.
