Skip to main content

Loading matlab binary (.mat) files into python

It happens. You have old data in matlab .mat format or your colleagues insist, for some obscure reason, on using MATLAB. You need scipy.io.loadmat and scipy.io.savemat from scipy.

import scipy.io
X = scipy.io.loadmat('mydata.mat')

X now contains a dictionary whose keys correspond to the variable names saved in the original mat file.

UPDATE:
Nested dictionaries seem to be a problem. A kind soul has a short set of methods that converts nested dictionaries here.

UPDATE:

Look here (scipy cookbook) for how to handle mat files from recent versions of matlab
Labels:

Comments

  1. CamillaJune 12, 2009 at 3:51 AM

    Hi,
    Loved this trick:)

    ReplyDelete
  2. AnonymousOctober 31, 2009 at 9:53 PM

    thanks! it's very useful

    ReplyDelete
  3. AnonymousJanuary 10, 2010 at 2:52 AM

    Very useful, thanks

    ReplyDelete
  4. AnonymousJuly 23, 2010 at 1:43 PM

    Doesn't read Matlab 7.3 files. It complains and suggests using the HDF reader.

    ReplyDelete
  5. Kaushik GhoseJuly 26, 2010 at 8:28 AM

    Hi,

    Thanks for pointing that out! From the cookbook (http://www.scipy.org/Cookbook/Reading_mat_files) I see that they suggest using PyTables or h5py packages.

    ReplyDelete
  6. NicolauAugust 8, 2010 at 12:48 PM

    Thank you so much! I love to find out something like that is actually extremely easy. :)

    ReplyDelete

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

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more