We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While working on issue #2899 i noticed the TODO about moving kornia.feature.sold2.WunschLineMatcher to kornia.feature.matching.
Should I go ahead and create a pull request for this change?
The text was updated successfully, but these errors were encountered:
I don't know about this matcher, but having another api “exposed” is always good -- cc @edgarriba @ducha-aiki
Sorry, something went wrong.
sounds good to me
WunschLineMatcher
kornia.feature.matching
No branches or pull requests
While working on issue #2899 i noticed the TODO about moving kornia.feature.sold2.WunschLineMatcher to kornia.feature.matching.
Should I go ahead and create a pull request for this change?
The text was updated successfully, but these errors were encountered: