Closed rayferric closed 20 hours ago
Please ask this as a question on robotics.stackexchange.com. When you do, please include a sample message from every sensor input. While there's always a first time, I have yet to see a case of NaN values that weren't the result of bad inputs or misconfiguration.
Also, the community is moving towards fuse, hence the eventual deprecation of this package.
Describe the bug
After #751 was merged, the Unscented Kalman Filter starts producing NaN values within about 5 seconds when the simulation is paused, and no new sensor readings are being published.
Once this happens, this message will appear:
https://github.com/cra-ros-pkg/robot_localization/blob/ef0a27352962c56a970f2bbeb8687313b9e54a9a/src/ros_filter.cpp#L2157-L2163
...and then the terminal will be flooded with TF NaN errors.
This issue does not occur when using the Extended Kalman Filter.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The UKF should never produce NaN values.
Desktop (please complete the following information):
robot_localization
Package Version:jazzy-devel
@ 0cd2e468493325754bd1e7add7384df75d9f1658 Added subscription to stamped topicAdditional context
We are currently using the EKF as a workaround. Below is the UKF configuration we used on Humble without issues:
Regarding Deprecation
In the issue template I also noticed the comment mentioning that the robot_localization package will soon be deprecated. This package is widely used and popular in the ROS community, so I have trouble understanding why it is being deprecated? Is there a planned replacement?