How to load and plot Slow Control data

How to load SC data

A number of parameters related to the LEGEND hardware configuration and status are recorded in the Slow Control (SC) database. The latter, PostgreSQL database resides on the legend-sc.lngs.infn.it host, part of the LNGS network. To access the SC database, follow the Confluence (Python Software Stack) instructions. Data are loaded following the pylegendmeta tutorial, which shows how to retrieve info from the SC database.

Available SC parameters

Available parameters at the moment include:

  • PT114, PT115, PT118 (cryostat pressures)

  • PT202, PT205, PT208 (cryostat vacuum)

  • LT01 (water loop fine fill level)

  • vmon (Ge diode voltage)

  • imon (Ge diode current)

  • RREiT (injected air temperature clean room), RRNTe (clean room temperature north), RRSTe (clean room temperature south), ZUL_T_RR (supply air temperature clean room)

  • DaqLeft-Temp1, DaqLeft-Temp2, DaqRight-Temp1, DaqRight-Temp2 (rack present temperatures)

  • if you want more, contact us!

These can be easily access for any time range of interest by giving a config.yaml file as input to the command line in the following way:

legend-data-monitor user_scdb --config config.yaml --port N --pswd ThePassword

Note

  • N is whatever number in the range 1024-65535. Setting a personal port different from the default one (5432) is a safer option, otherwise if a port is already in use by another user, you’ll receive an error indicating that the port is already taken and you will not be able to access the SC database;

  • ThePassword can be found on Confluence at this page.

An example of a config.yaml file is the following:

output: output_folder
dataset:
  experiment: L200
  period: p09
  version: tmp-auto
  path: /data2/public/prodenv/prod-blind/
  type: phy
  time_selection: ...   # Replace '...' with actual time selection details
saving: overwrite
slow_control:
  parameters:
    - DaqLeft-Temp1
    - ZUL_T_RR

The meaning of each entry is explained below:

  • output: output folder path;

  • dataset:

    • experiment: either L60 (to be checked) or L200

    • period: period to inspect

    • version: prodenv version (eg tmp-auto or ref-v1.0.0)

    • path: global path to prod-blind prodenv folder

    • type: type of data to inspect (either cal or phy)

    • time selection: check how to build a config file to see available options for this entry

  • saving: option is available to either "overwrite" any already present output file (or create a new one if not present) or "append" new data to the previously obtained output files

  • slow_control: entry for specifying SC parameters

    • parameters: list of parameters to retrieve

Note

In principle, for plotting the SC data you would need just the start and the end of a time interval of interest. This means that SC data does not depend on any dataset info (i.e. on entries experiment, period, version, type). However, these entries are important to retrieve any channel map of interest for the given time range of interest.

We store SC data in the following way:

<output_path>/
    └── <version>/
        └── generated/
            ├── plt/
            │    └── hit/
            │        └── <type>/
            │            └── <period>/
            │                └── <time_selection>/
            │                    └── <experiment>-<period>-<time_selection>-<type>-slow_control.hdf
            └── tmp/
                └── mtg/
                    └── <period>/
                        └── <time_selection>/
                            └── <experiment>-<period>-<time_selection>-<type>.log

Note

The accessible Slow Control database is scdb. For databases with previous deployment data, scdbL140 or scdbL60 with data from the 142 kg or 60 kg campaign, respectively, will be automatically retrieved based on the period you want to inspect.