You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Thank you for picking up issue #16. The imu message is now usable within the ROS system. For sensor fusion however, the covariance fields needs to be filled.
Describe the solution you'd like
Preferably fill the covarience fields with the actual uncertainties.
If these are not known, fill them with the squared value of the stdev from the specsheet. (0.0044 for angular and 0.04 for linear acceleration in the novatel case i think).
Describe alternatives you've considered
We now have an 'fix' node inbetween which inserts these values, but this should be fixed at the source.
Additional context
We can offer a pull-request if you like.
The text was updated successfully, but these errors were encountered:
Hi @Timple, thank you for the feedback! I believe this has also been reported as issue #23. We do have this in our queue of items to address and will note there is increased demand for a fix.
Is your feature request related to a problem? Please describe.
Thank you for picking up issue #16. The imu message is now usable within the ROS system. For sensor fusion however, the covariance fields needs to be filled.
Describe the solution you'd like
Preferably fill the covarience fields with the actual uncertainties.
If these are not known, fill them with the squared value of the stdev from the specsheet. (0.0044 for angular and 0.04 for linear acceleration in the novatel case i think).
Describe alternatives you've considered
We now have an 'fix' node inbetween which inserts these values, but this should be fixed at the source.
Additional context
We can offer a pull-request if you like.
The text was updated successfully, but these errors were encountered: