Skip to content

Mdt conditions remove string payload & add DCS voltages

Johannes Junggeburth requested to merge jojungge/athena:DumpMdtCond into main

MdtCondDbData:

  • Noisy channels & chamber names are nowhere used. Remove them from as data members.
  • Streamline the definition of what's a good chamber, layer, multilayer / tube .
  • Add the DcsFsmState values to the conditions ojbect instead. They'll be used in the MdtCalibDbAlg

MdtDigitization : Enforce the usage of the MdtCondDbData object to define dead channels

MdtCondJsonDumpAlg: Add algorithm to dump the constants into a JSON file. The dead channel data is dumped into different vectors where each entry is a composition of the Identifier fields:

{
 "Chambers": [
{
     "station": "BIL",
     "eta": -6,
     "phi": 1
}
],
 "MultiLayers": [
{
     "station": "BIL",
     "eta": -6,
     "phi": 1,
     "ml": 1,
}
],
 "TubeLayers:": [
{
    "station": "BIL",
     "eta": -6,
     "phi": 1,
     "ml": 1,
     "layer": 1,
}

],
 "Tubes:": [
{
    "station": "BIL",
     "eta": -6,
     "phi": 1,
     "ml": 1,
     "layer": 1,
     "tube": 1,

}
]
}

The DCS voltage data is dumped in the following format:

[
    {
     "station": "BIL",
     "eta": -6,
     "phi": 1,
     "ml": 1,
     "state": "ON",
     "standByVolt": 2501, 
     "readyVolt": 3080
    }, ...
]

This format is just a proposal. But I think, it's worth to reconsider how the data is processed on a longer term scale. Tagging: @formica, @zyan, @idrivask, @ekarentz

Edited by Johannes Junggeburth

Merge request reports