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,
On Mon, Mar 30, 2015 at 3:59 PM, Allan Haldane
wrote:
> Hello everyone,
>
> What does the list think of renaming the arguments of np.clip and np.put
> to match those of ndarray.clip/put? Currently the signatures are
>
> np.clip(a, a_min, a_max, out=None)
> ndarray.clip(a, min=None, max=No
Hello everyone,
What does the list think of renaming the arguments of np.clip and np.put
to match those of ndarray.clip/put? Currently the signatures are
np.clip(a, a_min, a_max, out=None)
ndarray.clip(a, min=None, max=None, out=None)
np.put(a, ind, v, mode='raise')
ndarray.put(i
On Sun, Mar 29, 2015 at 7:39 PM, Blake Griffith
wrote:
> I have an open PR which lets users control the checks on the input
> covariance matrix. The matrix is required to be symmetric and positve
> semi-definite (PSD). The current behavior is that NumPy raises a warning if
> the matrix is not PSD,
Hi Jerome,
> -Original Message-
> From: numpy-discussion-boun...@scipy.org [mailto:numpy-discussion-
> boun...@scipy.org] On Behalf Of Jerome Kieffer
> Sent: Friday, March 27, 2015 8:41 PM
> To: numpy-discussion@scipy.org
> Subject: Re: [Numpy-discussion] ANN: pyMIC v0.5 released
>
> Inte
