Skip to content

Factrorizing precisionElectron step and making Empty step signature specific

Debottam Bakshi Gupta requested to merge dbakshig/athena:ATR_21211_etCut_ChainMerging into master

As being discussed in ATR-21211 and !36736 (closed) we want to implement an additional step between precisionCalo and final precisionElectron step that is precisionTracking (which was previously combined with precisionElectron). This additional step has a menusequence which does precisionTracking of the events passing precisionCalo step and as menusequence requires a hypo it uses precisionCalo hypo to apply etcut on calclusters already passing precisionCalo step. The sequences look like

'etcut'     : ['getFastCalo', 'getFastElectron', 'getPrecisionCaloElectron', 'getPrecisionTracking'],
'lhloose'   : ['getFastCalo', 'getFastElectron', 'getPrecisionCaloElectron', 'getPrecisionTracking', 'getPrecisionElectron'],
'lhvloose'  : ['getFastCalo', 'getFastElectron', 'getPrecisionCaloElectron', 'getPrecisionTracking', 'getPrecisionElectron'],

current issue discussed ATR-22153 where we face Name clash. Egamma and Muon are both now needing to insert an empty step in #5, they both try and use the same "Step5_Empty1_IMEmptySeq5_Empty1_leg1" which doesn't work.

Suggesting going to "Step5_Empty1_IMEmptySeqEgamma5_Empty1_leg1" and "Step5_Empty1_IMEmptySeqMuon5_Empty1_leg1" to keep them separate. That is signature specific Empty step.

Adding @fernando , @cjmeyer , @tamartin , @hrussell

ps. Also removing gsf place holders from ElectronDef.py (!37504 (merged)) since steps got changed and will be added in future by !35642 (merged)

Edited by Debottam Bakshi Gupta

Merge request reports