add timeCutUpperLimit flag for topoclusters
introduce timeCutUpperLimit flag for topoclusters Hello, This MR is introducing a 'timeCutUpperLimit' flag for topoclusters, with a default value of 20, in order to avoid hardcoded numbers in several places (ATLPHYSVAL-825). This cut could possibly be tuned in specific domains, like pi0 reconstruction for taus, but until then, it's better to have a central flag controlling this. I also added the timing cut to the CA configuration for pi0 topoclustering for taus, which was missing. Cheers, Bertrand
Showing
- Calorimeter/CaloRec/python/CaloClusterTopoGetter.py 1 addition, 1 deletionCalorimeter/CaloRec/python/CaloClusterTopoGetter.py
- Calorimeter/CaloRec/python/CaloConfigFlags.py 1 addition, 0 deletionsCalorimeter/CaloRec/python/CaloConfigFlags.py
- Calorimeter/CaloRec/python/CaloTopoClusterConfig.py 1 addition, 1 deletionCalorimeter/CaloRec/python/CaloTopoClusterConfig.py
- Calorimeter/CaloRec/python/CaloTopoClusterFlags.py 12 additions, 3 deletionsCalorimeter/CaloRec/python/CaloTopoClusterFlags.py
- Reconstruction/HeavyIonRec/HIJetRec/python/SubtractedCaloClusterTopoGetter.py 2 additions, 2 deletions...IonRec/HIJetRec/python/SubtractedCaloClusterTopoGetter.py
- Reconstruction/tauRec/python/TauToolHolder.py 6 additions, 0 deletionsReconstruction/tauRec/python/TauToolHolder.py
- Reconstruction/tauRec/share/Pi0ClusterMaker_jobOptions.py 1 addition, 1 deletionReconstruction/tauRec/share/Pi0ClusterMaker_jobOptions.py
Loading
Please register or sign in to comment