Participants

Topics

• Naming for bits of the "detailedStatus" (int8_t)
  • We agreed on the following:
    • bit0 = TRUE/FALSE ( FALSE always has to be 0 --> Guideline )
    • bit1 = IS_ERROR_BIT ( If flagged, the state FALSE of bit 0 will signal an error )
    • Alex will provide a method to only set bit0 during runtime, and to read bit1 from the instance-file, if possible.

• Naming for Timing value-items
  • statusTiming
    • The property "Status" will have a value-item "statusTiming" ( was "statusTimingReceiver" before )
    • This item should show if the timing is ok for the class ( not only the status of the timing-receiver itself )
    • --> Item possibly can be merged with others. See Status-Conventions for connected Hardware
  • deviceNameTimingReceiver
    • This value-item wil be part of a new GSI-specific property, named "DeviceDescription"
    • The property will be a device-specific acquisition-property
    • The property will as well have the following value-items:
      • propertyNames (2D char array)
      • deviceNames (2D char array)
      • globalDeviceName (char array)
      • host (char array)

• Schedule for the next releases
  • CERN is going to freeze the FESA RDA3 integration. The reason for that is, that the schedule is too tight. The first integration-tests at the end of LS1 are going to start soon.
  • --> Consequence: At GSI we will not use rda3 for the MCS.
  • Ralph Baer asked for a FESA-release end of November.
    • This release should run the most recent changes of the status-property (see Naming for bits of the "detailedStatus" (int8_t) )
    • The GSI trunk-version of fesa will be used for release (currently this is v1.1.1 )

• Status-Conventions for connected Hardware
  • In order to have a unified way to display hardware stati
  • Proposal:
    • Additional value-items in the property "Status"
    • "moduleStatus" ( array of enums, enum values 0..128 reserved, everything above user-specific )
    • "moduleStatus_labels" ( array of strings, names of the modules in "moduleStatus" )
  • Propsal needs to be discussed/agreed with the AP-Team ! --> next FE-Int meeting
  • This proposal would make the value-item "statusTiming" obsolete !
  • Add to Guideline: A FESA-class as well needs to start/run if the state of the connected hardware is faulty ( in order to show this state in "moduleStatus" )