Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Odometry covariance #40

Closed
ricber opened this issue Mar 31, 2020 · 3 comments
Closed

Odometry covariance #40

ricber opened this issue Mar 31, 2020 · 3 comments

Comments

@ricber
Copy link
Contributor

ricber commented Mar 31, 2020

Hi Koide,
Can I ask you why you didn't fill the covariance matrix of the nav_msgs::Odometry odometry message? I see that your UKF class exposes a method called getCov(). Could I use this method to fill the covariance of the /odom topic?

Thank you.

@koide3
Copy link
Owner

koide3 commented Apr 6, 2020

Hi @ricber ,
Yes, you can retrieve the covariance using getCov(). But, I expect that the estimated covariance doesn't well represent the true uncertainty of the localization result because the UKF doesn't take scan matching errors into account.

@ricber
Copy link
Contributor Author

ricber commented Apr 13, 2020

Ok, thank you!

Also, why did you put to zero the linear twist? Because I see you're estimating linear velocities in the Kalman Filter.

odom.twist.twist.linear.x = 0.0;
odom.twist.twist.linear.y = 0.0;
odom.twist.twist.angular.z = 0.0;

@koide3
Copy link
Owner

koide3 commented May 7, 2020

Yeah, of course, we can put the estimated velocity in the odom message. The reason I didn't is that the velocity was not necessary in my application, and I was lazy to check the velocity output coordinate...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants