[MRG+1] Fix optics metric issues (DOC and precomputed)#12028
[MRG+1] Fix optics metric issues (DOC and precomputed)#12028qinhanmin2014 merged 7 commits intoscikit-learn:masterfrom
Conversation
|
I'm not sure about this travis error, is it because of something I did? |
|
We are pretty informal about what should deserve author credit. Maybe we
should have some written policy. I've certainly touched a lot more files
than credit me as an author, but when a contributor adds their name to the
list it's not like I'm going to argue; and when we split modules, we are
not meticulous about splitting the author list.
|
jnothman
left a comment
There was a problem hiding this comment.
We should accept a sparse X as well, but that may be a separate pr.
Can you test metrics supported by neighbors and by metrics.pairwise and all their combinations. I'm a bit worried about us mixing them
|
I just checked the metrics supported by I also tried running |
|
@jnothman, regarding the sparse Which throws: |
|
Not sparse precomputed, just sparse feature matrix with, say, Euclidean
distance
|
|
I guess we can handle the sparse input in a separate PR, should we merge this? |
qinhanmin2014
left a comment
There was a problem hiding this comment.
LGTM, thanks @adrinjalali
|
Hi team, thanks for your great work! I was wondering if there's any plan to support sparse input for OPTICS recently? |
|
Sparse input meaning sparse precomputed distance graph?
|
|
Meaning the scikit-learn/sklearn/cluster/dbscan_.py Lines 330 to 355 in 68044b0 |
|
It might be very easy to support. Try adding accept_sparse and test it out.
|
Fixes #12009
See #11982
Still doesn't support the output of
radius_neighbors_graphas input though.Question: what's the criterion to include one's name in the authors section in the files? Are those only the original authors or do I count as an author in the
optics_.pyandtest_optics.pynow?