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

failed static init #453

Open
Jiangjiacheng-scau opened this issue Jun 18, 2024 · 2 comments
Open

failed static init #453

Jiangjiacheng-scau opened this issue Jun 18, 2024 · 2 comments
Labels
user-platform User has trouble running on their own platform.

Comments

@Jiangjiacheng-scau
Copy link

[init]: failed static init: no accel jerk detected, platform moving too much

how to solve it?

@precyon
Copy link

precyon commented Jun 19, 2024

On what datastet? Or are you using your own?

If you are using your own, what does the start of the dataset look like? The error seems to suggest that the setup is already moving at the start?

You could:

  1. Post the full log for the community to look at and better understand what's going on. You could set the verbosity to DEBUG.
  2. Look at the disparities and IMU values/jerk at the start tweak the init_* options in estimator_config.yaml

@goldbattle goldbattle added the user-platform User has trouble running on their own platform. label Aug 12, 2024
@goldbattle
Copy link
Member

hi @Jiangjiacheng-scau , here are some steps to get your static initialization tuned. The values will likely be specific to your IMU and robotic platform's vibrations.

  • Start the device start at static and set the config init_imu_thresh to a very large number
  • You can then take a look at the debug messages to see what the current value is
  • Pickup the device and look at how the numbers have changed
  • Set the init_imu_thresh to a value which is a bit larger then the static amount (prevent false positives)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user-platform User has trouble running on their own platform.
Projects
None yet
Development

No branches or pull requests

3 participants