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

SVO 2.0 as odom feedback #65

Open
mrsp opened this issue May 14, 2018 · 1 comment
Open

SVO 2.0 as odom feedback #65

mrsp opened this issue May 14, 2018 · 1 comment

Comments

@mrsp
Copy link

mrsp commented May 14, 2018

Hi

Digging up a bit in your code, your feedback is based on an instance of "state_predictor", have you tried using your SVO 2.0 as your odometry feedback?

Thx in advance

@mfaessle
Copy link
Contributor

The state_predictor is only responsible to compensate for latencies of the state estimate and the resulting control command. When the state estimate arrives at the controller, it already has a certain age from which it is predicted forward until the current time. Similarly, we can consider delays of the resulting control command, e.g. when using a wireless link to send commands, by integrating the state estimate forward based on previously applied control commands.

The origin of the state estimate does not matter as long as it is passed to the controller as a nav_msgs/Odometry message. And of course we have used SVO 2.0 together with the Multi Sensor Fusion framework (https://github.com/ethz-asl/ethzasl_msf) to get a state estimate. This is how all our basic demos work, e.g. https://youtu.be/7-kPiWaFYAc

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