vel_start
and vel_end
in computePathParametrization()
handled differently
#255
Labels
vel_start
and vel_end
in computePathParametrization()
handled differently
#255
vel_start
is the path velocity squared at s=0vel_end
is the actual path velocity at s=1This is not only not documented, but also very misleading.
The text was updated successfully, but these errors were encountered: