-
Notifications
You must be signed in to change notification settings - Fork 185
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
Make it possible to find the closest cluster/node for new data #208
Comments
I could see that being very useful. Thanks for the suggestion. If you would like to take a stab at the implementation, that would be great for everyone. |
Here is something functional. With the addition of some extra internal data structures to track cubes->nodes this could probably be made a bit cleaner.
|
Looks great! would you like to submit a PR? |
This would indeed be very useful. I was wondering if this has been implemented or shall I just use the code snippet shared above? |
Most of it has been merged already except for one outstanding PR, use the code from that branch. Sent from my Galaxy
-------- Original message --------From: ahassaine ***@***.***> Date: 16/11/2021 11:15 (GMT+00:00) To: scikit-tda/kepler-mapper ***@***.***> Cc: pulquero ***@***.***>, Author ***@***.***> Subject: Re: [scikit-tda/kepler-mapper] Make it possible to find the closest cluster/node for new data (#208)
This would indeed be very useful. I was wondering if this has been implemented or shall I just use the code snippet shared above?
Many thanks!
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Given a new data point and its associated lens values, make it possible to find where it should appear on the graph, i.e. find which cluster is the closest. The lens values can be used to lookup the hypercube(s), then find the nearest cluster(s), like get the N nearest points and return which clusters they belong to.
The text was updated successfully, but these errors were encountered: