-
Notifications
You must be signed in to change notification settings - Fork 56
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
Examples/fix knn #903
Examples/fix knn #903
Conversation
Codecov Report
@@ Coverage Diff @@
## master #903 +/- ##
==========================================
- Coverage 95.49% 91.07% -4.43%
==========================================
Files 64 64
Lines 9793 9793
==========================================
- Hits 9352 8919 -433
- Misses 441 874 +433
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
NOTE: the accuracy bug is still open, however this PR fixes the issue that the classifier in the example was not called previously (as noted in the first comment) see #914 |
Description
The knn demo stopped working at some unspecified time.
Here's a version that runs. However, it returns a different accuracy depending on the number of MPI processes I run it on:
~~Help would be great @mtar @coquelin77 @Inzlinger ~~
EDIT Feb 8.: The unstable accuracy is due to a
getitem
call withinKNearestNeighbours.predict()
, where the indices are distributed and not ordered, see #914. Since it's not a specificknn
problem, this PR is ready for review.Issue/s resolved: #
Changes proposed:
Type of change
Memory requirements
N.A.
Performance
N.A.
Due Diligence
Does this change modify the behaviour of other functions? If so, which?
no
skip ci