-
Notifications
You must be signed in to change notification settings - Fork 236
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
Why not ORB? #55
Comments
Not sure why @gaoxiang12 decided this way. My guess would be that Shi Tomasi corners are slightly more repeatable compared to FAST corners. For FAST you can get a lot of features and it's super efficient. Since we don't use it for tracking, we neither need a lot of them, nor do we need to extract them in every frame (only keyframes), so performance and count is not of upmost importance. Repeatibility o.t.o.h. is more important for loop closures. Otherwise, the descriptor is like ORB as you have noticed, so overall there is probably only very little difference. |
Thank you so much for your reply. That solved my question. |
I don't know. It's pretty much the same, but Xiang refactored the code a little bit, so there might be slight changes compare to DSO other than just the point selection. |
Thank you for your remarkable work.
I just have a question:
I noticed LDSO detect corners by shi-tomasi.
I just wondering why don't you use ORB features like orb-slam2?
Because when calculating the descriptor, LDSO also use the ORB descriptors.
Thank you so much for your reply!
The text was updated successfully, but these errors were encountered: