Run 3 L1Calo tau algorithms
Adding Oregon and Tel-Aviv algorithms for the Run 3 L1calo taus to be computed in the eFEX to TrigT1CaloRun3TauFex.cxx. Energy sums and isolation variables are calculated. This is a very simple implementation of the algorithm which is still undergoing development.
To take advantage of timing handling, TrigT1CaloBaseFex::CaloCellET is now used when TH2Ds are filled with supercell information.
Merge request reports
Activity
added 1 commit
- 26bb850e - Changed std::cout to MSG::DEBUG, changed multiple equivalent eta/phi/ET calls...
added 1 commit
- 96fe4bd6 - Incorporate bigCluster algorithm, standardize variable names
added 1 commit
- 40612486 - Fix syntax errors and comment out unused bigCluster variables
added 1 commit
- 525f0ba4 - Change CaloCellEt call to use digitization and threshold properties
added 21.3 Run3L1Calo Trigger TriggerEDM alsoTargeting:21.9 labels
- Resolved by Ben Carlson
Hey Nicholas, Thanks for putting in all the correction! This is looking very nice. I take it you now have the MR now has both algorithms, which is nice.
The remaining work is to ensure that the implementation looks reasonable in terms of efficiency, and we are good to go, right?
One further thing you should change. In order to make the output collections accessible in the AOD, could you add / modify the trigger EDM to contain both of the new collections: https://gitlab.cern.ch/atlas/athena/blob/21.3/Trigger/TriggerCommon/TrigEDMConfig/python/TriggerEDM.py#L1003-1004
You should put in the description of the git the size of the collections in kb/event(which you can get from checkxAOD). There is no reason you shouldn't be able to include them, but the TriggerEDM coordinators want to keep track of it.
Ben
Edited by Ben Carlson - Last reply by Nicholas Luongo
added 1 commit
- b24f2cdf - Oregon and TLV bug fixes, implemented Oregon 12 GeV and 20 GeV isolation boolean flags