Skip to content

TrigCost: Save deadtime and pileup per lumiblock range

Aleksandra Poreba requested to merge aporeba/athena:trp-in-costpostproc into 22.0

Save to cost metadata deadtime and pileup per lumiblock range during the Cost Postprocessing. This option should be primarily used for processing the P1 data.

First, the function will read the lumiblocks that were processed in the range (first and last range can be incomplete: for example for Lb_00100 can include lb 110-149). Then it will read start and stop timestamps from COOL database. Last, it will read the average deadtime, average, min and maximum pileup from TRP by the pbeast library.

Example:

    {
      "LumiblockDetails": {
        "LumiBlock_00100": {
          "avgPileup": 42.869,
          "deadtime": 0.131,
          "maxPileup": 45.278,
          "minPileup": 41.241
        },
        "LumiBlock_00150": {
          "avgPileup": 49.892,
          "deadtime": 0.077,
          "maxPileup": 54.551,
          "minPileup": 44.895
        },
        "LumiBlock_00200": {
          "avgPileup": 53.286,
          "deadtime": 0.1,
          "maxPileup": 54.302,
          "minPileup": 52.004
        },
        "LumiBlock_00250": {
          "avgPileup": 53.02,
          "deadtime": 0.108,
          "maxPileup": 54.917,
          "minPileup": 51.27
        },
        "LumiBlock_00300": {
          "avgPileup": 54.757,
          "deadtime": 0.265,
          "maxPileup": 57.503,
          "minPileup": 51.667
        },
        "LumiBlock_00350": {
          "avgPileup": 55.688,
          "deadtime": 0.434,
          "maxPileup": 56.864,
          "minPileup": 53.053
        }
      }
    },

Plot from TRP (Pileup is in the right axis):

Related to ATR-27110

Tagging @tamartin @mark

Edited by Aleksandra Poreba

Merge request reports