KNN Clustering #271
Merged
KNN Clustering #271
+365
−10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am reopening this PR. I've manually after reset the previous commit history. Looking at the commits, there were too many changes bundled together that I was not able to cherry pick across commits.
In terms of changes, I've simplified the synthetic dataset for unittests and incorporated some of the feedback such as only using the classifier for the unlabeled data and using more informative error messages.
The comments that were ignored were largely centered around unittests that check if a key exists in the AnnData object. These were ignored since the keys are only generated after calling the knn_clustering method and hence could not be checked somewhere else.