numpy-discussion

[Numpy-discussion] dgesdd error

[Travis O. <oli...@ie...>]

Apparently some dgesdd libraries don't actually compute the correct 
value for the work-space size if requested. 

This results in an ** ILLEGAL value and program termination from LAPACK.

I've added code in the latest SVN to that particular wrapper to make 
sure the query gives back the minimums at least, but I'd like to see who 
else has the problem.

On my system, doing numpy.linalg.svd on a 25 x 50 array pulled the trigger.

Anybody else have that problem with their lapack library?

-Travis

Re: [Numpy-discussion] dgesdd error

[Fernando P. <fpe...@gm...>]

On 11/1/06, Travis Oliphant <oli...@ie...> wrote:
>
> Apparently some dgesdd libraries don't actually compute the correct
> value for the work-space size if requested.
>
> This results in an ** ILLEGAL value and program termination from LAPACK.
>
> I've added code in the latest SVN to that particular wrapper to make
> sure the query gives back the minimums at least, but I'd like to see who
> else has the problem.
>
> On my system, doing numpy.linalg.svd on a 25 x 50 array pulled the trigger.
>
> Anybody else have that problem with their lapack library?

Seems fine here:

In [4]: N.linalg.svd(N.random.rand(25,50));

In [5]: N.linalg.svd(N.random.rand(25,50));

In [6]: N.__version__
Out[6]: '1.0.1.dev3423'

Ubuntu Dapper (6.06) box, up to date.  I'm using the ubuntu-supplied
ATLAS and LAPACK, I can give you more info if needed.

Cheers,

f

Re: [Numpy-discussion] dgesdd error

[Charles R H. <cha...@gm...>]

On 11/1/06, Fernando Perez <fpe...@gm...> wrote:
>
> On 11/1/06, Travis Oliphant <oli...@ie...> wrote:
> >
> > Apparently some dgesdd libraries don't actually compute the correct
> > value for the work-space size if requested.
> >
> > This results in an ** ILLEGAL value and program termination from LAPACK.
> >
> > I've added code in the latest SVN to that particular wrapper to make
> > sure the query gives back the minimums at least, but I'd like to see who
> > else has the problem.
> >
> > On my system, doing numpy.linalg.svd on a 25 x 50 array pulled the
> trigger.
> >
> > Anybody else have that problem with their lapack library?
>
> Seems fine here:


Fine here also: 1.0.1.dev3416

Fedora 6, ATLAS and LAPACK from extras.

Chuck

Re: [Numpy-discussion] dgesdd error

[Charles R H. <cha...@gm...>]

On 11/1/06, Charles R Harris <cha...@gm...> wrote:
>
>
>
> On 11/1/06, Fernando Perez <fpe...@gm...> wrote:
> >
> > On 11/1/06, Travis Oliphant <oli...@ie...> wrote:
> > >
> > > Apparently some dgesdd libraries don't actually compute the correct
> > > value for the work-space size if requested.
> > >
> > > This results in an ** ILLEGAL value and program termination from
> > LAPACK.
> > >
> > > I've added code in the latest SVN to that particular wrapper to make
> > > sure the query gives back the minimums at least, but I'd like to see
> > who
> > > else has the problem.
> > >
> > > On my system, doing numpy.linalg.svd on a 25 x 50 array pulled the
> > trigger.
> > >
> > > Anybody else have that problem with their lapack library?
> >
> > Seems fine here:
>
>
> Fine here also: 1.0.1.dev3416
>
> Fedora 6, ATLAS and LAPACK from extras.
>
> Chuck
>

Oh, and 32 bit.