Re: [SciPy-Dev] [SciPy-User] ANN: SciPy 0.11.0 release candidate 1
On Sat, Jul 21, 2012 at 7:21 PM, John Hassler <hasslerjc@comcast.net> wrote:
On 7/20/2012 5:00 PM, Pauli Virtanen wrote:
20.07.2012 22:24, John Hassler kirjoitti:
The offending line is: AA,BB,Q,Z,sdim = qz(A,B,sort=sort)
I couldn't find 'sort' defined anywhere, so I arbitrarily changed it to sort='lhp'. Then it runs, although the test fails.
Is there something else I can try? Seems to be a problem with the callable sort function then.
That it works with sort='lhp' is strange, and probably means that there is not a problem with all callback functions, but something goes wrong in the algorithm. (Which would be expected, if *gees callbacks work without problems.)
If you can/know how to recompile, try recompiling with
set OPT=-g -DDEBUGCFUNCS python setup.py .........
This should make the f2py wrappers spit out extra information on what is going on.
I'm not set up to recompile.
Is there anyone who can reproduce the issue and investigate this further? Alternatively I can build some binaries with the above debug flags. I can't reproduce the issue though, so that may be a painful way to debug. Ralf
I set up a little test program to reproduce the problem (below). It leads to the Fortran call to gges in _decomp_qz.py. This crashes if sort_t = 1 (which calls the lambda), but not for sort_t = 0. I didn't play with it any further. john
# Test qz import numpy as np from scipy.linalg import qz
A = np.array([[3.9, 12.5, -34.5, -0.5], [ 4.3, 21.5, -47.5, 7.5], [ 4.3, 21.5, -43.5, 3.5], [ 4.4, 26.0, -46.0, 6.0 ]])
B = np.array([[ 1.0, 2.0, -3.0, 1.0], [1.0, 3.0, -5.0, 4.0], [1.0, 3.0, -4.0, 3.0], [1.0, 3.0, -4.0, 4.0]])
#sort = lambda ar,ai,beta : ai == 0 ## crashes sort = None ## runs
print(qz(A,B,sort=sort))
_______________________________________________ SciPy-User mailing list SciPy-User@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-user
On Mon, Jul 30, 2012 at 10:36 PM, Ralf Gommers <ralf.gommers@googlemail.com>wrote:
On Sat, Jul 21, 2012 at 7:21 PM, John Hassler <hasslerjc@comcast.net>wrote:
On 7/20/2012 5:00 PM, Pauli Virtanen wrote:
20.07.2012 22:24, John Hassler kirjoitti:
The offending line is: AA,BB,Q,Z,sdim = qz(A,B,sort=sort)
I couldn't find 'sort' defined anywhere, so I arbitrarily changed it to sort='lhp'. Then it runs, although the test fails.
Is there something else I can try? Seems to be a problem with the callable sort function then.
That it works with sort='lhp' is strange, and probably means that there is not a problem with all callback functions, but something goes wrong in the algorithm. (Which would be expected, if *gees callbacks work without problems.)
If you can/know how to recompile, try recompiling with
set OPT=-g -DDEBUGCFUNCS python setup.py .........
This should make the f2py wrappers spit out extra information on what is going on.
I'm not set up to recompile.
Is there anyone who can reproduce the issue and investigate this further? Alternatively I can build some binaries with the above debug flags. I can't reproduce the issue though, so that may be a painful way to debug.
I have been able to reproduce this now. Some tracebacks and details at http://projects.scipy.org/scipy/ticket/1717. If anyone has some ideas, shoot! Ralf
Ralf
I set up a little test program to reproduce the problem (below). It leads to the Fortran call to gges in _decomp_qz.py. This crashes if sort_t = 1 (which calls the lambda), but not for sort_t = 0. I didn't play with it any further. john
# Test qz import numpy as np from scipy.linalg import qz
A = np.array([[3.9, 12.5, -34.5, -0.5], [ 4.3, 21.5, -47.5, 7.5], [ 4.3, 21.5, -43.5, 3.5], [ 4.4, 26.0, -46.0, 6.0 ]])
B = np.array([[ 1.0, 2.0, -3.0, 1.0], [1.0, 3.0, -5.0, 4.0], [1.0, 3.0, -4.0, 3.0], [1.0, 3.0, -4.0, 4.0]])
#sort = lambda ar,ai,beta : ai == 0 ## crashes sort = None ## runs
print(qz(A,B,sort=sort))
_______________________________________________ SciPy-User mailing list SciPy-User@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-user
06.08.2012 23:21, Ralf Gommers kirjoitti:
On Mon, Jul 30, 2012 at 10:36 PM, Ralf Gommers wrote: [clip] I have been able to reproduce this now. Some tracebacks and details at http://projects.scipy.org/scipy/ticket/1717. If anyone has some ideas, shoot!
If I understand correctly, this bug only occurs with the SSE3 binaries in our vendor repo. I should try to reproduce this also. Compiling with DEBUGFLAGS seems not to have worked out in your case. The f2py wrappers should spew out a lot of debug prints, if compiled with the correct debug #define enabled. The second thing is a longer shot, but wine does have a debugger, and obtaining a traceback from that could help. Or possibly not. Pauli
On Tue, Aug 7, 2012 at 12:40 AM, Pauli Virtanen <pav@iki.fi> wrote:
06.08.2012 23:21, Ralf Gommers kirjoitti:
On Mon, Jul 30, 2012 at 10:36 PM, Ralf Gommers wrote: [clip] I have been able to reproduce this now. Some tracebacks and details at http://projects.scipy.org/scipy/ticket/1717. If anyone has some ideas, shoot!
If I understand correctly, this bug only occurs with the SSE3 binaries in our vendor repo. I should try to reproduce this also.
Compiling with DEBUGFLAGS seems not to have worked out in your case. The f2py wrappers should spew out a lot of debug prints, if compiled with the correct debug #define enabled.
So where does f2py get its flags from? Since I can't set env variables in wine the way you suggested, I added this flag to the following items in "executables" in numpy/distutils/gnu.py (and checked that they were present in the build log): 'compiler_f77' 'compiler_f90' 'linker_so' 'linker_exe' Ralf
The second thing is a longer shot, but wine does have a debugger, and obtaining a traceback from that could help. Or possibly not.
Pauli
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@scipy.org http://mail.scipy.org/mailman/listinfo/scipy-dev
participants (3)
-
Pauli Virtanen -
Ralf Gommers -
Ralf Gommers