evedata.measurement subpackage
An interface towards measurements.
Generally, the measurement subpackage,
as mentioned already in the Concepts section, provides the
interface towards the “user”, where user mostly means the evedataviewer
and radiometry packages. However, besides these two Python packages,
human users will want to use the evedata package as well. Hence,
it should be as human-friendly as possible.
What is the main difference between the evefile and
the measurement subpackages? Basically,
the information contained in an eveH5 file needs to be “interpreted” to
be able to process, analyse, and plot the data. While the evefile subpackage provides the necessary data structures to
faithfully represent all information contained in an eveH5 file,
the measurement subpackage provides the result
of an “interpretation” of this information in a way that facilitates data
processing, analysis and plotting.
However, the measurement subpackage is still
general enough to cope with all the different kinds of measurements the eve
measurement program can deal with. Hence, it may be a wise idea to create
dedicated dataset classes in the radiometry package for different types
of experiments. The NeXus file format may be a good source of inspiration
here, particularly their application definitions. The
evedataviewer package in contrast aims at displaying whatever kind of
measurement has been performed using the eve measurement program. Hence it
will deal directly with Measurement (facade) objects
of the measurement subpackage.
As each functional layer, the measurement subpackage consists of three technical layers – boundaries, controllers, entities –, each in their individual subpackage: