Hi all, I recently got a report of a bug triggered only on 64-bit hardware, and on a machine (in case it's relevant) that runs python 2.5. This is with current numpy SVN which I just rebuilt a moment ago to triple-check: In [3]: a = numpy.array([[1.0,2],[3,4]]) In [4]: numpy.linalg.qr(a) ** On entry to DGEQRF parameter number 2 had an illegal value sage[~]> # dumped back at system prompt In case anyone has ideas, I added some more initial detail and guesses as to where the problem may be coming from here: http://projects.scipy.org/scipy/numpy/ticket/446 Unfortunately I don't know this part of the code well enough to come up with a quick fix myself. Cheers, f
Fernando Perez wrote:
I recently got a report of a bug triggered only on 64-bit hardware, and on a machine (in case it's relevant) that runs python 2.5. This is with current numpy SVN which I just rebuilt a moment ago to triple-check:
In [3]: a = numpy.array([[1.0,2],[3,4]])
In [4]: numpy.linalg.qr(a) ** On entry to DGEQRF parameter number 2 had an illegal value sage[~]> # dumped back at system prompt
Has there been any progress in solving this problem? I get the same error message and have no idea how to solve it. Regards, Steffen
Steffen Loeck wrote:
Fernando Perez wrote:
I recently got a report of a bug triggered only on 64-bit hardware, and on a machine (in case it's relevant) that runs python 2.5. This is with current numpy SVN which I just rebuilt a moment ago to triple-check:
In [3]: a = numpy.array([[1.0,2],[3,4]])
In [4]: numpy.linalg.qr(a) ** On entry to DGEQRF parameter number 2 had an illegal value sage[~]> # dumped back at system prompt
Has there been any progress in solving this problem? I get the same error message and have no idea how to solve it.
Regards, Steffen _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Confirmed with Python 2.4.1 (#1, Oct 13 2006, 16:51:58) [GCC 4.0.2 20050901 (prerelease) (SUSE Linux)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
import numpy numpy.__version__ '1.0.2.dev3571' a = numpy.array([[1.0,2],[3,4]]) numpy.linalg.qr(a) ** On entry to DGEQRF parameter number 2 had an illegal value
Nils
On Monday 05 March 2007 08:01, Steffen Loeck wrote:
Has there been any progress in solving this problem? I get the same error message and have no idea how to solve it.
I do not understand those code parts very well but I think the values passed to the lapack routines must be integer and not long integer on 64bit architecture. A few tests with the attached patch worked well. Best Regards, Lars
On Wednesday 07 March 2007 09:57, Lars Bittrich wrote:
I do not understand those code parts very well but I think the values passed to the lapack routines must be integer and not long integer on 64bit architecture. A few tests with the attached patch worked well.
It works fine for me now. Thanks a lot, Steffen
On Mar 7, 2007, at 04:57 , Lars Bittrich wrote:
On Monday 05 March 2007 08:01, Steffen Loeck wrote:
Has there been any progress in solving this problem? I get the same error message and have no idea how to solve it.
I do not understand those code parts very well but I think the values passed to the lapack routines must be integer and not long integer on 64bit architecture. A few tests with the attached patch worked well.
Yeah, this problem is kind of ugly; we should have a test for the integer size in Fortran compilers. However, I don't know how to do that. We've been pretty lucky so far: INTEGER seems to be a C int on everything. I know this is true for GNU Fortran (g77, gfortran) on Linux, on both 32-bit and 64-bit platforms. But I don't think there's any guarantee that it would be true in general. -- |>|\/|< /------------------------------------------------------------------\ |David M. Cooke http://arbutus.physics.mcmaster.ca/dmc/ |cookedm@physics.mcmaster.ca
Steffen Loeck wrote:
Fernando Perez wrote:
I recently got a report of a bug triggered only on 64-bit hardware, and on a machine (in case it's relevant) that runs python 2.5. This is with current numpy SVN which I just rebuilt a moment ago to triple-check:
In [3]: a = numpy.array([[1.0,2],[3,4]])
In [4]: numpy.linalg.qr(a) ** On entry to DGEQRF parameter number 2 had an illegal value sage[~]> # dumped back at system prompt
Has there been any progress in solving this problem? I get the same error message and have no idea how to solve it.
I just added a patch from Lars Bittrich that probably solves it. Try it now. -Travis
participants (6)
-
David M. Cooke -
Fernando Perez -
Lars Bittrich -
Nils Wagner -
Steffen Loeck -
Travis Oliphant