Laser Scanner #11
Merged
Laser Scanner #11
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
…ublish inside laser.render
…ere SimDepthCamera and other classes are stored). Does not allow for ROS or PCL, so implemented similar to SimDepthCamera where return DepthImage that gets converted to a pointcloud. See prior commit to have SimLaserScanner::render return a pointcloud
…readme and add mp4, add stanford dragon
marip8
approved these changes
Sep 14, 2020
|
Thanks for the contribution @cbw36 |
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.
Add the SimLaserScanner class, which models a laser scanner and simulates realistic data for the laser, including a pointcloud of the scanner data and the distances to points in the pointcloud. This is useful when we want to simulate scan data for a laser sensor without using a physics simulator like Gazebo. Include example node and a unit test.
Issues: The angular resolution of a scan is not equal to its inputted value. It is roughly 66% larger. Need to update the code to output the desired angular resolution and update the unit test to verify this.