How to save slam estimated trajectory for evo evaluate about pyslam HOT 2 CLOSED

Were you able to solve this issue?

from pyslam.

Hi,
thanks for your feedback. I think it is very helpful to consider that:

• ORBSLAM was designed and runs under C++ in a multithreading way,
• pyslam was designed and runs under Python, where the GIL does not allow real multithreading (everything runs on a single core)

As stated in the main README
_"You can use this framework as a baseline to play with local features, VO techniques and create your own (proof of concept) VO/SLAM pipeline in python. When you test it, consider that's a work in progress, a development framework written in Python, without any pretense of having state-of-the-art localization accuracy or real-time performances".
pyslam was NOT designed to have real-time performance.

That being said, you can save "current" estimates as explained here
#97 (comment)
A function to save the "final" estimates is currently missing. Work in progress.

As for the EVO format, it's a question of understanding its requirements.

Hope this helps.
Luigi

from pyslam.