-
Notifications
You must be signed in to change notification settings - Fork 92
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
FutureWarning #162
Comments
Thanks for letting me know. If someone wants to look into this, I will happily merge a PR |
Hi all, kernel_funcs.py @ line 294 (v1.1.8):
The warning happens as f(x) returns an array. I think that this can be fixed (for my problem at least) by simply returning the first element, e.g.:
However, this will not work if bw is not a float (a brief look at the code seems to imply that bw could be an array... is that correct?). As I did not study the code sufficiently, I am reluctant to formally propose this fix. What do you think? |
I looks like you're onto something! Makes sense that the Please do propose a fix! If tests pass with no FutureWarning then we're good! |
Thank you for your support. While the mod fixed my problem, warnings were raised while running test_api.py, likely coming from the usage of brentq in bw_selection.py. I will investigate and try to propose a fix when I have free time. |
Hello everyone,
I am getting the following FutureWarning:
A minimal example to reproduce the behaviour:
I am using the version 1.1.8 of KDEpy and 1.26.4 of numpy.
The text was updated successfully, but these errors were encountered: