-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
RPP Dexory tweaks #4140
RPP Dexory tweaks #4140
Changes from all commits
e6eef04
2aa762a
058397e
4ce993b
39882d4
994351e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -90,6 +90,7 @@ Note: The maximum allowed time to collision is thresholded by the lookahead poin | |
| `rotate_to_heading_min_angle` | The difference in the path orientation and the starting robot orientation to trigger a rotate in place, if `use_rotate_to_heading` is enabled. | | ||
| `max_angular_accel` | Maximum allowable angular acceleration while rotating to heading, if enabled | | ||
| `max_robot_pose_search_dist` | Maximum integrated distance along the path to bound the search for the closest pose to the robot. This is set by default to the maximum costmap extent, so it shouldn't be set manually unless there are loops within the local costmap. | | ||
| `interpolate_curvature_after_goal` | Needs use_fixed_curvature_lookahead to be true. Interpolate a carrot after the goal dedicated to the curvate calculation (to avoid oscilaltions at the end of the path) | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Question for @doisyg @james-ward : Do you feel there's any reason to make this a parameterization or always be in play? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it should always be in play - for two reasons. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @doisyg if you agree, you can remove the param and make it the always-on behavior There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On that one, I would be a bit conservative and keep it as a parameter for a while, then changing it later to default true, and finally then removing it. A bit like with the former There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @james-ward can you give this a whirl and let us know what you think? He's testing this on straight-line paths in warehouses, so they don't end on curves (they use other algorithms for free space controlling). If so, we can simplify this a bit |
||
|
||
Example fully-described XML with default parameter values: | ||
|
||
|
@@ -137,6 +138,7 @@ controller_server: | |
rotate_to_heading_min_angle: 0.785 | ||
max_angular_accel: 3.2 | ||
max_robot_pose_search_dist: 10.0 | ||
interpolate_curvature_after_goal: false | ||
cost_scaling_dist: 0.3 | ||
cost_scaling_gain: 1.0 | ||
inflation_cost_scaling_factor: 3.0 | ||
|
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.
TODO Me: remove AMCL dep and use
angles
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.
oh yeah forgot about than one and your eyes when you saw that we are still using the good old amcl angles utils