On Dec 30, 2011, at 8:40 AM, Francesc Alted wrote:
> 2011/12/30 Gael Varoquaux :
>> Hi list,
>>
>> I am trying to do a simple comparison of various I/O libraries to save a
>> bunch of numpy arrays. I don't have time to actually invest in PyTables
>> now, but it has always been on my radar. I want
As of 2009, I don't think this functionality was supported. You can look here
for one solution "I always recommend":
http://www.mail-archive.com/pytables-users@lists.sourceforge.net/msg01207.html
If you store separate vlarrays for each trial, you can keep metadata on those
vlarrays (guaranteed
NOTE - this has nothing to do with the ongoing soft / external
reference thread.
I'd like to have some large, heterogeneously sized arrays in my hdf5
file, and refer to them from within a table (can't put them in the
table easily, as I want to accomodate very different sized, even maybe
di
(Fernando, please forward this to anyone that you think might care /
help!)
I suspect you're not aware of Fernando's DataArray object, which is an
implementation of named axes on a numpy array, but you can find his
slides about it here:
https://cirl.berkeley.edu/fperez/talks/0908_scipy_data
I'm pretty sure something like this has come up before on the list,
but I figured I'd go for one more ping on it... I'm having some
crashing with PyTables, and the result looks like the text below my
signature... Is there simply no way to have a traceback to the
relevant python code?
Dav
On May 21, 2009, at 5:54 PM, David Warde-Farley wrote:
> On 21-May-09, at 8:21 PM, Dav Clark wrote:
>
>> for i in range(1):
>> f.createArray('/', 'array%d' % i,
>> np.random.random(np.random.random_integers(10)))
>
> I may be wr
ample highlighted someplace. (Perhaps it is and I just missed
it. I looked around quite a bit, though.)
Do you know if it is possible to attach attributes to the array? I
have just a few other scalars that I'd love to bundle up it.
-robert
On May 21, 2009, at 6:21 PM, Dav Clark wrote:
I feel like this is the same (only?) message I always send to people
on the list...
Have you considered simply storing each item as a separate atomic
array? Then you don't need to mess with any of this VLArray stuff, or
tables at all. I know it's called PyTables, but you can actually get
the single table
take about 10 seconds. So, that's tolerable for now.
I guess I could also go to a "file hierarchy" structured "database"
... I forget the standard linux directory file limit. But, I'm pretty
happy with pytables.
Thanks again,
Mark
On Sun, Ap
help you index them better.
Searching on a column then becomes a simple matter of searching on each
of the tables in 'tuples', which will be considerably faster than the VL
/ ObjectAtom approach. There are a number of ways to get a group's
children - I like
pytablesfile.root...t
is just as easy to set the File-level metadata to fix this - so maybe
this is finally your way to coerce me into doing this with my plain
HDF5...
So, both of these are small, easy to work with issues. Not even
bugs. But opportunities for (IMHO) improvement.
Thanks
Well, I've gotta say that you guys have been doing a great job finding what seem to be some very subtle bugs! In recognition of that - here is yet another that I've found!I've only tested the following so far on OS X - there is some similarity with my previous problem getting Unsupported types, so
code in any Python SCM system.
--
Dav Clark
@Stanford / Wandell Lab
917-544-8408
))<>((
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live
atlab (matlab can't delete
things from HDF5 - indeed, it can only write things that are not already
there, no changes at all)... bleh.
Cheers,
--
Dav Clark
@Stanford / Wandell Lab
917-544-8408
))<>((
---
This SF.Net email is spon
system goes into production...
corruption of the central repository would be terrible!
Cheers,
--
Dav Clark
@Stanford / Wandell Lab
917-544-8408
))<>((
HDF5-DIAG: Error detected in HDF5 library version: 1.6.5 thread 3086534336.
Back trace follows.
#000: H5Dio.c line 499 in H5D
On Wednesday 22 March 2006 03:35, Francesc Altet wrote:
> El dg 19 de 03 del 2006 a les 11:38 -0800, en/na Dav Clark va escriure:
> > Generally, if you keep everything simple - strings, basic arrays and
> > scalars, matlab and pytables both read things fine. However, you
> &g
manual on how to properly set
metadata for things like hdf5 compounds and such, so that pytables
will read them. PyTables default behavior with things like compounds
is not very robust at this point (so far as I can tell - it won't
read them without proper metadata
eems a little confusing,
and probably not as efficient...
Any advice on this would be great!
Thanks,
Dav Clark
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. At
18 matches
Mail list logo