Trajectory resolution should be a timestep in seconds, not number of points
Closed this issue · 0 comments
sea-bass commented
Right now, the trajectory_res
parameter in the KTOpt planner defaults to 101 points for the trajectory, but actually it should ve a time resolution (e.g. 0.01 seconds) and then dependent on the trajectory length instead.