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

lost tracking after initialization 15 sec? #64

Open
amranov opened this issue Dec 21, 2018 · 1 comment
Open

lost tracking after initialization 15 sec? #64

amranov opened this issue Dec 21, 2018 · 1 comment

Comments

@amranov
Copy link

amranov commented Dec 21, 2018

Hi , first i would like to thank you for this great job
i tried to run the code USING loirorVIsensor but the tracking is lost after initialization , no new KF
Also the scale value are bit weird (negative values)
IMU and CAMERA i'm using are well synchronized , any succession to solve this issue ?
Time: 15.2993, sstar: 0.710862, s: 0.495204
Local Mapping STOP
-----------here is the last KF in vScaleGravityKF------------
dt = 0.000, this vs next time: 1545394068.362 vs 1545394068.362

... Map scale updated ...

... Map NavState updated ...

Local Mapping RELEASE

dt = -0.038, this frame vs last imu time: 1545394085.081 vs 1545394085.043
dt = -0.038, this frame vs last imu time: 1545394085.081 vs 1545394085.043
CHOLMOD warning: L not positive definite

@CQnancy
Copy link

CQnancy commented Aug 8, 2023

Hi , first i would like to thank you for this great job i tried to run the code USING loirorVIsensor but the tracking is lost after initialization , no new KF Also the scale value are bit weird (negative values) IMU and CAMERA i'm using are well synchronized , any succession to solve this issue ? Time: 15.2993, sstar: 0.710862, s: 0.495204 Local Mapping STOP -----------here is the last KF in vScaleGravityKF------------ dt = 0.000, this vs next time: 1545394068.362 vs 1545394068.362

... Map scale updated ...

... Map NavState updated ...

Local Mapping RELEASE

dt = -0.038, this frame vs last imu time: 1545394085.081 vs 1545394085.043 dt = -0.038, this frame vs last imu time: 1545394085.081 vs 1545394085.043 CHOLMOD warning: L not positive definite

Have you resolved the issue?

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