Re: [Pytables-users] [POLL] Fully Adopt PEP8 Proposal - Please respond!

2012-07-25 Thread Richard Llewellyn
+1 I'm already making the 2 to 3 transition, so have left pytables for awhile ;[. It's great news that the next version will be py3k compatible! Style change will be a good thing as far as I'm concerned. On Wed, Jul 25, 2012 at 12:39 PM, Andre' Walker-Loud wrote: > +1 > > while it will be painf

Re: [Pytables-users] using vlarray

2009-12-12 Thread Richard Llewellyn
I'll join in the guessing game. This looks, in part, a way to store a huge multiple sequence alignment with a reference sequence (the first character in ( ) being the DNA base in a reference DNA molecule, but due to the inequal lengths in each VLA, it would seem that gaps are not stored, or stored

Re: [Pytables-users] speed of selecting from table vs numpy.where with array

2009-07-01 Thread Richard Llewellyn
Oops. I thought I was reading the array off disk for the speed test, but apparently the array was already in RAM. Changing this so that I read the array, eg where(a[:] == id), takes about the same time as searching for the id value in a table. Sorry about that. Rich ---

[Pytables-users] speed of selecting from table vs numpy.where with array

2009-07-01 Thread Richard Llewellyn
I've been finding pytables useful for organizing big genomics data (e.g. storing and querying ~200 Gb all vs all uniparc smith-waterman hits from Uniprot). One thing that has surprised me a little: I was interested in the efficiency of querying small tables storing an index (integer) and an integ