Revision history [back]

you can try to set the parameter inf_is_valid: false . in this way the local costmap (or global) will not treat scans with "inf" values.

this is a quick fix, and you may have problems with not clearing the costmaps in front of the robot if your sensor output "inf" for scans farther than max_range, for example. in that case you might want to use a filter to correct that kind of measurements from your data as in here.

you can try to set the parameter parameter inf_is_valid: false . in this way the local costmap (or global) will not treat scans with "inf" values.

this is a quick fix, and you may have problems with not clearing the costmaps in front of the robot if your sensor output "inf" for scans farther than max_range, for example. in that case you might want to use a filter to correct that kind of measurements from your data as in here.

you can try to set the parameter inf_is_valid: false . in this way the local costmap (or global) will not treat scans with "inf" values.

this is a quick fix, and you may have problems with not clearing the costmaps in front of the robot if your sensor output outputs "inf" for scans farther than max_range, for example. in that case you might want to use a filter to correct that kind of measurements from your data as in here.