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.

Sign up for GitHub

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

Jump to bottom

Surprising behavior for get_clusters with the first-k method. #52

Open
bpkent opened this issue Jan 17, 2016 · 0 comments
Open

Surprising behavior for get_clusters with the first-k method. #52

bpkent opened this issue Jan 17, 2016 · 0 comments
Assignees
@bpkent
Labels
API usability

Comments

@bpkent
Copy link
Collaborator

bpkent commented Jan 17, 2016

When retrieving clusters with the first-k method, there is some surprising behavior for edge cases.

  • If there are more root nodes than k, all roots are returned as clusters, so there are more than k clusters.
  • If there are fewer than 'k', each leaf is a cluster, but this still leaves fewer than 'k' clusters.

The solution is probably to simply warn the user when the number of clusters returned isn't exactly 'k'.
@bpkent bpkent self-assigned this Jan 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bpkent bpkent

Labels
API usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bpkent