Is it really necessary to include negative pace values on the secondary axis of the Lactate Threshold charts? I thought 0 would be a more sensible minimum value than -9:40, and it isn't as if the blue line (for pace) must overlap the red line in a certain manner.
It seems to be a static axis. I have exactly the same axis values, even though my LT pace is very different from yours.
I guess that makes it even worse. If it was a dynamic axis, we could at least assume that something in our pace is confusing the automatic scaling algorithm in a way which did not show up during Garmin's testing . But if it is a static axis, Garmin should have seen it if they had done any testing.
By the way, even though the axis shows pace values, it seems to be a linear speed axis with fixed intervals of 7,2 km/h between each positive value on the axis. The pace values have been added afterwards. This is the reason for the uneven intervals between the pace values on the axis.
(For the 0 and negative value, this doesn't hold up. 0 is 0 km/h and should have been shown as infinite min/km. And the negative pace doesn't fit a negative 7,2 km/h speed.)
