Skip to main content

Installing HDF5

HDF5 is a data file format specification with some opensource libraries. Matlab version 7.3 and above are supposed to store data in this format. You can load these files into Python using the h5py library.

IMPORTANT:
  1. Due to an incompatibility with HDF5 1.8.5 h5py tests (and operation) will fail. Using 1.8.4 or earlier should resolve the issue. (issue 124)
  2. When installing h5py  change to super user account (su) rather than sudo because you need some environment variables to be set during the installation
Install HDF5 on your machine

Following instructions from http://www.hdfgroup.org/ftp/HDF5/current/src/unpacked/release_docs/INSTALL

  1. grab the bz2 file
  2. ftp://ftp.hdfgroup.org/HDF5/prev-releases/hdf5-1.8.4-patch1/src/hdf5-1.8.4-patch1.tar.bz2
  3. bunzip2 hdf5-1.8.4-patch1.tar.bz2
  4. tar -xvf hdf5-1.8.4-patch1
  5. cd hdf5-1.8.4-patch1
  6. ./configure --prefix=/usr/local/hdf5
  7. make
  8. make check
  9. sudo make install
  10. make check-install
Install h5py

  1. su
  2. export HDF5_DIR=/usr/local/hdf5/
  3. export HDF5_API=18
  4. easy_install h5py
How to recover if you did use HDF 1.8.5:
  1. Download, compile and install the correct version of HDF (as above)
  2. Get rid of the h5py egg compiled against this by doing:
    sudo easy_install -m h5py to get rid of paths etc.
    rm -r /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/h5py-1.3.0-py2.6-macosx-10.3-fat.egg (or where ever your egg is, to get rid of the compiled version)
  3. reinstall
  4. run tests to be sure
    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    A note on Python's __exit__() and errors

    Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
    Post a Comment
    Read more

    Store numpy arrays in sqlite

    Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
    Post a Comment
    Read more