Skip to content

Deprecate function-based normalization with nan interpolation - #18365

Draft
keflavich wants to merge 6 commits into
astropy:mainfrom
keflavich:issue8114
Draft

keflavich wants to merge 6 commits into
astropy:mainfrom
keflavich:issue8114

Conversation

@keflavich

Copy link
Copy Markdown
Contributor

Resolves #8114.

That issue noted an inconsistency in convolve vs convolve_fft behavior. The convolve_fft behavior is, as I now see it, allowing for unnecessary corner cases. The proposal is to eventually raise an Exception for the circumstance highlighted here (nan_treatment='interpolate' with a user-specified normalization function), but start by deprecating.

I could use some hand-holding on the deprecation process - should I add a release ID to the deprecation warning here?

@github-actions

This comment was marked as spam.

@github-actions

This comment was marked as spam.

@keflavich

Copy link
Copy Markdown
Contributor Author

Since the original point of the issue was that it was holding back a performance-boosting change in #8101, I've added those changes back in here. That is also in-scope as improving consistency between convolve and convolve_fft

@pllim pllim added this to the v7.2.0 milestone Jun 30, 2025
@pllim pllim added the API change PRs and issues that change an existing API, possibly requiring a deprecation period label Jun 30, 2025
@astrofrog astrofrog modified the milestones: v7.2.0, v9.0.0, v8.0.0 Nov 3, 2025
@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label Nov 26, 2025
@github-actions

Copy link
Copy Markdown
Contributor

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.

@keflavich keflavich removed the Close? Tell stale bot that this issue/PR is stale label Nov 28, 2025
@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label Apr 28, 2026
@github-actions

Copy link
Copy Markdown
Contributor

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.

@keflavich keflavich removed the Close? Tell stale bot that this issue/PR is stale label Apr 28, 2026
@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label Apr 29, 2026
@github-actions

github-actions Bot commented May 1, 2026

Copy link
Copy Markdown
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 5 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.

@keflavich keflavich added keep-open and removed Close? Tell stale bot that this issue/PR is stale labels May 1, 2026
@astrofrog astrofrog modified the milestones: v8.0.0, v8.1.0 May 5, 2026
@pllim pllim removed the keep-open label Oct 14, 2026
@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label Oct 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 11 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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

API change PRs and issues that change an existing API, possibly requiring a deprecation period Close? Tell stale bot that this issue/PR is stale convolution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issues with NaN treatment and normalisation in convolve_fft

3 participants