-
Notifications
You must be signed in to change notification settings - Fork 540
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
[REVIEW] Fix brute force KNN distance metric issue #3755
[REVIEW] Fix brute force KNN distance metric issue #3755
Conversation
Concerning MNMG KNN, the change looks good. |
Codecov Report
@@ Coverage Diff @@
## branch-0.20 #3755 +/- ##
==============================================
Coverage ? 85.96%
==============================================
Files ? 225
Lines ? 16986
Branches ? 0
==============================================
Hits ? 14602
Misses ? 2384
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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.
LGTM
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.
LGTM
The brute force KNN default distance metric switched from
L2SqrtExpanded
(or equivalent with FAISS metrics) toL2Unexpanded
recently. I believe that it was a voluntary move to speedup calculations. However some calls to theraft::spatial::knn::brute_force_knn
function in the cuML codebase required specifying a non-default metric. This is the case of distances that are not kept internally by an estimator but are instead provided to the end-user as results. This is also the case of features that specify a specific distance metric for their calculations. Please tell if you notice some other places where a non-default distance metric should have been specified.cc @MatthiasKohl