Handling of Cat-A calibration data

After discussion with ACADA and DPPS team and with the TCU team we plan to implement the following solution (as first step):

1- all LST-1 calibration data (drs4 corrections and dc_to_pe) are considered ad service data

2- we introduce in the data-base a new document (e.g. CalibrationServiceSet) which includes the calibration_service_id (uint64) and the list of file paths necessary for the waveform calibration in the EvB

3- This document is updated each time one of the files is updated

4- Whenever TCU needs, it queries the calibration database for the last CalibrationServiceSet and retrieve the info to be sent, via Caco, to the EvB :

• calibration_service_id
• calibration file path
• drs4 correction path (we plan to collect all drs4 data in one single file)

5-EvB will write the calibration_service_id in the R1 CameraConfiguration, which will allow to find the applied calibrations through a query to the calibration DB

The above scheme is compliant with the present R1 data model, and it will allow to proceed with the implementation of R1 calibration inside the EvB

This scheme however does not permit an easy solution for the access to the calibration files by ACADA/DPPS. Discussion are starting between LST, DPPS and ACADA in order to define a final solution associated eventually to a change of the R1 data model (see issue).