Fix severe bug in distance matrix -- found/fixed by Bernd Fritzke. #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Nov. 2021, Bernd Fritzke reported & fixed a severe bug in the distance matrix calculation. The bug resulted in poor performance equivalent to naive init (rather than k-means++).
Bernd reports:
In summary:
See also this post by Paul Harrison, who also noticed sub-optimal results. When I compared these to scikit-learn, I discovered the results were as if the inits were still naive (random).
Bernd's analysis would explain that -- and appears to fix it.