public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ivo Alxneit <ivo.alxneit@psi.ch>
To: Brian Gough <bjg@network-theory.co.uk>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: help with gsl_matrix_complex_row
Date: Tue, 20 May 2003 09:17:00 -0000	[thread overview]
Message-ID: <200305201109.41196.ivo.alxneit@psi.ch> (raw)
In-Reply-To: <16073.2415.364552.763652@debian.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ooops my initial response was not cc'ed to gsl-discuss so i include it here :
> >i get
> >row0(0) = 1, 1.1
> >row1(0) = -3.00652e-182, 7.7651e-62
> >row0(1) = 1.2, 1.3
> >row1(1) = -1.31435e+64, 3.39464e+184
> >on
> >gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)
> >
> >compiler problem?
> >
> >i checked with ddd. gsl_matrix m is correctly initialized but
> >vv1=gsl_matrix_complex_row fails.
> >
> > my initial response ends here

On Monday 19 May 2003 18:42, you wrote:
> Ivo Alxneit writes:
>  > gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)
>  >
>  > compiler problem?
>
> Yes, I don't think the library passes "make check" with that compiler,
> because of this problem with complex numbers.
i just tried make check 

make check stops with
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/usr/local/src/gsl-1.3/eigen'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/usr/local/src/gsl-1.3/eigen'
make: *** [check-recursive] Error 1

no FAIL's in gsl/{complex,vector,matrix,block} !
careful: gsl_matrix_complex_row() is not checked but gsl_matrix_complex 
get_row PASSes!

i get a lot (1144) of FAIL's  in gsl/eigen in the herm(4) and herm(10) part. i 
dont include them here.
most of them are that i get completely different numbers than expected but 
there are also 'interesting' cases

FAIL: herm(4), eigenvalue(1,0), real, unsorted
       (-4.54283729443259248e-305 ob vs -1.77454581813773183e-307 expected)
FAIL: herm(4), eigenvalue(1,2), real, unsorted
      (-1.77454581813773144e-307 obs vs -4.54283729443259349e-305 expected)
- -> (1,0) and (1,2) exchanged??

quite some ieee errors like
nan expected versus 0/1 observed
inf expected versus 0 observed

- --
Dr. Ivo Alxneit
Laboratory for Solar Technology   phone: +41 56 310 4092
Paul Scherrer Institute             fax: +41 56 310 2624
CH-5232 Villigen                   http://solar.web.psi.ch
Switzerland                   gnupg key: 0x515E30C7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+yfDUAd7CE1FeMMcRAtPkAJ94X7YJQQ59QUpXeKGgD5H7MXP3jQCgvnpz
nFoOutfgDvhCnZ/amrL3HeU=
=zopR
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2003-05-20  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 21:31 Mario Pernici
2003-05-19  9:42 ` Brian Gough
     [not found] ` <200305191158.43653.ivo.alxneit@psi.ch>
     [not found]   ` <16073.2415.364552.763652@debian.local>
2003-05-20  9:17     ` Ivo Alxneit [this message]
2003-05-20 13:01 Mario Pernici
2003-05-20 13:30 ` Dirk Eddelbuettel
2003-05-20 22:15   ` Mario Pernici

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200305201109.41196.ivo.alxneit@psi.ch \
    --to=ivo.alxneit@psi.ch \
    --cc=bjg@network-theory.co.uk \
    --cc=gsl-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).