A Dimarts 01 Agost 2006 22:25, Stefan Kuzminski va escriure:
> Indeed, when I set complevel parameter in the Filters constructor to 0,
> the problem goes away, ( toggling the shuffle buffer did not effect the
> problem ). The error appears with either zlib or lzo compression. I
> will see about d
Indeed, when I set complevel parameter in the Filters constructor to 0,
the problem goes away, ( toggling the shuffle buffer did not effect the
problem ). The error appears with either zlib or lzo compression. I
will see about duplicating outside our app.
S
--- Francesc Altet <[EMAIL PROTECTED]
A Dijous 20 Juliol 2006 17:47, Stefan Kuzminski va escriure:
> I reproduced this stack trace with HDF5 v1.6.5 and also with
> v1.8.0-alpha4 ( both with pytables-1.3.2 ). Here is the most
> mysterious part, I can get the program to run successfully if I round
> the values I am setting in the HDF5 t
I reproduced this stack trace with HDF5 v1.6.5 and also with
v1.8.0-alpha4 ( both with pytables-1.3.2 ). Here is the most
mysterious part, I can get the program to run successfully if I round
the values I am setting in the HDF5 to <10 places of precision, if I
leave them unrounded, or round them t
Hi Stefan,
Looking at the trace and your description it seems that the error could
be at the core of the HDF5 library, but can't be entirely sure until we
can reproduce the problem. It should be nice if you can try HDF5 1.6.5
or even 1.8.0 alpha4 (recently announced a couple of days ago).
If usin
En/na Stefan Kuzminski ha escrit::
> Hi, after looking at this stack trace for the last 2 days, I'm starting
> to lose it. I have an application that does a bunch of manipulation to
> the hdf5 ( read, write, add new tables, read again ) and it generates
> the stack trace below. [...]
Humm, I'm
Hi, after looking at this stack trace for the last 2 days, I'm starting
to lose it. I have an application that does a bunch of manipulation to
the hdf5 ( read, write, add new tables, read again ) and it generates
the stack trace below. Unfortunatly I can't duplicate the error
outside the applicat
