athena merge requestshttps://gitlab.cern.ch/atlas/athena/-/merge_requests2023-03-15T15:44:48+01:00https://gitlab.cern.ch/atlas/athena/-/merge_requests/61468Fix ApplyPsi1MassConstraint in BPHY232023-03-15T15:44:48+01:00Xin ChenFix ApplyPsi1MassConstraint in BPHY23Fixed three places with wrong configurations related to ApplyPsi1MassConstraint in BPHY23.pyFixed three places with wrong configurations related to ApplyPsi1MassConstraint in BPHY23.pyhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/61193LLP1 modifications for Emerging Jets Run-3 analysis2023-03-22T09:42:45+01:00Guillaume Lucas AlbouyLLP1 modifications for Emerging Jets Run-3 analysisWe propose here modifications to the LLP1 derivation configuration for compatibility with the Emerging Jets Run-3 analysis ([ANA-EXOT-2022-31](https://atlas-glance.cern.ch/atlas/analysis/analyses/details.php?id=8998)) as discussed during...We propose here modifications to the LLP1 derivation configuration for compatibility with the Emerging Jets Run-3 analysis ([ANA-EXOT-2022-31](https://atlas-glance.cern.ch/atlas/analysis/analyses/details.php?id=8998)) as discussed during an internal [meeting](https://indico.cern.ch/event/1259285/#2-proposal-for-an-llp1-derivat).
The modifications are :
- addition of reconstructed (truth) reclustered jets from AntiKt4EMTopoJets (AntiKt4TruthJets)
- computation and addition of substructure variables (22 vars) to RC jets through a custom tool
- addition of tracks associated to RC jets (thinning)
- addition of the Emerging Jets and large-R jet trigger
Leading to ~ +6.6% in event size regarding the nominal LLP1 config (on mc20 ttbar sample).
![figure-14](/uploads/9660bc1b34bc7a806746819e819ce2ba/figure-14.png)
~~Discussion and validation with AMG is still needed, so will keep this MR as Draft in the mean time.~~
Modifications validated during the DAOD+AMG [meeting](https://indico.cern.ch/event/1264717/#6-llp1-modifications-for-emerg) of 15/03/2023, undrafting MR.Guillaume Lucas AlbouyGuillaume Lucas Albouyhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/60975Fix setup for HION9 ART tests2023-02-24T09:44:33+01:00Klaudia MajFix setup for HION9 ART testsThe 21.2 HION9 ART tests for data and MC are broken because of missing R=0.3 and R=0.5 HI jet collections. This is fixed by adjusting the ART preExecs to include these collections.The 21.2 HION9 ART tests for data and MC are broken because of missing R=0.3 and R=0.5 HI jet collections. This is fixed by adjusting the ART preExecs to include these collections.https://gitlab.cern.ch/atlas/athena/-/merge_requests/60799HION13 SegmentTag muon bugfix2023-02-20T15:46:09+01:00Hao PangHION13 SegmentTag muon bugfixAdd SmartCollections in BPHY13SlimmingHelper
to solve the crach in MC framework running.Add SmartCollections in BPHY13SlimmingHelper
to solve the crach in MC framework running.https://gitlab.cern.ch/atlas/athena/-/merge_requests/60594Modified HION9 to include jets of various radii2023-02-23T09:11:44+01:00Anabel RomeroModified HION9 to include jets of various radiiModified HION9 to include jets of various radii (R=0.2, 0.3, 0.4, 0.5, 0.6, 0.8, 1.0). Modified the pT cuts to be 50 GeV for the larger radii (R=0.8, 1.0) and 20 GeV for the other radii.Modified HION9 to include jets of various radii (R=0.2, 0.3, 0.4, 0.5, 0.6, 0.8, 1.0). Modified the pT cuts to be 50 GeV for the larger radii (R=0.8, 1.0) and 20 GeV for the other radii.https://gitlab.cern.ch/atlas/athena/-/merge_requests/60593enabled b-jets triggers in HIGG4D5 slimming2023-03-10T14:27:35+01:00Mahsana Haleemenabled b-jets triggers in HIGG4D5 slimmingThis affects only the HIGG4D5 derivation. The b-jets trigger features are enabled in slimming to allow scale factors calculations properly.This affects only the HIGG4D5 derivation. The b-jets trigger features are enabled in slimming to allow scale factors calculations properly.ATLAS RobotATLAS Robothttps://gitlab.cern.ch/atlas/athena/-/merge_requests/60569Edits to B Physics DerivationFramework and addition of BPHY24 for R(K-short) ...2023-03-07T21:44:40+01:00Andrew Donald GentryEdits to B Physics DerivationFramework and addition of BPHY24 for R(K-short) AnalysisAdded BPHY24 Derivation, used for R(K-short) analysis. Made several edits to DerivationFrameworkBPhys tools:
1) Edits to JPsiPlusV0Cascade tool to include JPsi to ee
2) Edits to VertexTrackIsolation tool to subtract electron tracks (GSF...Added BPHY24 Derivation, used for R(K-short) analysis. Made several edits to DerivationFrameworkBPhys tools:
1) Edits to JPsiPlusV0Cascade tool to include JPsi to ee
2) Edits to VertexTrackIsolation tool to subtract electron tracks (GSFTrackParticles) from cones
3) Edits to VertexTrackIsolation tool to account for tracks from neutral particlesPeter OnyisiAndrew Donald GentryPeter Onyisihttps://gitlab.cern.ch/atlas/athena/-/merge_requests/60535Fix in handling charged FEs in UFO energy per layer calculation2023-02-10T09:47:07+01:00Chris Malena DelitzschFix in handling charged FEs in UFO energy per layer calculationThis MR is a follow-up of !60135 which caused some crashes in the ART tests for JETM1 and JETM2 where the energy-per-layer variables are calculated for small-R UFO CSSK jets.
The crash occurs when the underlying object of a combined UF...This MR is a follow-up of !60135 which caused some crashes in the ART tests for JETM1 and JETM2 where the energy-per-layer variables are calculated for small-R UFO CSSK jets.
The crash occurs when the underlying object of a combined UFO is a charged FE rather than a neutral FE. These charged FEs do not have the energy-per-layer information stored and therefore the code crashed. Instead, it is now checked if the `otherObject` is a charged FE and its energy is added to the total energy.
In addition, small content changes are implemented for JETM2.
I'm marking this as urgent as I understood from @calpigia that a new release is imminent.https://gitlab.cern.ch/atlas/athena/-/merge_requests/60397Fix a small typo and update mass bound in python2023-02-07T21:45:05+01:00Xin ChenFix a small typo and update mass bound in pythonFixed a small typo in PsiPlusPsiCascade.cxx and updated the X particle mass upper limit in BPHY23.py. Affect BPhys derivations only.Fixed a small typo in PsiPlusPsiCascade.cxx and updated the X particle mass upper limit in BPHY23.py. Affect BPhys derivations only.https://gitlab.cern.ch/atlas/athena/-/merge_requests/60325Additional triggers to STDM72023-02-04T09:45:41+01:00Evgeny SoldatovAdditional triggers to STDM7This merge request adds to STDM7 13 muon triggers (11 - requested by SM group, 2 - requested by HI group).This merge request adds to STDM7 13 muon triggers (11 - requested by SM group, 2 - requested by HI group).https://gitlab.cern.ch/atlas/athena/-/merge_requests/60135Changes to energy-per-layer calculations for PFlow and UFO jets2023-02-09T14:07:16+01:00Chris Malena DelitzschChanges to energy-per-layer calculations for PFlow and UFO jetsUpdating the description to match the latest status and take into account the feedback that was received on this MR and in meetings.
Thanks to the trigger experts, an issue was discovered for EMFrac (and in general for the energy-per-la...Updating the description to match the latest status and take into account the feedback that was received on this MR and in meetings.
Thanks to the trigger experts, an issue was discovered for EMFrac (and in general for the energy-per-layer calculations) for EMPFlow jets. The changes were introduced by !56971 when including the energy-per-layer information for UFO jets. UFO and PFlow jets use the same code to calculate the variables. The impact of the change in the aforementioned MR on EMFrac for PFlow jets is shown in the below figure:
![EMFrac](/uploads/23a61fb6f288d23df70b68593d950b02/EMFrac.png)
After discussing this with the jet experts, e.g. in the Jet Definitions meeting ([agenda](https://indico.cern.ch/event/1237537/)) it was decided that we restore the behaviour for PFlow jets as the recommendations were derived with the blue distribution. This means that we also restore the behaviour in R22.
The difference between the red and the blue distributions is that for the blue distribution, the jet constituents (i.e. the FEs) are used directly to calculate the total energy and to retrieve the energy-per-layer. In the red distribution, the underlying cluster corresponding to the FE is used, i.e. the energies are extracted before the energy subtraction!
In addition, new variables (corresponding to the red distribution) will be calculated at the derivation level that are expected to have superior performance compared to those used for the blue distribution. This has to be confirmed. This approach was not used in R21 as the links to the clusters were broken and therefore the underlying cluster could not be retrieved. The new variables will be used to derive new recommendations using small-R UFO jets. These new variables will be only calculated for the moment in JETMX derivations until it's clear that they should be used for future recommendations.
This MR violates frozen Tier-0 policy as
(1) EMFrac, HECFrac, PSFrac, FracSamplingMax, FracSamplingMaxIndex and EnergyPerSampling change significantly (all triggered by changes to EnergyPerSampling) and
(2) the trigger count will change because the change in the energy-per-layer calculation affects the GSC calibration of jets and therefore the events passing jet trigger requirements. The reference files will be updated accordingly once the CI ran.
Summarizing here quickly the logic for the restored EMFrac:
PFlow jets (constituents are charged and neutral FEs):
- The energy of charged FEs is added to the total energy
- The energy of neutral FEs is added to the total energy and the energy-per-layeris extracted only for neutral FEs
For the new variables (with `CaloBased` in the name), for each FE, the underlying cluster is extracted and its energy is added to the total energy and its energy-per-layer used to calculate variables such as EMFrac. Double-counting is avoided by checking if the cluster has been used already in the calculation.
Tagging some experts: @mhodgkin @mswiatlo @schaarsc @mleblanc @camacho @jroloff @mspalla @haweber
Tagging also @calpigia for his informationhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/60062HIGG1D1 Derivation : Add missing variables2023-01-26T15:44:26+01:00Alkaid ChengHIGG1D1 Derivation : Add missing variablesThis merge request added a missing variable in the HIGG1D1 derivation format for Rel22,specifically for data derivation. It is an urgent fix needed by the HGam analysis group for early run3 coupling analysis targeting morion.
Tagging Hg...This merge request added a missing variable in the HIGG1D1 derivation format for Rel22,specifically for data derivation. It is an urgent fix needed by the HGam analysis group for early run3 coupling analysis targeting morion.
Tagging Hgam conveners @yanght, @ancuetog and software contact @ahabouelhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59940BPHY13 and BPHY23 Updates (derivations only)2023-01-21T09:43:56+01:00Xin ChenBPHY13 and BPHY23 Updates (derivations only)Updated the BPHY13.py to enable reading of MuonSegments in the DAOD output files. Updated JpsiPlusPsiCascade.*, PsiPlusPsiCascade.* and BPHY23.py to deal with large number of candidates per event.Updated the BPHY13.py to enable reading of MuonSegments in the DAOD output files. Updated JpsiPlusPsiCascade.*, PsiPlusPsiCascade.* and BPHY23.py to deal with large number of candidates per event.https://gitlab.cern.ch/atlas/athena/-/merge_requests/59760Adding support for Hybrid Truth Tagging with GNN2023-01-31T10:42:12+01:00Nilotpal KakatiAdding support for Hybrid Truth Tagging with GNN- Added the additional option of Hybrid Truth Tagging with GNN
- Hybrid Truth tagging = Direct tag the given flavor of jets and Truth tag the rest of the jets in the event.
- It first gets the efficiencies of all the jets the usual way, ...- Added the additional option of Hybrid Truth Tagging with GNN
- Hybrid Truth tagging = Direct tag the given flavor of jets and Truth tag the rest of the jets in the event.
- It first gets the efficiencies of all the jets the usual way, and if we are in the Hybrid tagging mode, it will replace the efficiencies of the jets for the given flavor with the Direct Tagging scores.
- The rest of the computation remains same.
tagging @eschopf @hanar @yama @fdibellohttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59756DerivationFrameworkPHYS: fix tau thinning in PHYSLITE and add DeepSet tau ID ...2023-01-12T15:43:00+01:00Bertrand Martin Dit LatourDerivationFrameworkPHYS: fix tau thinning in PHYSLITE and add DeepSet tau ID to PHYSLITE outputHello,
This MR fixes a problem with tau thinning in PHYSLITE caused by !59677 : the TauTrackParticleThinning was dropped from the list of thinning tools supported in PhysCommonThinningConfig and replaced with an all-in-one tau thinning ...Hello,
This MR fixes a problem with tau thinning in PHYSLITE caused by !59677 : the TauTrackParticleThinning was dropped from the list of thinning tools supported in PhysCommonThinningConfig and replaced with an all-in-one tau thinning tool; this was propagated to the PHYS configuration but not to PHYSLITE.
This MR drops the TauTrackParticleThinning from PHYSLITE and only keeps the new TauThinningTool.
It fixes all the PHYSLITE ART tests that are failing today.
Besides, I have added the new Deep Set tau ID to the PHYSLITE output, that's 2 floats (scores) and 4 chars (WPs).
The new tau ID was introduced in !59725 but the output was not kept in PHYSLITE.
For completeness, there is no tau thinning issue in PHYS->PHYSLITE, and the PHYSLITE output seems to be the same (for what concerns taus) when running AOD->PHYSLITE and AOD->PHYS->PHYSLITE.
Unrelated to this MR, I also checked that the multiple tau MRs from yesterday didn't introduce differences in other objects for the PHYS format (I compared today's nightly with yesterday's nightly). I had to ignore tau branches and InDetTrackParticles for this check, as these are affected by tau thinning.
Adding the urgent label. Tagging @calpigia and @jcatmore .
Cheers,
Bertrandhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59725DerivationFramework: add more generic wrapper for tau ID tools, and deploy ne...2023-01-12T14:49:07+01:00Bertrand Martin Dit LatourDerivationFramework: add more generic wrapper for tau ID tools, and deploy new Deep Set tau ID in DAOD_PHYSHello,
This MR is the last urgent tau development for the DerivationFramework, and is doing the following:
* replace TauWPDecoratorWrapper tool (which we used to recompute a tau eVeto RNN WP in AODtoDAOD, as the original WP from RAWtoAL...Hello,
This MR is the last urgent tau development for the DerivationFramework, and is doing the following:
* replace TauWPDecoratorWrapper tool (which we used to recompute a tau eVeto RNN WP in AODtoDAOD, as the original WP from RAWtoALL is buggy) with a more generic TauIDDecoratorWrapper tool that can run additional tauRecTools tools, in particular it allows to deploy the new Deep Set tau ID implemented in !59684
* the fixed eVeto WPs and the Deep Set ID are scheduled by default in PHYS (this is configurable)
* the Deep Set ID scores and WPs are added to the tau smart slimming list
* the CA config for the fixed eVeto WP was streamlined and moved from DerivationFrameworkTau/python/TauCommonConfig.py to Reconstruction/tauRec/python/TauToolHolder.py
Adding the 'urgent' flag as it would be needed for 23.0.13 to be built imminently.
Tagging @calpigia , @lfiorini , @dta , @sineadf , @wlampl .
Thanks!
Bertrandhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59713Updating PHYSLITE input files for CI tests2023-01-11T15:43:16+01:00Cristiano AlpigianiUpdating PHYSLITE input files for CI testsThe CI tests running on PHYSLITE are failing ( ATLASG-2440 ) since the PHYSLITE input files "disappeared" from cvmfs. As temporary patch, this merge request adds new files made with 2023-01-08T2101 nightly. As soon as 23.0.13 is built, ...The CI tests running on PHYSLITE are failing ( ATLASG-2440 ) since the PHYSLITE input files "disappeared" from cvmfs. As temporary patch, this merge request adds new files made with 2023-01-08T2101 nightly. As soon as 23.0.13 is built, new files will be produced for all tests and updated.https://gitlab.cern.ch/atlas/athena/-/merge_requests/59677DerivationFramework: implement self-contained tau thinning, update tau smart ...2023-01-13T17:15:20+01:00Bertrand Martin Dit LatourDerivationFramework: implement self-contained tau thinning, update tau smart slimming list and enable tau thinning in PHYSHello,
This MR implements a self-contained tool in the DerivationFramework to thin all tau-related containers at once. It replaces the per-container thinning tools used so far.
The following containers are thinned: TauJets, TauTracks, I...Hello,
This MR implements a self-contained tool in the DerivationFramework to thin all tau-related containers at once. It replaces the per-container thinning tools used so far.
The following containers are thinned: TauJets, TauTracks, InDetTrackParticles, TauNeutralParticleFlowObjects, TauSecondaryVertices, as well as the equivalent "_MuonRM" containers from the muon-subtracted tau reconstruction.
The tau thinning that had been deactivated for easier R21-vs-R22 comparisons is re-enabled. For now, we only require tau pt > 13 GeV. No cut is applied to nTracks nor to the RNN ID score.
The tau smart slimming list has been extended to take advantage of new variables:
* TauJetsAux.nChargedTracks.nIsolatedTracks.nAllTracks: the first is for convenience, the last two cannot be accessed anymore at DAOD level due to tau track thinning and are useful to understand tau modelling
* TauJetsAux.NNDecayModeProb_1p0n.NNDecayModeProb_1p1n.NNDecayModeProb_1pXn.NNDecayModeProb_3p0n: tau NN decay mode probabilities, new in R22, the last probability NNDecayModeProb_3pXn can be obtained from unitarity and was not added
* TauTracksAux.rnn_chargedScore.rnn_isolationScore.rnn_conversionScore: new in R22, again the last score rnn_fakeScore can be obtained from unitarity and was not added
Thanks to the thinning, the size of DAOD_PHYS is kept almost unchanged :-) Numbers taken from 1k ttbar events:
```
Before:
================================================================================
Disk Size Fraction Category Name
--------------------------------------------------------------------------------
2.391 kb 0.064 tau
3.128 kb 0.083 InDet
37.517 kb 1.000 Total
--------------------------------------------------------------------------------
Mem Size Disk Size Size/Evt Compression Items Container Name (Type)
--------------------------------------------------------------------------------
189.111 kb 34.521 kb 0.035 kb 5.478 1000 TauSecondaryVertices_MuonRM (DataVector<xAOD::Vertex_v1>) [tau]
201.008 kb 41.326 kb 0.041 kb 4.864 1000 TauTracks_MuonRM (DataVector<xAOD::TauTrack_v1>) [tau]
347.127 kb 62.358 kb 0.062 kb 5.567 1000 DiTauJets (DataVector<xAOD::DiTauJet_v1>) [tau]
189.941 kb 65.823 kb 0.066 kb 2.886 1000 TauNeutralParticleFlowObjects_MuonRM (DataVector<xAOD::PFO_v1>) [tau]
721.512 kb 146.839 kb 0.147 kb 4.914 1000 DiTauJetsLowPt (DataVector<xAOD::DiTauJet_v1>) [tau]
969.123 kb 176.326 kb 0.176 kb 5.496 1000 TauJets_MuonRM (DataVector<xAOD::TauJet_v3>) [tau]
769.607 kb 196.075 kb 0.196 kb 3.925 1000 TauSecondaryVertices (DataVector<xAOD::Vertex_v1>) [tau]
894.438 kb 229.125 kb 0.229 kb 3.904 1000 TruthTaus (DataVector<xAOD::TruthParticle_v1>) [Truth]
1013.831 kb 286.620 kb 0.287 kb 3.537 1000 TauTracks (DataVector<xAOD::TauTrack_v1>) [tau]
953.835 kb 606.876 kb 0.607 kb 1.572 1000 TauNeutralParticleFlowObjects (DataVector<xAOD::PFO_v1>) [tau]
5791.151 kb 774.328 kb 0.774 kb 7.479 1000 TauJets (DataVector<xAOD::TauJet_v3>) [tau]
```
```
After:
================================================================================
Disk Size Fraction Category Name
--------------------------------------------------------------------------------
2.217 kb 0.060 tau
2.952 kb 0.079 InDet
37.241 kb 1.000 Total
--------------------------------------------------------------------------------
Mem Size Disk Size Size/Evt Compression Items Container Name (Type)
--------------------------------------------------------------------------------
185.936 kb 33.244 kb 0.033 kb 5.593 1000 TauSecondaryVertices_MuonRM (DataVector<xAOD::Vertex_v1>) [tau]
161.026 kb 41.938 kb 0.042 kb 3.840 1000 TauNeutralParticleFlowObjects_MuonRM (DataVector<xAOD::PFO_v1>) [tau]
347.016 kb 61.961 kb 0.062 kb 5.601 1000 DiTauJets (DataVector<xAOD::DiTauJet_v1>) [tau]
253.153 kb 63.924 kb 0.064 kb 3.960 1000 TauTracks_MuonRM (DataVector<xAOD::TauTrack_v1>) [tau]
721.512 kb 147.100 kb 0.147 kb 4.905 1000 DiTauJetsLowPt (DataVector<xAOD::DiTauJet_v1>) [tau]
830.890 kb 153.712 kb 0.154 kb 5.405 1000 TauJets_MuonRM (DataVector<xAOD::TauJet_v3>) [tau]
714.360 kb 175.785 kb 0.176 kb 4.064 1000 TauSecondaryVertices (DataVector<xAOD::Vertex_v1>) [tau]
894.324 kb 230.427 kb 0.230 kb 3.881 1000 TruthTaus (DataVector<xAOD::TruthParticle_v1>) [Truth]
647.084 kb 393.983 kb 0.394 kb 1.642 1000 TauNeutralParticleFlowObjects (DataVector<xAOD::PFO_v1>) [tau]
1147.327 kb 456.443 kb 0.456 kb 2.514 1000 TauTracks (DataVector<xAOD::TauTrack_v1>) [tau]
4353.117 kb 688.641 kb 0.689 kb 6.321 1000 TauJets (DataVector<xAOD::TauJet_v3>) [tau]
```
Adding the 'urgent' flag as this is needed for the imminent PHYS production.
Tagging @calpigia , @lfiorini , @dta , @sineadf .
Cheers,
Bertrandhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59664fixed a typo in HIGG8D1 format (followup of https://gitlab.cern.ch/atlas/athe...2023-01-26T08:39:25+01:00Mahsana Haleemfixed a typo in HIGG8D1 format (followup of https://gitlab.cern.ch/atlas/athena/-/merge_requests/59575)fixed a typo in HIGG8D1 format (followup of https://gitlab.cern.ch/atlas/athena/-/merge_requests/59575). The original request (https://gitlab.cern.ch/atlas/athena/-/merge_requests/59575) only enables the TopHadronOrigin decoration in th...fixed a typo in HIGG8D1 format (followup of https://gitlab.cern.ch/atlas/athena/-/merge_requests/59575). The original request (https://gitlab.cern.ch/atlas/athena/-/merge_requests/59575) only enables the TopHadronOrigin decoration in the derivation.ATLAS RobotATLAS Robothttps://gitlab.cern.ch/atlas/athena/-/merge_requests/59654DerivationFramework: fix tau RNN eVeto WP decoration2023-01-09T15:43:10+01:00Bertrand Martin Dit LatourDerivationFramework: fix tau RNN eVeto WP decorationHello,
The primary goal of this MR is to fix this warning showing up in AOD->DAOD:
```
Derivation 11:43:48 ToolSvc.TauSele...WARNING SG::ExcBadAuxVar: Attempt to retrieve nonexistent aux data item `::EleRNNLoose_v1' (1008).
```
This is ...Hello,
The primary goal of this MR is to fix this warning showing up in AOD->DAOD:
```
Derivation 11:43:48 ToolSvc.TauSele...WARNING SG::ExcBadAuxVar: Attempt to retrieve nonexistent aux data item `::EleRNNLoose_v1' (1008).
```
This is due to AddEventCleanFlagsCfg, which schedules AddTauAugmentationCfg that decorates taus with a `DFTauLoose` flag telling whether a tau passes a loose selection.
The problem is that the `DFTauLoose` criterion relies on an electron veto WP that must be re-computed in AOD->DAOD, as the original WP computed in RAWtoALL is buggy, and the fixed eVeto WP re-decoration is currently scheduled independently from AddTauAugmentationCfg and happens to be scheduled too late in DAOD_PHYS. So this MR makes sure that AddTauAugmentationCfg internally calls AddTauWPDecorationCfg, such that the fixed WP exists when we compute `DFTauLoose`.
We were also missing the eVeto WP re-decoration for muon-subtracted taus (boosted mu-had reconstruction scheduled in AOD->DAOD). "TauJets_MuonRM" are built from "TauJets": after subtracting the muon off the tau, we rerun most of the standard tau reconstruction. So we also need to rerun the fixed eVeto WP decoration. The TauWPDecoratorWrapper is modified such that in the mu-had case, we ignore the presence of an existing decoration (coming from the decoration of "TauJets" performed upstream) and proceed regardless.
Finally, a few fixes were made to AddTauAugmentationCfg (correct WP tightness), and the use of ConfigFlags and tool/algorithm names was simplified: we no longer use a prefix when a given tool/algorithm has a fixed configuration.
Running AOD->DAOD_PHYS over 1k ttbar events, comparing DAOD_PHYS with/without the MR, diff-root finds:
```
Py:diff-root WARNING the following variables exist only in the new file !
Py:diff-root WARNING - [TauJets_MuonRMAuxDyn.EleRNNLoose_v1]
Py:diff-root WARNING - [TauJets_MuonRMAuxDyn.EleRNNMedium_v1]
Py:diff-root WARNING - [TauJets_MuonRMAuxDyn.EleRNNTight_v1]
Py:diff-root WARNING - [TauJets_MuonRMAuxDyn.RNNEleScoreSigTrans_v1]
Py:diff-root INFO comparing [2135] leaves over entries...
Py:diff-root INFO 691.EventInfoAuxDyn.DFCommonJets_eventClean_LooseBad [[0.0]] -> [[1.0]] => diff= [N/A]
Py:diff-root INFO Found [17487966] identical leaves
Py:diff-root INFO Found [1] different leaves
Py:diff-root INFO [EventInfoAuxDyn.DFCommonJets_eventClean_LooseBad]: 1 leaves differ
```
It seems the effect on `DFCommonJets_eventClean_LooseBad` is rather small, fortunately, at least in MC.
Tagging @lfiorini .
Cheers,
Bertrand