It looks like some of the problem I was seeing has to do with reading in
hdf5 files from matlab that contain strings for column types. when they
are read in using h5py the type is reported as 'O' which is object. The
problem is I can't reproduce the problem in small script because I can't
get
On Fri, 2017-05-12 at 16:28 +0200, Jens Jørgen Mortensen wrote:
> Den 11-05-2017 kl. 03:48 skrev Charles R Harris:
> > Hi All,
> >
> > I'm please to announce the NumPy 1.13.0rc1 release. This release
> > supports Python 2.7 and 3.4-3.6 and contains many new features. It
> > is one of the most
On 12.05.2017 16:28, Jens Jørgen Mortensen wrote:
> Den 11-05-2017 kl. 03:48 skrev Charles R Harris:
>> Hi All,
>>
>> I'm please to announce the NumPy 1.13.0rc1 release. This release
>> supports Python 2.7 and 3.4-3.6 and contains many new features. It is
>> one of the most ambitious releases in
Den 11-05-2017 kl. 03:48 skrev Charles R Harris:
Hi All,
I'm please to announce the NumPy 1.13.0rc1 release. This release
supports Python 2.7 and 3.4-3.6 and contains many new features. It is
one of the most ambitious releases in the last several years. Some of
the highlights and new
I was able to fix my problem. One of the types in the recarray was of type
object when it should have been S27. Type object was the result of reading
in a matlab generated hdf5 file which had a string for one of the matrix
columns. I converted this column manually to a S27.
I am reverting my
