Participants

Topics

• *Re-discussion "detailedStatus"
  • The proposal from the last FE-Int meeting caused some implementation-problems (usage of same field for acquisition- and configuration-data). So we needed to re-discuss the design.
  • 3 new proposals were presented Alexander Schwinn
  • In the end all agreed on the following concept:
    • acq-field: "detailedStatus" - array of bool ( like it is in v1.0.0 )
    • config-field "detailedStatus_severity" - array of enums
    • the enum-values will be
      • 0 - INFO
      • 1 - WARNING_ON_FALSE
      • 2 - ERROR_ON_FALSE
      • ( all others are reserverd )
  • reasoning for this descision:
    • Clear separartion between acquisition and configuration data
    • Possibility to differ between info, warning and error ( future-proof )
    • Good C++ API / no additional complexity for the class-developer ( int8_t approach )