BUG: interpolate: integral(a, b) should be zero when both limits are outside of the interpolation range #10633
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ev-br
added
defect
|
|
|
Yeah, it's zero regardless of the extrapolation mode. We could bolt it on, but it's been like that since forever (?) and I'm not sure we should change it. |
ev-br
changed the title
Integrals should be zero when both limits are outside of the interpolation range fixes scipygh-7906
tylerjereddy
added a commit
to tylerjereddy/scipy
that referenced
this pull request
Jan 20, 2020
* update SciPy 1.2.3 release notes to include backports for: scipygh-11126, scipygh-10906, scipygh-10633, scipygh-10138, and scipygh-10076. * briefly mention in the notes that this is part of the Python 2.7 LTS support series
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Integrals should be zero when both limits are outside of the interpolation range
fixes gh-7906
The bug was that FITPACK moves the out-of-range upper limit of integration to the upper bound of the base interval, and the out-of-range lower limit to the lower bound. This way, if both limits are, say, above the upper bound, the lower limit stays above it, and the computational routine goes haywire.