-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Improving the disparity filter interface #303
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest to divide this method to:
createDisparityWLSFilter(left_matcher)
// and
setupRightMatcher(left_matcher) // or 'createRightMatcher'|
Looks good, thank you! |
Now the filter natively supports StereoBM and StereoSGBM with no parameter tuning required. Also, now user won't need to set the ROI and the right matcher parameters manually, it is all done in the respective convenience factory method based on the left matcher instance. Tutorial was added to clarify the provided example of use.
f8889a8 to
6a0545e
Compare
|
@mshabunin I replaced the code in the tutorial with a link to GitHub and squashed all the commits |
|
👍 |
|
Is it possible that this change introduced this error when building: |
|
@Arqu , please use latest master branch version of opencv repository when building latest version of opencv_contrib. This mode has been added recently: |
|
Thanks, I'll rebuild it when I get some spare time, I've managed to skip the module in the build process for now. I probably didn't use the latest source as I've used the 3.0.0 branch instead of master. |
Several changes to minimize the need for explicit parameter tuning when using with either StereoBM or StereoSGBM and to make the filter more easy to use in general.