Closed hermands closed 9 years ago
HDF5 does not appear to support databases all that well. We can try packing the individual tables into the container but it will need to be reconstituted through a SQL declaration. Please see: http://www.pytables.org/moin/FAQ#IsPyTablesareplacementforarelationaldatabase.3F and this concerning the h5py I am using: http://docs.h5py.org/en/2.3/faq.html#what-s-the-difference-between-h5py-and-pytables
In response to your proposal: FCS subroutines
Sounds good. Histogram can be not in FCS if it is always going to be pushed to HDF5 and it pushes itself. It sounds like we now have two histogram functions (1D and multi-D), but that is probably fine as long as that's all we need.
HDF5 hierarchy /database_info_version /query /case_list /data/"case_tube_idx"/data_array /data/"case_tube_idx"/indices /data/"case_tube_idx"/indptr /data/"case_tube_idx"/shape
HDF5_IO renamed to Feature_IO, new class MergedData_IO inherit similar things such as push and pull dataframes. This now handles IO to two separate HDF5 files with different schemas and properties.
Proposal is to: