The min_valid_distance parameter #9
Open
Conversation
This file contains hidden or 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
WubinXia
force-pushed
the
master
branch
3 times, most recently
from
8548b73 to
934b402
Compare
chrisl8
pushed a commit
to chrisl8/rplidar_ros
that referenced
this pull request
Aug 25, 2020
* Update ROS 2 parameters and use node's clock instance Signed-off-by: Hunter L. Allen <hunter.allen@ghostrobotics.io> * Fix scan_mode listing output Signed-off-by: Hunter L. Allen <hunter.allen@ghostrobotics.io> * Stop motors and exit when set_scan_mode() call fails Signed-off-by: Hunter L. Allen <hunter.allen@ghostrobotics.io>
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.
The introduced parameter might be handy for cases when there are obstacles close to the lidar that move along with it.
min_valid_distancecan be set to a small positive value so that the presence of the obstacles does not pollute the readings.