-
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
Adding parameter for minimum range for raycasting to clear obstacles #2126
Changes from all commits
096ee33
2aa9f81
c8f31b9
0e697b2
4011e15
bbf332f
703f930
a9f465a
5845024
42b9fb2
34ad359
a735fca
e8e3583
aa5d92c
2762716
c034f9b
7464cb0
867600f
3cfa819
eb0fdc2
c24f128
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 |
---|---|---|
|
@@ -119,8 +119,10 @@ When `plugins` parameter is not overridden, the following default plugins are lo | |
| `<data source>`.inf_is_valid | false | Are infinite returns from laser scanners valid measurements | | ||
| `<data source>`.marking | true | Whether source should mark in costmap | | ||
| `<data source>`.clearing | false | Whether source should raytrace clear in costmap | | ||
| `<data source>`.obstacle_range | 2.5 | Maximum range to mark obstacles in costmap | | ||
| `<data source>`.raytrace_range | 3.0 | Maximum range to raytrace clear obstacles from costmap | | ||
| `<data source>`.obstacle_max_range | 2.5 | Maximum range to mark obstacles in costmap | | ||
| `<data_source>`.obstacle_min_range | 0.0 | Minimum range to mark obstacles in costmap | | ||
| `<data source>`.raytrace_max_range | 3.0 | Maximum range to raytrace clear obstacles from costmap | | ||
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. Please also update the names of these in the We also need a PR in https://github.com/ros-planning/navigation.ros.org to reflect the parameter change in the costmap configuration pages and migration guide that this has changed. 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 found the pages for you for reference
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. Add a new section to the migration page just explaining the parameter name change and that there's a minimum one too - link to this PR and the ROS answers ticket 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. Thanks for the info! I am not able to find any folder named config in the nav2_bringup package. I think I have updated all references to the old parameters (raytrace_range) 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. Sorry, params, https://github.com/ros-planning/navigation2/tree/main/nav2_bringup/bringup/params I use those interchangably. I should probably figure out which is the correct one... Problems for another day 😄 |
||
| `<data_source>`.raytrace_min_range | 0.0 | Minimum range to raytrace clear obstacles from costmap | | ||
|
||
## range_sensor_layer plugin | ||
|
||
|
@@ -168,8 +170,10 @@ When `plugins` parameter is not overridden, the following default plugins are lo | |
| `<data source>`.inf_is_valid | false | Are infinite returns from laser scanners valid measurements | | ||
| `<data source>`.marking | true | Whether source should mark in costmap | | ||
| `<data source>`.clearing | false | Whether source should raytrace clear in costmap | | ||
| `<data source>`.obstacle_range | 2.5 | Maximum range to mark obstacles in costmap | | ||
| `<data source>`.raytrace_range | 3.0 | Maximum range to raytrace clear obstacles from costmap | | ||
| `<data source>`.obstacle_max_range | 2.5 | Maximum range to mark obstacles in costmap | | ||
| `<data_source>`.obstacle_min_range | 0.0 | Minimum range to mark obstacles in costmap | | ||
| `<data source>`.raytrace_max_range | 3.0 | Maximum range to raytrace clear obstacles from costmap | | ||
| `<data_source>`.raytrace_min_range | 0.0 | Minimum range to raytrace clear obstacles from costmap | | ||
|
||
## keepout filter | ||
|
||
|
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.
I thought we were going to do a min for both obstacle and ray trace? Then use the obstacle for the
marking
functions and the raytrace for theclearing
functions - essentially decoupling them the same way the max ranges areThere 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.
I'm not sure I understand what you mean. I created seperate min variables for the obstacle and raytracing. When I created the obstacle_min_range variable, I realized I could rename the obstacle_range to obstacle_max_range to maintain consistency
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.
But it looks like you also removed the other one. There are 2 max range parameters now and should have also 2 analog min parameters
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.
No I have not removed the minimum range parameters