Hi, if I have a workout which has both time and distance based steps, then in the resulted activity the workout-target graph is (wrongly) based on time only. See, for example, Intervals.icu
First two workout steps are distance based (for practical reasons: to pass a certain road-junction with traffic lights before starting time based intervals
then comes the time-based intervals.
What is wrong: target intensity chart is displayed on time-basis in the HR chart
Expected behavior: Intervals.icu shall draw the target intensity graph conforming to the workout description. For the first two steps it shall follow the distance then switch to time basis. Moreover, if the step is terminated with lap-button-press, then the intensity-target graph shall follow that, too That is: follow the marked lap boundary in the activity file.
Intervals.icu “needs” a time based graph to calculate time in zones, training load etc… So it converts distance based steps into time using the pace for the step (if specified), a speed derived from your pace zones and threshold pace for the sport or 30 km/h for rides. It would be very tricky to adjust this using a paired activity.
Why can it not convert using the actually recorded time from whithin the paired activity? Why does it converts distance based steps into time using some hypothetic pace for the step which is guaranteed(!!) to differ from the actual time recorded in the activity, while it could use the real, measured and recorded elapsed time of the distance based step? Could it use the actual, elapsed time? It is right there, inside the recording.
It is clearly visible, that the workout-target graph is totally out of sync, as the first two steps of the workout are distance based and the 2nd one ends in a “press lap”.
Nevertheless, the actual elapsed time at the moment of actually starting the intervals is known to intervals.icu in multiple way:
any workout step is necessarily ends in a lap-marker, at least for Garmin devices. Hence, the beginning and end of any workout-step are ALWAYS at lap markers. The time-based-workout-target-chart do not have to rely on hypothetical (and naturally always wrong) calculated speed/pace to derive a fake (and wrong) time duration for the graph-segment. Intervals.icu KNOWS exactly the elapsed time-duration, it is just a matter of design decision to use the measured elapsed time as the basis for the workout-target graph
the proof for the above claim is marked up at the lower left corner of the picture: you do correctly indicate the actual, recorded time-elapsed-since-activity-start at the end of the workout interval-step…
the problem is that the rendering logic for the workout target-intensity chart does not use the actual elapsed time, but the hypothetical (and always wrong!!) calculated time from the workout description – even for distance based steps. The bugfix would be is to use the actually recorded elapsed time for
the actual elapsed time at all the distance based workout-steps (use either the recorded timestamp corresponding to the prescribed distance)
or the timestamps of the lap-end markers for all the “press-lap” marked workout steps.
