-
Notifications
You must be signed in to change notification settings - Fork 13
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
Looking for a simple, pure inertial motion estimation #334
Comments
Hi @pauljurczak , yes and no answer -- yes those factors exist but we are not able to share them publicly just yet owing to license restrictions. We are working on getting those available but will still take a bit of time to get that legally sound. Wish we could make them immediately available. In the mean time we are working on integrating xref: |
Thank you for responding. In the meantime, do you know another Julia package or C++ library, which does pure inertial motion estimation? Everything I found so far fuses inertial with visual or other sensing modes. |
Apologies for the slow reply. Perhaps the fastest thing to do is just make a new factor and embed an ODE solution of the classic inertial navigation solution (akin to preintegrating). This will provide similar or better numerical answers with a little computation slowdown -- it will, however, avoid licensing delays. I will build that for common purpose in the next month or two if I can get to it -- should be pretty straight forward. |
Just an update on this, I'm busy adding |
see new on-manifold code for factors This new functionality supercedes previous questions such as: Note that InertialPose3 may well be used in the future, but currently a new variable Next major milestone towards fully consolidated operations will be to complete |
Is there a way to get a simple, pure inertial motion estimation with RoME.jl o rrelated packages? Ultimate accuracy is not required as I want to use it for motion estimation between camera frames capture events, every 50ms with IMU data rate of 250Hz.
The text was updated successfully, but these errors were encountered: