Repository navigation
Conversation
|
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
|
Hi humans 👋 - this pull request hasn't had any new commits for approximately 4 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then. In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary. If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock. If you believe I commented on this pull request incorrectly, please report this here. |
|
I used an LLM to write the tests, but I checked the numerical values by hand (they got them wrong sometimes anyway... unfortunately my by-hand checking is not guaranteed to be correct at only 0.75 coffees into the day). TODO: Why is the coverage <100%? |
The report in Details might give you clue. A rebase might also help (but maybe not but doesn't hurt). |
|
thanks. i thought i had rebased already, but maybe i lost this one in the mix... |
|
I had rebased, but apparently hadn't fetched recently enough. |
|
Still need that change log fragment. Thanks! |
|
Hi humans 👋 - this pull request hasn't had any new commits for approximately 4 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then. In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary. If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock. If you believe I commented on this pull request incorrectly, please report this here. |
larrybradley
left a comment
There was a problem hiding this comment.
Thanks, @keflavich. I have a few comments to address.
As a general comment (not for this PR), we should eventually clean up the tests to parameterize convolve/convolve_fft. There is a lot of duplicated test code.
Also, this PR has merge conflicts and needs a rebase.
| convolve_fft should treat infinities like NaN values. | ||
| Regression test for issue #8099. | ||
| """ | ||
| from astropy.convolution import Gaussian1DKernel |
There was a problem hiding this comment.
Move import to top of file.
| assert not np.any(np.isnan(result)) | ||
|
|
||
|
|
||
| def test_convolve_fft_kernel_with_inf(): |
There was a problem hiding this comment.
This test is identical to test_kernel_with_inf. Remove one of them.
There was a problem hiding this comment.
I bet this was from a bad rebase way back months ago...
Co-authored-by: Larry Bradley <[email protected]>
Co-authored-by: Larry Bradley <[email protected]>
Co-authored-by: Larry Bradley <[email protected]>
Co-authored-by: Larry Bradley <[email protected]>
|
pre-commit.ci autofix |
|
@keflavich This PR stills need a rebase to resolve merge conflicts. |
|
Hi humans 👋 - this pull request hasn't had any new commits for approximately 6 months. I plan to close this in a month if the pull request doesn't have any new commits by then. In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary. If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock. If you believe I commented on this pull request incorrectly, please report this here. |

Resolves #8099.
convolve_ffthas always treatedinfasnan, since it is not possible to do otherwise and get a usable result.convolvehas allowed infs to be propagated around by the kernel size.This PR prevents the latter behavior. I think it is a correct solution, but it is theoretically possible that someone has relied on this 'bug' over the last 7 years, so it warrants allowing for some minimal discussion.