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

Some question about "Bad IMU Rate". #654

Closed
liaozihang opened this issue Dec 1, 2023 · 3 comments
Closed

Some question about "Bad IMU Rate". #654

liaozihang opened this issue Dec 1, 2023 · 3 comments
Labels
question Theory or implementation question

Comments

@liaozihang
Copy link

In the wiki, there is a mention about bad IMU timestamps ,
I have a question about the impact of bad timestamps.

Can anyone explain me,a big question is what is the impact of a bad imu rate on vio, which seems to have no relevant explanation found on the wiki or issue.

I would be thankful for any answer.

Thanks

@goldbattle goldbattle added the question Theory or implementation question label Dec 31, 2023
@goldbattle
Copy link
Collaborator

I think this all depends on the noise and the integration methods used.
You want to have a reasonable rate ~100-500Hz IMU with low noise.

The problem with "bad timestamps" is that they are inconsistent, i.e. it is unknow what the true measurement timestamp of each IMU reading is. In this case, I believe basically all VIO / inertial method will fail.

@liaozihang
Copy link
Author

I think this all depends on the noise and the integration methods used. You want to have a reasonable rate ~100-500Hz IMU with low noise.

The problem with "bad timestamps" is that they are inconsistent, i.e. it is unknow what the true measurement timestamp of each IMU reading is. In this case, I believe basically all VIO / inertial method will fail.

Thanks for the reply !

Based on your reply, my understanding is that "a good imu driver output should have stable time intervals.If the actual output imu time intervals appear to be unstable, there may be a problem with the driver or the sensor itself (although based on the clock mark a time, it may not coincide with the actual time it happens), which is not good for any VIO method"

Is that a correct understanding?
Thanks

@goldbattle
Copy link
Collaborator

Correct!

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

No branches or pull requests

2 participants