"Klemm, Michael" wrote:
> I have found that the numpy.linalg.svd algorithm creates the resulting U,
> sigma, and V matrixes with Fortran storage. Is there any way to force
> these kind of algorithms to not change the storage order? That would
> make passing the matrixes to the native dgemm oper
Dear all,
> -Original Message-
> From: numpy-discussion-boun...@scipy.org [mailto:numpy-discussion-
> boun...@scipy.org] On Behalf Of Sebastian Berg
> Sent: Tuesday, March 31, 2015 9:37 AM
> To: numpy-discussion@scipy.org
> Subject: Re: [Numpy-discussion] How to F
On Di, 2015-03-31 at 07:11 +, Ian Henriksen wrote:
> On Tue, Mar 31, 2015, 12:50 AM Klemm, Michael
> wrote:
>
>
> Dear all,
>
> I have found a bug in one of my codes and the way it passes a
> Numpy matrix to MKL's dgemm routine. Up to now I was assuming
>
On Tue, Mar 31, 2015, 12:50 AM Klemm, Michael
wrote:
> Dear all,
>
> I have found a bug in one of my codes and the way it passes a Numpy matrix
> to MKL's dgemm routine. Up to now I was assuming that the matrixes are
> using C order. I guess I have to correct this assumption :-).
>
> I have fou
Dear all,
I have found a bug in one of my codes and the way it passes a Numpy matrix to
MKL's dgemm routine. Up to now I was assuming that the matrixes are using C
order. I guess I have to correct this assumption :-).
I have found that the numpy.linalg.svd algorithm creates the resulting U,
