-
Notifications
You must be signed in to change notification settings - Fork 640
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
Dashing fixes #307
Dashing fixes #307
Conversation
This lets us get rid of calls to 'new', and is the more modern way to store unique pointers. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
This really puts it back to what it used to be, which seems to fix a bug where the scans would be intermittent. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Since we are doing a std::move of the scan, we can't access the stamp afterwards to get the stamp. Store the stamp before we std::move it so we can use it later. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Without this, the published pointclouds get slower and slower. Just recalculate the row_step every time, which isn't really expensive anyway. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
This has side-effects for the class, so we can't just eliminate it. Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette - Everything in this MR looks fine. Do you know if it solves the problem that @pjreed brought up in #298? |
I believe it should, but a confirmation would be great. |
Yep, I just tested it out and it looks much better now. Thanks! |
Fantastic, thanks for testing! |
This PR has a bunch of fixes that I needed to make the current Dashing actually work with my VLP-16. With all of these in place, I'm now able to make this produce pointclouds as before. @JWhitleyAStuff please take a look, thanks!