-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Using NearestNeighbors
with p < 1
and floats raises an error
#26548
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
Comments
This issue arises due to the different underlying computations when 'X' is of integer or float type. |
I think should allow Feel free to open a PR. |
Out of curiosity, what is your use case for this combination of hyper-parameters? |
@ogrisel I was trying to explore what neighbors look like for high-dimensional datasets, and modifying the metric for that computation. I noticed that I'm happy to open or contribute to a PR on this issue. |
@catanzaromj Are you working on this? If not, I will open PR. |
@Shreesha3112 I am not but I just realized it may be getting fixed on #26568 |
@catanzaromj I think #26568 deals specifically with |
Describe the bug
Using
NearestNeighbors
withp < 1
raises an error if the arrayX
contains floats. It does not seem to raise errors ifX
consists of integers.This was originally discussed in #26536
For example, this is fine:
I would expect this behavior whether
X
consists of floats or integers.Steps/Code to Reproduce
Expected Results
Actual Results
Versions
The text was updated successfully, but these errors were encountered: