Basic Info

Description of contribution in a few bullet points

Pretty much what the title says. I accidentally came across this bug while running AMCL against a dataset with LaserScan messages that happened to bear NaNs every now and then.

Here I apply the same NaN check that the other sensor models use, for consistency.

Description of documentation updates required from your changes

None.

Future work that may be required in bullet points

None.

For Maintainers:

• Check that any new parameters added are updated in navigation.ros.org
• Check that any significant change is added to the migration guide
• Check that any new features OR changes to existing behaviors are reflected in the tuning guide
• Check that any new functions have Doxygen added
• Check that any new features have test coverage
• Check that any new plugins is added to the plugins page
• If BT Node, Additionally: add to BT's XML index of nodes for groot, BT package's readme table, and BT library lists