You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous versions of DataInterpolations (at least v6.0), I could do a LinearInterpolation where one node was at -Inf, and as long as I asked for the value at the other node, there was no problem. Now it throws an InexactError.
Expected behavior
It should give the value at the non-infinite node.
Minimal Reproducible Example 👇
x = [-Inf, 0.0]
y = [-1.0, 1.0]
itp = DataInterpolations.LinearInterpolation(y, x)
itp(0.0) # this gave 1.0 in v6.0.0
I did not know we ever supported this 😅 . If it worked it worked unintentionally, though we could see if we could add that. I presume that beyond linear and constant interpolations though it might be hard to guarantee support for.
We handled it on our side to prevent -Inf from appearing in the input array, but it's a change of behavior in an edge case that wound up breaking our code.
Describe the bug 🐞
In previous versions of DataInterpolations (at least v6.0), I could do a LinearInterpolation where one node was at -Inf, and as long as I asked for the value at the other node, there was no problem. Now it throws an InexactError.
Expected behavior
It should give the value at the non-infinite node.
Minimal Reproducible Example 👇
Error & Stacktrace⚠️
Environment (please complete the following information):
using Pkg; Pkg.status()
using Pkg; Pkg.status(; mode = PKGMODE_MANIFEST)
versioninfo()
Additional context
Making @orso82 aware
The text was updated successfully, but these errors were encountered: