-
Notifications
You must be signed in to change notification settings - Fork 19
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
Added approximate KNN backend #791
Conversation
for more information, see https://pre-commit.ci
@Zethson what is your stance on importing private variables from scanpy, as we are doing elsewhere too? I remember in the past you've added a fix of a previously imported, external private variable by defining the required variable ourselves. I lean towards doing this here too |
Yeah, we should try to avoid importing internals so I think that's a good option. |
Thank you so much @nicolassidoux ! But this is from our side so far a lacking suite of tests (as we as of now have been closely eyeing scanpy), and hence no test suite at this point to add to here :) |
Co-authored-by: Eljas Roellin <[email protected]>
ready for me to take a quick look again or are you still doing stuff? :) |
Hi @eroell, ready for re-review! |
Added the intersphinx mappings for pynndescent, and linked the reference to the scanpy knn tutorial with a readable text; Also added a more wordy description on the arguments, more wordy than scanpy... |
@eroell |
great - this is a nice addition, thank you @nicolassidoux ! |
I had to
from scanpy.neighbors._types import KnnTransformerLike, _KnownTransformer
to make transformer argument ofneighbors()
consistent with scanpy. But _types is protected...