Participants

Topics

• Proposals to address beam-processes via cycle-selector
  • After some longer discussion we found out the following:
    • We dont want to use the cycle-selector for indexing. Instead, either specific value-items or filter-items will be used in order to index specifix beam-processes. ( more flexibility )
    • We want to be able to use indexing per beam-process only for some specific fields of some specific classes --> The developer has to use arrays for BP-Indexing. Fesa-core-gsi will only provide helper-methods to obtain an array-id for a specific beam-process-id. (Mapping)

• Current-State DB-Integration at GSI
  • The DB-Team at CERN created a Jira-Issue in order to track the work which has to be done to port the DB-services to GSI:
    • FESA-4399 Provide a version of the Controls Configuration Service (db, views, triggers, packages, PL/SQL and Java APIs) supporting the FESA framework to GSI
  • This issue (and it's sub-issues) is planned to be finished in the mid of october.
  • After that, DB-work at GSI could be started

• FESA-Guideline Properties "Acquisition" and "Setting" as optional
  • Currently we enforce for each GSI-FESA-Class that there is a property, named "Acquisition" and a property named "Setting". These propertys should carry all relevant information for the daily operating.
  • Recently we found out that this concept just does not work for some classes (RGA, stepmotor-control)
  • We agreed on removing the enforcement of the two properties and making them optional.
  • However if it is possible for class, the properies should be used.
  • The properties will still be available in the GSI-Template (opt-out)

• Pre-defined value-item to describe data-precision for acquisition-data
  • The idea is to have some predefined naming which can be used as standard for all devices giving information about the data-precision
  • E.g. for the field "voltage" we could have the meta-field "voltage_precision".

• HW-Address-field
  • At CERN this configuration-field is used by class-developers to e.g save slot-, name-, port- and channel-information
  • The infrmation will be available in the FESA-DB. There are some DB-tools in order to search for a specific hardware which make use of the HW-address-field
  • The Component-DB at GSI will have the same purpose, so we dont need to force our class-developers to use this type of field.
  • ANyhow the developers will now check the usibility of the field-type.

• JAPC + value-items with _min/_max
  • The topic will not be treat today, since both LSA developers are not available today (needed for this discussion)