-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Python tutorial that uses ORB feature from OpenCV to initialize RGBDOdometry #26
Comments
Another idea is providing python example code using OpenCV python interface. We have plan to include OpenCV python + Open3D OdometryRGBD example for #51. In this manner, Open3D does not need to be directly linked to heavy OpenCV. |
Working on this issue. But there are few concerns
|
|
Actually earlier we had a discussion with the OpenCV core development team, and the main recommendation I gave them was to put OpenCV into Anaconda. (Not in the forge. Forge is like the community build support.) I think they will be working on it. So hopefully in the future, cv will be included natively in Anaconda. We just test this environment. Btw: Anaconda is also the easiest way for setting up TensorFlow. I think everything is converging into it. It won't be a bad choice if we just stick with it. |
Some technical issue. Please check current implementation of 5pt algorithm. (Let me know if you have not privileged to see the code). Checkout It also depends on complex OpenCV function. To name a few |
Wow, for real! Where did you get these equations? An alternative approach is to replace the 5-pt algorithm with RANSAC. We do RANSAC on ORB features, and compute transformation based on points converted from depth pixels. Does this make sense? |
I decided to go with OpenCV python binding as it provides ORB feature + 5pt algorithm. This is handy and we don't have to merge complex 5pt algorithm in Open3D. I finished writing a code for building fragment. There will be PR regarding this module soon. |
This issue handled with #74 |
This issues is derived from #24. Lower priority.
Need not to be done before the first launch.
The text was updated successfully, but these errors were encountered: