-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add native Python consensus clustering process #839
Conversation
…constructor of PixieConsensusCluster
…and not just final
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.
It looks good! Just a couple of small things.
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'll defer to @cliu72 on this one
This looks good to me. Did you have any additional questions about testing? I didn't look at it that hard but it looks fine to me |
Nope, everything else looks straightforward. |
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.
Looks good
Will wait to merge this in until #823 is resolved |
Pixel subsetting merging complete and tested. |
What is the purpose of this PR?
Closes #831. Closes #852. Consensus clustering needs to be ported over to Python as part of the efforts to remove all R code.
How did you implement your changes
See #831. I decided not to use a fixture for
test_pixel_consensus_cluster
andtest_cell_consensus_cluster
since those functions already generate test datasets. When we port the entire pipeline over to OOP, then we'll think about creating test fixtures.