I've found a bug in lasercspace driver.
The problem is that it shortens even those ranges that are out of the maximun range of the original scan, but they are not obstacles to enlarge.
This situation can be shown by using this driver on an open field. The result is not the same as the original scan as spected (because there are no obstacles to enlarge). All the ranges are shortened instead, giving a wrong laser scan.
A simple check over the original scan range (is it really an obstacle or it is out of range) seems to be enough to avoid this problem.
Log in to post a comment.