Metadata and data model for muon calibration

Summary

Metadata model

Here I present first draft of reference metadata model for the optical throughput calibration using muons in yaml format

CTA:
   METADATA:
      VERSION: 1.0.0
   CONTACT:
      ORGANIZATION: DPPS 
      NAME: ?
      EMAIL: ?
   PRODUCT:
      DESCRIPTION: Absolute optical_efficiency coefficient
      CREATION TIME: 2024-01-01 00:00
      ID: TBD
      DATA CATEGORY: B
      DATA LEVEL: 
      DATA ASSOCIATION: Telescope
      DATA TYPE: Monitoring
      DATA MODEL NAME: calibpipe-optical-eff
      DATA MODEL VERSION: v0.1
      FORMAT: ecsv
   PROCESS:
      TYPE: Acquisition
      SUBTYPE: Observation
      ID: obs_id
   ACTIVITY:
      NAME: Optical Throughput Calibration
      TYPE: Muon Calibration
      ID: TBD
      START: 2024-01-01 00:01
      END: 2024-01-01 00:02
      SOFTWARE NAME: calibpipe
      SOFTWARE VERSION: 0.1
   INSTRUMENT:
      SITE: CTA-North/CTA-South
      CLASS: telescope
      TYPE: LST/MST/SST
      SUBTYPE: 
      ID:

Open questions to metadata model:

• What format we choose for result table (ecsv, fits, hdf5 etc)
• Name and email in CONTACT field

Data model

title: Schema for absolute optical_efficiency coefficient
version: 0.1.0
name: optical_efficiency
description: Optical efficiency for each telescope calculated using different methods.


data:
    - type: datatable
      table_columns:
        - name: tel_id
          description: Telescope description
          required: true
          type: int
        - name: obs_id
          description: Observation description
          required: true
          type: int
        - name: validity_start
          description: Lower time boundary of optical efficiency validity
          required: true
          type: datetime
        - name: validity_end
          description: Upper time boundary of optical efficiency validity
          required: true
          type: datetime
        - name: opt_eff_coeff
          description: Mean of the calculated optical efficiency over the validity time range
          required: true
          type: float
          allowed_range:
             min: 0.0
             max: 1.0
        - name: opt_eff_std
          description: Standard deviation of calculated mean optical efficiency 
          required: true
          units: dimensionless
          type: float
        - name: method
          description: Method for optical efficiency calculation
          required: true
          type: string

instrument:
    class: Telescope
    type:
       - LST
       - MST
       - SST

Open questions to the data model:

• For data model I was following the schema template from SimPipe schemas - should we mention this or should we create our own base_schema template?

Here comes the first draft of the DB schema: