Hi,
`np.nonzero` for a 2D array `A` returns:
row_inds, col_inds = np.nonzero(A)
I notice that `row_inds` appears to be sorted by value, and `col_inds`
appears to be sorted by value, within each row.
Is this a guarantee of the `np.nonzero` function? If not, does this
function guarantee any
Hi Jason,
As I understand numpy has been set up to mirror C-structs as long as you
use the 'align' flag. For example, your struct can be represented as
np.dtype('f8,f4,i4,u8', align=True)
(assuming 32 bit floats). The offsets of the fields should be exactly
the offsets of the elements
Chris Barker chris.bar...@noaa.gov wrote:
we get away with np.float, because every OS/compiler that gets any regular
use has np.float == a c double, which is always 64 bit.
Not if we are passing an array of np.float to a ac routine that expects
float*, e.g. in OpenGL, BLAS or LAPACK. That will
On Sun, Jul 26, 2015 at 11:19 AM, Sturla Molden sturla.mol...@gmail.com
wrote:
we get away with np.float, because every OS/compiler that gets any
regular
use has np.float == a c double, which is always 64 bit.
Not if we are passing an array of np.float to a ac routine that expects
float*,
Hi everyone,
I have encountered an initially rather confusing problem in a piece of
code that attempted to symmetrize a matrix: `h += h.T`
The problem of course appears due to `h.T` being a view of `h`, and
some elements being overwritten during the __iadd__ call.
What made it nasty is that it
Chris Barker chris.bar...@noaa.gov wrote:
32 bits on all (most) 32 bit platforms
64 bits on 64 bit Linux and OS-X
32 bits on 64 bit Windows (also if compiled by cygwin??)
sizeof(long) is 8 on 64-bit Cygwin. This is to make sure it is inconsistent
with MSVC and MinGW-w64, and make sure there
On 27/07/15 22:10, Anton Akhmerov wrote:
Hi everyone,
I have encountered an initially rather confusing problem in a piece of
code that attempted to symmetrize a matrix: `h += h.T`
The problem of course appears due to `h.T` being a view of `h`, and
some elements being overwritten during the
