-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Inconsistent behaviour of NaN treatment in astropy.convolution.convolve
vs. astropy.convolution.convolve_fft
#16497
Comments
Welcome to Astropy 👋 and thank you for your first issue! A project member will respond to you as soon as possible; in the meantime, please double-check the guidelines for submitting issues and make sure you've provided the requested details. GitHub issues in the Astropy repository are used to track bug reports and feature requests; If your issue poses a question about how to use Astropy, please instead raise your question in the Astropy Discourse user forum and close this issue. If you feel that this issue has not been responded to in a timely manner, please send a message directly to the development mailing list. If the issue is urgent or sensitive in nature (e.g., a security vulnerability) please send an e-mail directly to the private e-mail [email protected]. |
@keflavich , are you able to advise? Thanks! |
Yes, this looks like a bug in |
Description
astropy.convolution.convolve
returns different results depending on if NaN values are present in the input array or not. If no NaN value is present, then the result has a NaN buffer ofkernel_size//2
. If a NaN value is present, then the result is as expected and matches the output ofastropy.convolution.convolve_fft
.Expected behavior
astropy.convolution.convolve
should not have a NaN buffer ofkernel_size//2
if no NaN value is present in the data. In addition the result should not differ depending on NaN values present in the data or not.How to Reproduce
Versions
The text was updated successfully, but these errors were encountered: