Editting ElectronDef.py and PhotonDef.py to avoid creating unnecessary steps
As described in https://its.cern.ch/jira/browse/ATR-21439 by @fpastore this MR is to avoid create all chainsteps for electrons and photon for every sequence rather define only the chainsteps required by the particular sequence. However still WIP since test_trig_data_v1Dev_build test is failing;
AvalancheSchedulerSvc 0 0 ERROR Event 0 on slot 0 failed
CaloBCIDAvgAlg (13), w/ decision: UNDEFINED(-1), in state: CONTROLREADY
missing data: ( 'xAOD::EventInfo' , 'StoreGateSvc+EventInfo' )
can be produced by alg(s): ( EFMuonViewDataVerifier_FS in state: INITIAL ) ( IDViewDataVerifierMuonIso in state: INITIAL ) ( muonCBViewDataVerifier in state: INITIAL ) ( tauViewDataVerifierEFTa$
L1Decoder (16), w/ decision: UNDEFINED(-1), in state: CONTROLREADY
missing data: ( 'TrigConf::HLTMenu' , 'DetectorStore+HLTTriggerMenu' )
can be produced by alg(s): ( SGInputLoader in state: ERROR )
LumiBlockMuWriter (1203), w/ decision: UNDEFINED(-1), in state: CONTROLREADY
missing data: ( 'xAOD::EventInfo' , 'StoreGateSvc+EventInfo' )
can be produced by alg(s): ( EFMuonViewDataVerifier_FS in state: INITIAL ) ( IDViewDataVerifierMuonIso in state: INITIAL ) ( muonCBViewDataVerifier in state: INITIAL ) ( tauViewDataVerifierEFTa$
AthenaHiveEventLoopMgr FATAL Failed event detected on s: 0 e: 0 w/ fail mode: AlgStall
Do I need to add anything to VDV? adding @tamartin @fpastore and @fernando
Edited by Debottam Bakshi Gupta