Inconsistent RICH1 and RICH2 Conditions between DetDesc and DD4Hep for processing of MC samples

During validation of simulation conditions in issue16, we are checking if the conditions between DetDesc and DD4Hep consistent for RICH1 and RICH2.

The distinction between DetDesc and DD4HEP for RICH1 and RICH2 conditions are listed below.

sim10/run3-ideal lhcb-condition-database/master Note
Conditions/Rich1/HardwareProperties/ Conditions/Rich1/HardwareProperties/PDProperties.yml/0 The two folders contain different files, and it is uncertain whether they include the same information. This need confirmation from sub-detector.
sim10/run3-ideal SIMCOND/upgrade/master Note

Conditions/Rich1/Environment/

All conditions here appear to be used in run1&run2. Are they still validate for run3?

Conditions/Rich1/ChannelInfo/PMTProperties.xml Conditions/Rich1(2)/ReadoutConf/DetectorConfig.xml Conditions/Rich1(2)/ReadoutConf/DetectorNumbers.xml Conditions/Rich1(2)/ReadoutConf/PMTDetectorNumbers.xml

Conditions only exist in SIMCOND.

Conditions/Rich1/HardwareProperties/LookupTable.yml

Conditions/Rich1(2)/HardwareProperties/PDProperties.yml

Conditions only exist in sim10/run3-ideal. If these conditions are needed for DetDesc?

Conditions/Rich1(2)/HardwareProperties/ReadoutTimeInfo.yml

Conditions/Rich1(2)/HardwareProperties/ReadoutTimeInfo.xml

Different conditions, for example, ReadoutDelay_2 as a list does not exist in Conditions/Rich1/HardwareProperties/ReadoutTimeInfo.xml

Conditions/Rich1(2)/Environment/Gas.xml

Conditions/Rich1(2)/Environment/Gas.xml

GasPressure and GasTemperature are in DD4HEP. Discussed in #16 and average of such conditions should be included in sim10/run3-ideal for each block.

cc: @gcorti, @mexu, @msaur

Edited by Christopher Rob Jones