Question 1 -
Is there any reason why intervals.icu structured workout shows 30-minute intervals when hovering over the structured graph of this workout when the planned workout is 5 km distance. I mean it doesn’t make any sense to convert that 5 km to 30 mins because every athlete will take his or her own time. So I am not sure what is happening here. Please help.
Now this second screenshot is when the workout is performed as planned on the Garmin watch and synced back to intervals.icu.
Question 2 -
Everything looks good. However, I am not able to understand why this 5 km planned interval is being split into 1.6 km blocks. Ideally, if the planned workout is for 5 km I would expect 5 KM intervals to appear there in the intervals on the platform so that it is easy to recognize and then analyze as well. Here yes I know when I take the average of these 4 I have highlighted in the second screenshot I can get the value for 5 km but again that’s the average and not a single 5 km data at once. Please help.
Is there any specific setting that I need to do to get this kind of interval at once rather than broken into a mile distance?
Thanks, Gerald for the response. So if the workout is planned based on duration then it will convert any distance-related segments planned to duration.
But this might cause issues in syncing the same workout to be performed by different people I feel.
Intervals.icu needs duration to calculate training load. So if you specify a step using distance and HR it assumes a pace in the middle of Z2 to calculate the duration. The sport settings for the currently selected athlete are used.
If you also specify pace then that pace is used to calculate duration even if the workout is done by HR. Example:
Why it happens?
I’m not 100% sure of the exact reason. The algorithm does like smooth intervals, and power is easier than HR and pace. There are a few topics where David has answered the queries:.
Does your original FIT file has laps recorded?
It’s interesting why instead of 1km splits, there is 1.6km splits (incidently 1mile = 1.6km)
If you’re using Intervals.icu built in LAPS detection, maybe that’s why it’s using 1.6km. Not entirely sure, you could change it to also ask intervals to “always use laps”
I think it’s not intervalls.icu issue. Seems Garmin has put laps but it has segregated that into each mile mark and there itself it is coming likewise.