You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Predict the cluster label of new points. The returned labels will be those of the original clustering found by clusterer, and therefore are not (necessarily) the cluster labels that would be found by clustering the original data combined with points_to_predict, hence the ‘approximate’ label.
Describe alternatives you've considered
Forking CuML and building the functionality, but perhaps it's already on your roadmap?
I saw on one of the issues it was slated for 22.04, but the 22.04 issue/project was closed/resolved without comment. Is it planned for a future release? I could take a stab at implementation for a future release if the issue is lack of resources.
The text was updated successfully, but these errors were encountered:
@whymauri no worries! As always, we welcome all contributions since you mentioned in your alternatives that you could want to implement this feature. If you would like to do that, I can be a resource to you in any way that is needed to get the PR across the finish line.
Is your feature request related to a problem? Please describe.
approximate_predict()
method.Describe the solution you'd like
Similar to scikit-learn HDBSCAN's approximate_predict
https://hdbscan.readthedocs.io/en/latest/api.html#hdbscan.prediction.approximate_predict
Predict the cluster label of new points. The returned labels will be those of the original clustering found by clusterer, and therefore are not (necessarily) the cluster labels that would be found by clustering the original data combined with points_to_predict, hence the ‘approximate’ label.
Describe alternatives you've considered
Forking CuML and building the functionality, but perhaps it's already on your roadmap?
I saw on one of the issues it was slated for 22.04, but the 22.04 issue/project was closed/resolved without comment. Is it planned for a future release? I could take a stab at implementation for a future release if the issue is lack of resources.
The text was updated successfully, but these errors were encountered: