TPC: Fix digitizer workflow to load GEM params from CCDB before creating Polya file#14267
TPC: Fix digitizer workflow to load GEM params from CCDB before creating Polya file#14267sawenzel merged 1 commit intoAliceO2Group:devfrom
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
|
||
| // IMPORTANT: load ParameterGEM from CCDB | ||
| auto& ccdbManager = o2::ccdb::BasicCCDBManager::instance(); | ||
| ccdbManager.getSpecific<o2::tpc::ParameterGEM>(o2::tpc::CDBTypeMap.at(o2::tpc::CDBType::ParGEM), timestamp); |
There was a problem hiding this comment.
after a quick code inspection, it appears that GEMAmplification not only relies on ParameterGEM but also in GainMap and ParameterGas. Shouldn't these values then also be fetched from CCDB prior to creating GEMAmplification? @wiechula @tubagundem
3 participants
The initTPC() function is updated to load GEM parameters from the CCDB using the provided timestamp. This ensures that the Polya file is generated with the correct amplification function with the tuning gain value from the CCDB. Previously, the Polya file was created using default GEM parameters, which led to inconsistencies in anchored MC.