Skip to content

vel_start and vel_end in computePathParametrization() handled differently #255

@mskripnik

Description

@mskripnik
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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions