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.
I adapted open_karto to work with the infinite readings from the Robopeak lidar driver on an Odroid XU4 (Exynos5422 Cortex™-A15 2Ghz and Cortex™-A7 Octa core CPUs, probably an ARM issue). The problem is that on the Odroid this infinite readings mess up the scan matching.
Without the patch:
With the patch:
On a generic pc (Intel Core i5) this doesn't happen:
Without patch:
Is it right that the scan matcher doesn't consider min and max range?
If you need more information ask and I will be happy to provide them.
I can provide also a rosbag file with laserscan data and odometry to reproduce the problem if you want.