Hi Derek,
Can you please run the following command and report back what you see?
python -c "import tables; tables.test()"
Be Well
Anthony
On Mon, Sep 24, 2012 at 10:56 PM, Derek Shockey wrote:
> Hello,
>
> I'm hoping someone can help me. When I specify start and stop values
> for calls to wher
PS When I do this on linux all 5077 tests pass for me.
On Mon, Sep 24, 2012 at 11:09 PM, Anthony Scopatz wrote:
> Hi Derek,
>
> Can you please run the following command and report back what you see?
>
> python -c "import tables; tables.test()"
>
> Be Well
> Anthony
>
>
> On Mon, Sep 24, 2012 at
I ran the tests. All 4988 passed. The information it output is:
PyTables version: 2.4.0
HDF5 version: 1.8.9
NumPy version: 1.6.2
Numexpr version: 2.0.1 (not using Intel's VML/MKL)
Zlib version: 1.2.5 (in Python interpreter)
LZO version: 2.06 (Aug 12 2011)
BZIP2 version:
Hi Derek,
Ok That is very strange. I cannot reproduce this on any of my data. A
quick couple of extra questions:
1) Does this still happen when you set start=0?
2) What is the chunksize of this data set (are you at a boundary)?
3) Could you send us the full table information, ie repr(table).
B
Hi Anthony,
It doesn't happen if I set start=0 or seemingly any number below 3257
(though I didn't try them *all*). I am new to PyTables and hdf5, so
I'm not sure about the chunksize or if I'm at a boundary. I did
however notice that the table's chunkshape is 203, and this happens
for exactly 203
Hello Derek, and devs,
After playing around with your data, I am able to reproduce this error on
my system.
I am not sure exactly where the problem is but I do know how to fix it!
It turns out that this is an issue with the indexes not being properly in
sync with the
original table OR the start
