-
Notifications
You must be signed in to change notification settings - Fork 14
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
rename extract_cluster
and extract_cluster_assignments
#27
Comments
I picked the
Agree! right now it returns the centroids. For now I like to keep |
Hmmm, that's a good argument for keeping Re: cluster assignments - I definitely take your point, and I know I've advocated for an easier way to extract info from supervised models too, so I guess this falls under that umbrella. |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
As I work with these, I don't like "extract" as the verb - especially because we might be considering extraction style clustering methods in the future...
Being nitpicky, I also thing
extract_cluster
should be wordier. (Is the "cluster" the centroids? The observations?).For the sake of starting conversation, I'll propose:
get_cluster_centers
- with future optional arguments for different notions of centers beyond geometric meansI'm also still on the fence as to whether
extract_cluster_assignments
needs to exist at all. Intidymodels
, the training data is labelled usingpredict
. Since we wantpredict
to always return the original cluster assignments, it may be all we need. Although the dedicated function does avoid duplicate computation of cluster assignments, I suppose...The text was updated successfully, but these errors were encountered: