Measurement Groups
Hey @sebastien.petitdemange @tiago.coutinho @alejandro.homs @papillon :)
Here is a small recap of what we said during the meeting.
The idea behind a MeasurementGroup
is that it is used when doing ct
or for a default scan (ascan, dscan, timescan, etc), to know what to record, e.g. it is used to build the internal Acquisition Chain for the scan.
TODO (or to check if it's agreed or done):
-
Measurement
class to be renamed toMeasurementGroup
-
MeasurementGroup
objects are created in yml config files, independently of any session; measurement groups can be shared across sessions -
a session will hold a list of measurement groups -
there is only one active measurement group at a time ; set_active()
function to be implemented somehow -
each MeasurementGroup
has one or more contexts ; there is a default context that has all underlying counters (defined in yml file) -
within a context, counters are enabled by default -
a MeasurementGroup
configuration (yml) can have aninclude
parameter, than gives a list of existing measurement groups; this is to compose a measurement group from others -
Measurement group contexts are stored in Redis, this allows to enable/disable counters on the fly while keeping it persistent
Question: is there a default measurement group in a session, even if it is not defined in yml config ? Or not ?