Skip to content

When estimating number of clusters/cuts automatically, don't allow nClusters== nCuts #21

Description

@mjlm

Most of the time, the number of clusters should be the number of cuts plus one. But sometimes, the function to estimate nCuts/nClusters automatically suggestsnClusters== nCuts. I always find myself changing that to nClusters== nCuts+1. I think it is sufficiently rare that nClusters== nCuts is really the best choice that we should never allow the auto-algorithm to suggest that.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions