After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782656 - interpolation: interpolating at a blank or NaN point should not return #VALUE!
interpolation: interpolating at a blank or NaN point should not return #VALUE!
Status: RESOLVED OBSOLETE
Product: Gnumeric
Classification: Applications
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2017-05-15 12:58 UTC by Frédéric Parrenin
Modified: 2018-05-22 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frédéric Parrenin 2017-05-15 12:58:51 UTC 
Steps to reproduce
- A1=1, A2=2, B1=1, B2=2
- D1=interpolation(A1:A2,B1:B2,C1)
=> #VALUE!
- if you put C1=NaN, still #VALUE!
This is problematic, since if you want to re-use a range encompassing D1 in a formula, it will always return #VALUE!.
I would prefer a Blank or a NaN value.
Comment 1 Andreas J. Guelzow 2017-06-02 04:07:12 UTC 
How are you entering NaN?
Comment 2 Frédéric Parrenin 2017-06-02 07:24:47 UTC 
I am just entering the string "NaN".
Is this correct?
Comment 3 Andreas J. Guelzow 2017-06-05 16:07:15 UTC 
We typically do not interpret strings that way. I thought that you might be using #NA! I could see that if C1 is the error value #NA! we might want to return #NA!. But we really should not act on string content (While NaN has a language independent meaning that would not be obvious to most users.)

Note that you could simulate your desired behaviour by using:
D1=iferror(interpolation(A1:A2,B1:B2,C1),"NaN")
Comment 4 GNOME Infrastructure Team 2018-05-22 14:28:42 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/318.