-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Benchmarking ORB_SLAM vs ORB_SLAM2 #11
Comments
Could you please provide a sequence where you notice a difference in performance so that I can analyse it? Provide also the settings for ORB-SLAM and ORB-SLAM2. |
haven't tested for fps but i also had less good initializations with ORB_SLAM2 compared to ORB_SLAM. furthermore I've noticed that ORB_SLAM2 had more problems with almost pure rotations than ORB_SLAM. though changing to the old keypoints computation in line 1054 as you @raulmur suggested did help. i will provide a sequence for the significant parts soon but i can upload the full files too. the biggest is 17 GB (>10 min. with 30 fps in VGA). what would be the best free cloud place to upload such big files? |
@cipri-tom that's true, totally forgot about this one. thx. will upload soon. |
@raulmur [1] shortStreet.bag |
Thanks a lot @gitunit. This is really useful. I will take some time to look at this particular case and let you know my conclusions. |
Hi @raulmur ,
I ran a few quick comparisons with your ROS example for ORB_SLAM2 in monocular mode and I can see a significant difference in performance between the previous version and this one. More specifically, the rate at which ORB_SLAM2 is able to process incoming frames on the same platform (now 3-4 vs previously 8-9 frames per second) is significantly lower. Also, ORB_SLAM2 refuses to initialize on the same dataset that ORB_SLAM is perfectly happy to initialize on.
What are your thoughts on this? What do you think are the major causes of this change?
Thanks a lot!
Marc
The text was updated successfully, but these errors were encountered: