Skip to main content

An efficient way to store pandas data

OK, after much belly aching I have a decent work flow for when I want to use Pandas which is actually quite convenient. Firstly, Pandas shines for when I have heterogeneous data (mixed types) that form nicely into columns and where I need to select out a subset of rows because they satisfy certain conditions.

UPDATE: Fixed confusion between 'table' and 'store'
UPDATE: Include note about how to set data columns

The basic steps are these
  1. Use table=True in .put or .to_hdf to indicate that you want the data stored as a frame_table that allows on-disk selection and partial retrieval
  2. Use data_columns= [...] during saving to identify which columns should be used to select data
You need to do BOTH steps to have a working selectable-table-on-disk.
  • If you do not use table=True you will get TypeError: cannot pass a where specification when reading from a non-table this store must be selected in its entirety
  • If you do not declare data_columns you will get ValueError: query term is not valid [field->...,op->...,value->...]

import pandas as pd

store = pd.HDFStore('filename.h5')

df = pd.DataFrame( ... ) #Construct some dataframe
#Save as a frame_table in filename.h5 and declare some data columns 
#append creates a table automatically 
store.append('data1', df, data_columns=[...]) 

#
df = pd.DataFrame( ... ) #Construct another dataframe 


#Put requires an explicit instruction to create a table


store.put('data2', df, table=True, data_columns=[...]) #This is convenient - it now adds a second node to the file 


 


 

Now you can use the battery of select methods (outlined here) to load just selected parts of the data structures. 












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




























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