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

RotateRecovery parameter names differ from TrajectoryPlannerROS parameter names #706

Closed
MarcoStb1993 opened this issue Apr 13, 2018 · 2 comments

Comments

@MarcoStb1993
Copy link

The parameters specified in TrajectoryPlannerROS that according to the documentation will be accepted by RotateRecovery have different than those of RotateRecovery which leads to RotateRecovery using the default values instead of the ones specified by the user in base_local_planners.yaml.
http://wiki.ros.org/rotate_recovery
(acc_lim_th, max_rotational_vel, min_in_place_rotational_vel )
http://wiki.ros.org/base_local_planner?distro=kinetic
(acc_lim_theta, max_vel_theta, min_in_place_vel_theta)

@mikeferguson
Copy link
Contributor

Adding melodic milestone to this -- since I'd like to try to address all of these random parameter issues we've found over the years in this new LTS.

@mikeferguson mikeferguson added this to the Melodic Release (1.16) milestone May 14, 2018
DLu added a commit to DLu/navigation that referenced this issue May 15, 2018
@mikeferguson
Copy link
Contributor

Is in PR -- closing so I can keep track of what we have to actually still do before release!

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

No branches or pull requests

2 participants