Database (2)

How to organise it all?

• Module objects (CtrlModule and/or DaqModule) get passed a single ModuleDbInfo (subclass) object at initialisation.
• CtrlModule objects also get passed the RunType object at each run state transition (at least for those after the run type is definitely known).
• ModuleDbInfo could be composed of several other objects:
  • the online configuration database information (ConfdbModule)
  • a default calibration object for the module, which may be updated by the run controller behind the scenes
  • possibly also run parameters for the module?
• The RunType object contains the general run parameters.
• Maybe module specific run parameters come this way too (instead of the ModuleDbInfo object?) which would ensure they couldnt be used before the run type was fixed.