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 615772 - Function argument types 'r' and 'A' vs. errors
Function argument types 'r' and 'A' vs. errors
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: 2010-04-14 18:56 UTC by Morten Welinder
Modified: 2010-04-16 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screns hot (110.48 KB, image/png)
2010-04-14 22:03 UTC, Andreas J. Guelzow 		Details

Description Morten Welinder 2010-04-14 18:56:09 UTC 
A slightly modified copy of
http://www.itl.nist.gov/div898/strd/lls/data/LINKS/DATA/Filip.dat
will be attached.

For some reason, all the regression stats are #REF!
Comment 1 Andreas J. Guelzow 2010-04-14 22:03:19 UTC 
Created attachment 158763 [details]
screns hot

I don't see any problem if I perform a linear regression (with a single x variable).

The results in teh data file are from a polynomial regression. Did you perform that?  Could you provide a sample file?
Comment 2 Andreas J. Guelzow 2010-04-14 22:13:38 UTC 
Ah I see: If I create additional independent variables x^2,...,x^10 then LINEST croaks giving only #NUM!. This causes INDEX to spew #REF!.

This is a LINEST problem and in fact it looks exactly like bug #551457.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 551457 ***
Comment 3 Morten Welinder 2010-04-16 12:27:05 UTC 
#NUM! should never make it to LINEST.  Patch in hand.
Comment 4 Morten Welinder 2010-04-16 12:31:20 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.