>From what I understand, netCFD is based on on HDF5, at least as of the
version 4 release.
On Mon, May 25, 2009 at 19:19, Eric Firing wrote:
> Francesc Alted wrote:
>> A Monday 25 May 2009 00:31:43 David Warde-Farley escrigué:
>>> As Robert's design document for the NPY format says, one option wo
Ok, I understand that my thought on making hdf5 the standard save/load
format for numpy was a bit naive. If it would have been easy it would
already have been done. Thanks for the insights Robert.
Well anyhow, I will continue with my little module and see where it
goes. I will start a new thread i
alizing it?
/Albert
On Sat, May 23, 2009 at 13:47, David Warde-Farley wrote:
> On 23-May-09, at 5:36 AM, Albert Thuswaldner wrote:
>
>> So i guess in the long term i have to also add pickling support. In
>> the short term i will add warnings for the data types that are not
>>
Thank you pauli for your input. I agree with you that our projects
have different goals, even if they touch on the same subject.
The goal of pyhdf5io is to provide a very simple interface, so that
the user can save his/her data. The reasone for picking hdf5 was of
course also to enable the use of t
On Thu, May 21, 2009 at 22:38, David Warde-Farley wrote:
> Hi Albert,
>
> So this is a wrapper on top of PyTables to implement load() and
> save()? Neat.
Yes, you got the idea. in its most simplest form you can type:
hdf5save()
And all your local variables are saved to a file with the default
Dear list,
I'm writing this because i have developed a small python module that might
be of interest to you the readers of this list:
http://code.google.com/p/pyhdf5io/
It basically implements load/save functions that mimic the behaviour of
those found in Matlab, ie with them you can store
