On Nov 23, 3:54 am, Jason Grout jason-s...@creativetrax.com wrote:
On 11/22/10 1:48 PM, Ethan Van Andel wrote:
In my development, I'm attempting to parallelize some code. However,
the bottleneck is a call to numpy.linalg.lapack_lite.zgesv, that is
the point where numpy calls LAPACK to
I wonder why zgesv comes here from lapack_lite rather than from Atlas,
which might have much faster zgesv.
Is it a feature (or a bug) of Sage configuration of Numpy?
Or in fact it does come come Atlas?
Dima
On Nov 23, 9:19 pm, dagss da...@student.matnat.uio.no wrote:
On Nov 23, 3:54 am, Jason
On Nov 23, 3:25 pm, Dima Pasechnik dimp...@gmail.com wrote:
I wonder why zgesv comes here from lapack_lite rather than from Atlas,
which might have much faster zgesv.
Is it a feature (or a bug) of Sage configuration of Numpy?
Or in fact it does come come Atlas?
It's just a strange feature of
On 11/23/10 7:19 AM, dagss wrote:
On Nov 23, 3:54 am, Jason Groutjason-s...@creativetrax.com wrote:
On 11/22/10 1:48 PM, Ethan Van Andel wrote:
In my development, I'm attempting to parallelize some code. However,
the bottleneck is a call to numpy.linalg.lapack_lite.zgesv, that is
the point
On Nov 23, 4:22 pm, Jason Grout jason-s...@creativetrax.com wrote:
On 11/23/10 7:19 AM, dagss wrote:
On Nov 23, 3:54 am, Jason Groutjason-s...@creativetrax.com wrote:
On 11/22/10 1:48 PM, Ethan Van Andel wrote:
In my development, I'm attempting to parallelize some code. However,
On 11/22/10 1:48 PM, Ethan Van Andel wrote:
In my development, I'm attempting to parallelize some code. However,
the bottleneck is a call to numpy.linalg.lapack_lite.zgesv, that is
the point where numpy calls LAPACK to solve my complex system of
linear equations. Ideally I'd like to parallelize
