-
Notifications
You must be signed in to change notification settings - Fork 722
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
Unable to open example VI map in maplab - missing vi_map/vi_map_metadata #394
Comments
Old maps, I'm removing those links in the new wiki update. Best solution is to build your own map from EuRoC. If you have everything compiled just source the workspace. And then run the launch file for the maplab node with rovio motion estimation And in parallel rosbag play one of the EuRoC bags from here. After the bag is finished the map should save automatically to |
Hi, thanks for the reply. I tried doing this and the result was an empty /resources directory located in /tmp/euroc. It looks like the maplab node shut down prematurely due to no odometry data received. In the Rviz visualization, the only thing that happens when rosbag is played is the TF is updated. Here's a block of code from the terminal window right when the node shuts down. I tried running with MH_01_easy.bag as well as MH_02_easy.bag. For now I'm going to investigate the launch file to see if any topics aren't lining up.
|
The topics seem fine. What seems to be the problem is that rovioli seems to diverge or have problems as it's just buffering a lot of data internally. You can see from these lines:
Are you running this on an extremely slow PC? Or playing the bag at a high speed? If you set this to true, you can visualize what ROVIO is doing
|
Thanks for the suggestion. I was playing back the rosbag at the normal rate, and it was crashing before receiving its first odometry message. I had some luck playing the rosbag at 0.1x speed, with the console out confirming that the first odometry message had been received, but this didn't carry on as MaplabNode-Synchronizer quickly shutdown everything in the same manner after not receiving an odometry message for 5 seconds. There was a warning message related to the canberra-gtk-module failing to load after the first odometry message was received, perhaps that could be the cause? Having the rovio frame visualization tracker enabled to see the first bits of progress was a nice touch. Fyi, after the MaplabNode-Synchronizer shut everything down, the tracker continued updating. I think this is expected behavior but wanted to share just in case. Regarding my CPU, I am running Ubuntu 20.04 on a virtual machine. It is configured with 12GB of RAM and 8 cores. I ran the process with System Monitor in the background and neither the memory nor the CPUs seemed to be maxing out when the node shuts down, so I don't think its performance-related, but I could be wrong. Which branch are you on? I am using the latest master branch. Thank you for your help!
[buffer continues to build up, then...]
|
So then the problem isn't in maplab per se, but more about your machine setup. Maplab shuts down automatically after a more than 5 second message interruption, that's normal. It seems rovioli, which is the odometry front end, is going very very slowly as it's just buffering stuff. That canberra-gtk-module failing error does not appear for me. Your virtual machine just seems to not be doing its job very well. If you need to run this on Windows can you just use WSL? I've had people running that without too many problems before. |
Ok, good to know. I will try using a different configuration, and report back if it works. Thanks! |
Hello, I am just getting familiar with this repository. I have built maplab and am attempting to load one of the example VI maps into maplab (I have tried downloading vi-maps for CLA floor F, Zurich old town dataset, and EuRoC MH01). However, all of the maps are missing the /vi_map/vi_map_metadata file, and because of this I am encountering a serialization error when running "maplab load". Am I missing a step in the setup?
Error message:
Let me know if I can provide any other information. Thanks!
Some info:
- Operating System: 64 bit, Ubuntu 20.04
- ROS Noetic
The text was updated successfully, but these errors were encountered: