-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[ENH] K-means: clusters can be inferred for new data #7010
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
[ENH] K-means: clusters can be inferred for new data #7010
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7010 +/- ##
=========================================
Coverage ? 88.72%
=========================================
Files ? 332
Lines ? 73444
Branches ? 0
=========================================
Hits ? 65164
Misses ? 8280
Partials ? 0 🚀 New features to boost your workflow:
|
1dc93bf
to
87bf4cc
Compare
f213cbe
to
0fb6067
Compare
0fb6067
to
79d9a62
Compare
@janezd, I finally finished |
e52507e
to
6ff8cff
Compare
Issue
@borondics had a so big data set that k-means was too slow, so he tried doing it on a sample and then modelling the clustering with a classifier. But for k-means this should not be needed because we could use the means/medoids to "predict" the cluster directly.
With one additional line we could make the Cluster useful with Apply domain.
Why don't we already do it? All the machinery is already there, in
ClusteringModel
, which does seems unused though. DoesIncludes