-
Notifications
You must be signed in to change notification settings - Fork 17
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
Change default AMCL params #244
Conversation
This is a minor patch to make default params match the navigation AMCL values in ROS 1 and ROS 2. This is convenient for users migrating from the AMCL node provided by the navigation stack, if they define a parameter file that does not mention all parameters, they can expect the behavior to match that of the navigation node. Signed-off-by: Nahuel Espinosa <nespinosa@ekumenlabs.com>
Signed-off-by: Nahuel Espinosa <nespinosa@ekumenlabs.com>
It looks like some tests in ROS Noetic depended on some of those defaults:
|
It seems that this parameter can't be changed after initialization. Signed-off-by: Nahuel Espinosa <nespinosa@ekumenlabs.com>
@hidmic It seems that if we set |
@hidmic @serraramiro1 @glpuga @ivanpauno Based on our discussion, I will create a compatibility mode ticket. While we work on that, I think it doesn't hurt to land this. |
Agreed. |
Signed-off-by: Nahuel Espinosa <nespinosa@ekumenlabs.com>
🚀 LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM too
Proposed changes
This is a minor patch to make default params match the navigation AMCL values in ROS 1 and ROS 2. This is convenient for users migrating from the AMCL node provided by the navigation stack, if they define a parameter file that does not mention all parameters, they can expect the behavior to match that of the navigation AMCL node.
Type of change
Checklist