Open josealeixopc opened 3 years ago
Hi! I'm aware of two ways doing that:
Reset
button in Pangolin GUI window. Note: after tracking is LOST, the only way to get position on the current map is relocalization. Elsewhere map will be removed and new created (after using methods described above also)
Hi! I'm aware of two ways doing that:
- Push
Reset
button in Pangolin GUI window.- Set this threshold value to 0 and recompile. After that change, tracking will be resetted after each LOST state
Note: after tracking is LOST, the only way to get position on the current map is relocalization. Elsewhere map will be removed and new created (after using methods described above also)
Thanks! I will be trying this sometime soon and I'll follow up with how I worked it out. :)
Just as an update to this, what @dimaxano suggested does not work as the test is always false if init_retry_thr is set to 0.
curr_frm_.id_ - initializer_.get_initial_frame_id() < camera_->fps_ * init_retry_thr
I just removed this test from the conditional. The question then becomes, how does one ensure the frame_trajectory.txt, mag.msg and other outputs get written with unique names to ensure the map data is not lost upon reset.
Any ideas for this?
I am performing SLAM using the
run_tum_rgbd_slam
command with a custom dataset.OpenVSLAM tracks nicely the trajectory and surroundings up until a fast camera turn. Then, in the visualizer, it says 'LOST' and no further mapping is done.
How can I tell OpenVSLAM to restart tracking when it gets lost? This way, I could manually "stitch" the resulting trajectories.
Thanks!