DUECA/DUSIME
|
metafunctor to access DCO HDF5 facilities. More...
#include <HDF5DCOMetaFunctor.hxx>
Public Member Functions | |
HDF5DCOMetaFunctor () | |
Constructor. | |
~HDF5DCOMetaFunctor () | |
Destructor. | |
virtual const H5::DataType * | operator() () |
Get a HDF5 datatype; not always defined! | |
virtual HDF5DCOWriteFunctor * | getWriteFunctor (std::weak_ptr< H5::H5File > file, const std::string &path, size_t chunksize, const std::string &label, const dueca::DataTimeSpec *startend, bool compress=false, bool writeticks=true)=0 |
Get an arrayed HDF5 channel reading & file writing functor. | |
virtual HDF5DCOReadFunctor * | getReadFunctor (std::weak_ptr< H5::H5File > file, const std::string &path, bool readticks=true)=0 |
Get an HDF5 channel writing & file reading functor. | |
Public Member Functions inherited from dueca::DCOMetaFunctor | |
DCOMetaFunctor () | |
Constructor. | |
virtual | ~DCOMetaFunctor () |
Destructor. | |
metafunctor to access DCO HDF5 facilities.
Two modes of interaction
Get a functor for reading a channel and writing the data into hdf5 format. This creates an hdf5 dataset for each variable in the DCO object. Again, limitations apply, the variables may not be dco objects for which a datatype cannot be obtained as described above. The hdf5 datasets are written as follows:
|
pure virtual |
Get an arrayed HDF5 channel reading & file writing functor.
file | HDF5 file on which to write |
path | Base path for writing the data. |
chunksize | Size of data chunks. |
label | Label to be written to the file |
startend | Pointer to a time spec controlling run/pause in logging |
compress | You can guess |
writeticks | If true, time is also logged |
|
pure virtual |
Get an HDF5 channel writing & file reading functor.
file | HDF5 file from which to read. |
path | Base path for reading the data. |
readticks | If true, time also read from the file |