Participants

Harald Bräuning, Udo Krause, Dominic Day, Peter Kainberger, Matthias Wiebel, Hanno Hüther, Raphael Müller, Barbara Grasmück, Alexander Schwinn (meeting minutes)

Topics

• "STANDBY" as setting value for the value-item "power" (enum DEVICE_STATUS)
  • Required by a specific cosylab FESA-class were "standby" can be actively set.
  • To generally introduce "STANDBY" would cause effort for all existing classes
  • Solution:
    • If a class supports "STANDBY". Only for this class the enum "DEVICE_STATUS" can be extended.
    • A paragraph in the FESA-Guideline, to handle this case will be added.
    • Rules will be established to check the enum "DEVICE_STATUS" in the design-document.
    • The enum-value should be the same than for "STANDBY" in the enum "DEVICE_POWER_STATE" which is used for acquisition.
• Introduction of a property to show the status of components(modules) which are required to run a FESA-class
  • In case of an error, the user wants to be able to quickly see if all required hardware/software modules are available and working
  • The solution on which all agreed:
    • new custom-type "MODULE_STATUS"
      • First 128 values reserved for GSI-conventions, all others can be user-specific
      • ok / warning / error / notAvailable
    • new Property, e.g. "GSI-module-status"
      • provides a custom-type-array named "moduleStatus" which uses MODULE_STATUS
      • provides a string-array named "moduleStatus_labels" to name the items in "moduleStatus"
    • new value-item in GSI-Status-Property, named "modulesOk".
      • If possible, it will automatically be linked to the items of "moduleStatus" and show the overall-state
    • Add to GSI-FESA-Guideline
      • If any special hardware/software module is required for a fesa-class to operate correctly, the status of this module should be shown in "GSI-module-status".
      • If the WR-Timing receiver is used, it's status should be registered in "GSI-module-status" with a predefined label-name(concrete name to defined)
• Misc
  • It should not be needed any more to use the application-argument -WR .. instead an explicit argument for using CERN timing should be required. WR-Timing should be the default

If you think these meeting minutes are incomplete/wrong, please feel free to extend them !