Avoid reusing label names for objects

[skkwan]

Lastly, could you review all the label names of the objects to avoid using the same one more than once (this is the case of the “RCT” and “GCT” labels used for “L1EGXtalClusters” and “L1CaloTowers”: https://github.com/cms-l1t-offline/cmssw/blob/l1t-integration-CMSSW_13_2_0_pre3/L1Trigger/L1CaloTrigger/plugins/Phase2L1CaloEGammaEmulator.cc#L501

https://github.com/cms-l1t-offline/cmssw/blob/l1t-integration-CMSSW_13_2_0_pre3/L1Trigger/L1CaloTrigger/plugins/Phase2L1CaloEGammaEmulator.cc#L632

Having the same label doesn’t allow the collection to be fed to NanoAOD-like ntuplizers. Always about the flags, are the Egamma collection and the CaloCrystalCluster 100% consistent?

• [x] Make the labels unique
• [x] Propagate these label changes to the analyzer and other dependencies
• [x] Check that efficiency analyzer works interactively
• [x] Check that rates analyzer works interactively
• [ ] Check that efficiency analyzer works on CRAB
• [ ] Check that rates analyzer works on CRAB

[skkwan]

Included unique labels for the RCT and GCT output collections [1] [1] https://github.com/skkwan/cmssw/commit/a68ce53cd8912fa9b49fd442b481e232932107a3