You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the docker image. It's been very helpful.
Do you know if this image will work on newer versions of Ubuntu? Like Ubuntu 20.04 or 21.04?
Also, I have been using the CPU version of your docker on Ubuntu 18.04. I noticed when I run the orb slam algorithm, the view of the drone's camera is kind of laggy (sometimes the video frames stop, and then skips half a second or so). I didn't think this was an issue, until I noticed that sometimes the trajectory is not recorded properly by orb slam. When I inspect the outputted trajectory file, I can see that large sections of timestamps are missing. When I plot the trajectory, I see missing gaps in the trajectory corresponding to those missing timestamps. There are no errors that pop up on the terminal while running the algorithm. Did you notice anything like this when running it? I think this problem might be caused by my computer's CPU not being strong enough to run the algorithm properly.
The text was updated successfully, but these errors were encountered:
Docker doesnt require your system to be ubuntu 20. You can run a docker based on ubuntu 18 while your system ubuntu is 20.
However I am planning to update it to ubuntu 20 so that people with ros2 and noetic can work on it.
Hi,
Thanks for the docker image. It's been very helpful.
Do you know if this image will work on newer versions of Ubuntu? Like Ubuntu 20.04 or 21.04?
Also, I have been using the CPU version of your docker on Ubuntu 18.04. I noticed when I run the orb slam algorithm, the view of the drone's camera is kind of laggy (sometimes the video frames stop, and then skips half a second or so). I didn't think this was an issue, until I noticed that sometimes the trajectory is not recorded properly by orb slam. When I inspect the outputted trajectory file, I can see that large sections of timestamps are missing. When I plot the trajectory, I see missing gaps in the trajectory corresponding to those missing timestamps. There are no errors that pop up on the terminal while running the algorithm. Did you notice anything like this when running it? I think this problem might be caused by my computer's CPU not being strong enough to run the algorithm properly.
The text was updated successfully, but these errors were encountered: