Skip to content
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

[FEA] Take advantage of MST in hierarchical clustering #2727

Closed
afender opened this issue Aug 20, 2020 · 4 comments
Closed

[FEA] Take advantage of MST in hierarchical clustering #2727

afender opened this issue Aug 20, 2020 · 4 comments
Labels
? - Needs Triage Need team to review and classify feature request New feature or request inactive-90d

Comments

@afender
Copy link
Member

afender commented Aug 20, 2020

Minimum spanning trees come up in hierarchical clustering is to enable a single-linkage clustering and the ability to draw dendrograms like Scipy's hierarchy package, which also enables HDBSCAN.

The kernels are being implemented in RAFT since it could also be used un cuGraph in the long run : rapidsai/raft#52


Solution

Parallel Baruvka algorithm supporting disconnected components. It is similar to Louvain in the sense it starts from all vertices as seeds and aggregate vertices into super vertices based on edge weights.

relevant papers :

Alternatives considered
Specific solutions for KNN-graphs. While this allows some optimizations, a more generic solution would have more benefits for the whole RAPIDS platform

  • “Fast Euclidean Minimum Spanning Tree: Algorithm, Analysis, & Applications.
  • "Design & Implementation of Cover Tree Algorithm on CUDA-Compatible GPU”
@afender afender added ? - Needs Triage Need team to review and classify feature request New feature or request labels Aug 20, 2020
@cjnolet
Copy link
Member

cjnolet commented Aug 20, 2020

Ref: #1783

@github-actions
Copy link

This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@github-actions
Copy link

This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.

@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
? - Needs Triage Need team to review and classify feature request New feature or request inactive-90d
Projects
None yet
Development

No branches or pull requests

3 participants