Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vel_start and vel_end in computePathParametrization() handled differently #255

Open
mskripnik opened this issue Oct 9, 2024 · 1 comment

Comments

@mskripnik
Copy link

PathParametrizationAlgorithm::computePathParametrization(value_type vel_start, value_type vel_end)

vel_start is the path velocity squared at s=0
vel_end is the actual path velocity at s=1

This is not only not documented, but also very misleading.

@mishrasubhransu
Copy link

Yes. I had to change m_data.parametrization(0) = vel_start; to m_data.parametrization(0) = vel_start * vel_start; to make both of them path velocity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants