8000 Add a test case for OPTICS bug #12090 by kno10 · Pull Request #12134 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

Add a test case for OPTICS bug #12090 #12134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

kno10
Copy link
Contributor
@kno10 kno10 commented Sep 22, 2018

Reference Issues/PRs

See also #12090

What does this implement/fix? Explain your changes.

Unit test to trigger a bug in current OPTICS code.

kno10 added a commit to kno10/scikit-learn that referenced this pull request Sep 22, 2018
kno10 added a commit to kno10/scikit-learn that referenced this pull request Oct 11, 2018
qinhanmin2014 pushed a commit that referenced this pull request Oct 14, 2018
* Add a test case for OPTICS bug (closes #12134)

* ENH Fix processing order in OPTICS. See #12090

The current code may expand the wrong point, because it only considers
the neighbors of the current point, not all currently unprocessed points
(which may have a better reachability).

Using the distance from the latest point as tiebreaker then does not
work anymore, because it might not yet be computed for all unprocessed
points when using an index.

If we choose the first on ties, we get the same result same as R and ELKI.

But the order of points in "unproc" is also unstable, so we cannot rely
on the first smallest to have the smallest index.

Instead of the cython quick_scan, we now use numpy masked arrays.
anuragkapale pushed a commit to anuragkapale/scikit-learn that referenced this pull request Oct 23, 2018
* Add a test case for OPTICS bug (closes scikit-learn#12134)

* ENH Fix processing order in OPTICS. See scikit-learn#12090

The current code may expand the wrong point, because it only considers
the neighbors of the current point, not all currently unprocessed points
(which may have a better reachability).

Using the distance from the latest point as tiebreaker then does not
work anymore, because it might not yet be computed for all unprocessed
points when using an index.

If we choose the first on ties, we get the same result same as R and ELKI.

But the order of points in "unproc" is also unstable, so we cannot rely
on the first smallest to have the smallest index.

Instead of the cython quick_scan, we now use numpy masked arrays.
xhluca pushed a commit to xhluca/scikit-learn that referenced this pull request Apr 28, 2019
* Add a test case for OPTICS bug (closes scikit-learn#12134)

* ENH Fix processing order in OPTICS. See scikit-learn#12090

The current code may expand the wrong point, because it only considers
the neighbors of the current point, not all currently unprocessed points
(which may have a better reachability).

Using the distance from the latest point as tiebreaker then does not
work anymore, because it might not yet be computed for all unprocessed
points when using an index.

If we choose the first on ties, we get the same result same as R and ELKI.

But the order of points in "unproc" is also unstable, so we cannot rely
on the first smallest to have the smallest index.

Instead of the cython quick_scan, we now use numpy masked arrays.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0