This makes little difference, and original DBSCAN did not shuffle.
Warn if `random_state` is used.
As is `random_state` encourages users to experiment with different
randomization, as you would do with k-means. But in contrast to
k-means, the output of DBSCAN is deterministic except for cluster
enumeration and "rare" cases, where a point is on the border of
two clusters at the same time. As this affects single points only,
the measureable performance difference will be close to zero.
Also, incorporate fix for minpts including the query point.
Make sparsity check check everything.
don't test everything. That would be nice but is out of scope :-/
catch special case of no core samples in DBSCAN
add nonregression test for sparse dbscan with no core samples.
Joel Nothman