KMeans - Going forward

[Olly Betts]

On Sun, Jul 23, 2017 at 03:50:51PM -0400, Richhiey Thomas wrote:
> Going forward, the next step to optimize KMeans is to use the faster
> optimized version of KMeans which reduces distance computations developed
> by Charles Elkan. For this, I will be providing the user an option to
> specify with the constructor whether they would want the standard algorithm
> or Elkans algorithm.

Is having a choice actually useful to the API user?

Unless the optimised algorithm is sometimes slower (and in a way that
you can usefully predict up front), or uses significantly more memory,
then this just seems like pointless clutter in the API and extra code in
the library.

Cheers,
    Olly