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 323784 - funb.xls: BESSEL*() functions not Excel-compatible
funb.xls: BESSEL*() functions not Excel-compatible
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Analytics
git master
Other All
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-12-11 12:42 UTC by Nick Lamb
Modified: 2008-06-20 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nick Lamb 2005-12-11 12:42:34 UTC
http://www.ecs.soton.ac.uk/~njl98r/excel/funb.xls

All BESSEL*() group functions fail Excel compatibility test. Gnumeric
documentation claims that they are compatible. Most of these functions fail for
two or more of the following reasons:

1. The order parameter 'y' is truncated before being range checked, so that
Gnumeric doesn't give #NUM! for -1.0 < 'y' < 0.0

2. The order parameter is not truncated at all, I don't know if these functions
are in fact defined for non-integer 'y' but the Help claims they are not.
Someone who uses and understands the functions should decide whether to truncate
or change the documentation.

3. Gnumeric accepts array formulae without array notation and gives first row,
first column answer, whereas Excel gives #VALUE! e.g. for =BESSELI(A3:C3,2).
This is a general problem, is it intentional? Is it useful functionality? Feel
free to break out to a separate bug if this isn't a simple decision.
Comment 1 Morten Welinder 2005-12-13 22:04:23 UTC
At least some of them do make sense for non-integer orders.  Bummer.
Comment 2 Morten Welinder 2008-06-20 13:54:06 UTC
Fixed, part from 3 which is covered elsewhere, I believe.

BESSELI had problems with negative x for some orders.  Docs were fixed.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.