Draft: Ensure the consistency of DataSet when reading from a file
DataSet could end up in an inconsistent state depending on the order of execution (e.g., the nr of frames or the metadata could be invalid).
To avoid such an inconsistency, the classes
IDataReader (as well as its derived classes),
DataSet are disentangled. The instrument-related methods and variables (like
computeQ) are moved to
MetaData is stored only in
DataSet (to avoid duplication in
IDataReader). Hence, a data-reader accepts a pointer to a
DataSet and stores the acquired data in the
DataSet (as the sole data container). The
DataSet metadata are updated as soon as the required data is available.
- The duplicate HDF5 exporter,
DataSet::saveHDF5, is discarded. HDF5 output is solely produced by the ExperimentExporter module.
- Adding unrecognized metadata keys will result in a warning in the log file.
RawDataReaderparameters include the name for the
DataSet; name duplication is checked in
RawDataDialog::verifyand the user is warned via a
BaseHDF5DataReaderfor proper naming.
- Retired unused modules
- Code and comments are improved.