Increase min max obstacle height for scan topic #157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adjust the values so that it is possible to mount another laserscan source anywhere on the turtlebot. In our setup we use, besides the kinect, a laserscanner which scans the field behind the turtlebot. This scanner is placed above the kinect and publishes data with a higher value than the max_obstacle height, in this case it is not possible to use the data for navigation and localization.
|
If you're adding another sensor would it not make sense to add another input for the costmap? @ros-pull-request-builder retest this please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjust the values so that it is possible to mount another laserscan source anywhere on the turtlebot.
In our setup we use, besides the kinect, a laserscanner which scans the field behind the turtlebot.
This scanner is placed above the kinect and publishes data with a higher value than the max_obstacle height,
in this case it is not possible to use the data for navigation and localization.
As you can see in the picture, the old values (red) are overly restrictive and there shouldn't be any harm in adjusting them to the new values (green).
