athena merge requestshttps://gitlab.cern.ch/atlas/athena/-/merge_requests2021-10-28T15:42:20+02:00https://gitlab.cern.ch/atlas/athena/-/merge_requests/47574implement TLA selector in HypoAlg2021-10-28T15:42:20+02:00Francesca Pastoreimplement TLA selector in HypoAlgTest to implement the TLA selector functionalities within a HypoAlg, was suggested in ATR-24263. The test is with one muon chain running this command:
```
athenaHLT.py -c "selectChains=['HLT_2mu4_L12MU3V','HLT_mu10_mu6_probe_PhysicsTLA_L...Test to implement the TLA selector functionalities within a HypoAlg, was suggested in ATR-24263. The test is with one muon chain running this command:
```
athenaHLT.py -c "selectChains=['HLT_2mu4_L12MU3V','HLT_mu10_mu6_probe_PhysicsTLA_L1MU8F','HLT_mu10_PhysicsTLA_L1MU8F'];setMenu='LS2_v1_TriggerValidation_prescale';doL1Sim=True;fpeAuditor=True;" -o output --dump-config-reload --imf --perfmon --threads=1 --concurrent-events=1 --nprocs=1 --number-of-events=4 --file=/cvmfs/atlas-nightlies.cern.ch/repo/data/data-art/Tier0ChainTests/data17_13TeV.00330470.physics_Main.merge.DRAW_ZMUMU.f843_m1831._0200.1 TriggerJobOpts/runHLT_standalone.py >athenaHLT.WriteBS.log 2>&1
```
It implements two additional steps:
```
Step5_filter [Seq] [Concurrent] [OR]
FStep5_1muonTLA [Alg] [n= 0]
Step5_reco [Seq] [Concurrent] [OR]
Step5_1muonTLA [Seq] [Sequential] [Prompt]
FStep5_1muonTLA [Alg] [n= 0]
Step5_1muonTLA_view [Seq] [Sequential] [Prompt]
Step5_1muonTLA_reco [Seq] [Concurrent] [OR]
TLAMuonAthSequence [Seq] [Sequential] [Prompt]
IM_TLAMuons [Alg] [n= 0]
MuonTLASeq [Seq] [Sequential] [Prompt]
tlaMuonInViewAlgs [Seq] [Concurrent] [OR]
TLAMuonViewDataVerifier [Alg] [n= 0]
TrigMuonTLAHypoAlg [Alg] [n= 0]
ComboHypo_Step5_1muonTLA [Alg] [n= 0]
TriggerSummaryStep5 [Alg] [n= 0]
Step6_filter [Seq] [Concurrent] [OR]
FStep6_merged1_PEBInfoWriter_PhysicsTLA [Alg] [n= 0]
Step6_reco [Seq] [Concurrent] [OR]
Step6_merged1_PEBInfoWriter_PhysicsTLA [Seq] [Sequential] [Prompt]
FStep6_merged1_PEBInfoWriter_PhysicsTLA [Alg] [n= 0]
Step6_merged1_PEBInfoWriter_PhysicsTLA_view [Seq] [Sequential] [Prompt]
Step6_merged1_PEBInfoWriter_PhysicsTLA_reco [Seq] [Concurrent] [OR]
pebSequence_PhysicsTLA [Seq] [Sequential] [Prompt]
IMpeb_PhysicsTLA [Alg] [n= 0]
PEBInfoWriterAlg_PhysicsTLA [Alg] [n= 0]
ComboHypo_Step6_merged1_PEBInfoWriter_PhysicsTLA [Alg] [n= 0]
TriggerSummaryStep6 [Alg] [n= 0]
```
The target is to collect the selected muons in the new EDM collection: HLT_Muons_RoI_TLA
tagging @mmontell, @tamartin , @rbielskiFrancesca PastoreFrancesca Pastorehttps://gitlab.cern.ch/atlas/athena/-/merge_requests/47554Switch Precision Calo Calibration to Online Rel21 Version2021-11-03T08:34:05+01:00Joao Victor Da Fonseca PintoSwitch Precision Calo Calibration to Online Rel21 VersionThis MR is a part of !46701 (from @dbakshig). Since the egammaSuperCluster is in place, now we need to specify the calibration MVA at the precision calo step. Here, we setup the Rel21 calib folder (as suggested by offline people) and ada...This MR is a part of !46701 (from @dbakshig). Since the egammaSuperCluster is in place, now we need to specify the calibration MVA at the precision calo step. Here, we setup the Rel21 calib folder (as suggested by offline people) and adapt the precision calo sequence to specify if is an electron or photon sequence type.
To validate this, we launched three productions based on 14th round:
- Topo cluster configuration (r15);
- SuperCluster with offline configuration using electron type for both sequences (r19);
- SuperCluster with online Rel21 configuration (these MR);
I will post the LCG jobs here soon.
**NOTE**: For now, I will not split the precision calo sequence in two (e and g) as suggested by @tamartin. I will leave these modifications to the next round since this MR must land asap into the master and to **avoid bugs into the menu** configuration. For the nexts rounds we (TrigEgamma) are planning to:
- split precision calo in two (e and g);
- Merge LRT, GSF and FWD python files into a single file;
- Centralize all keys into the EgammaDefs;
- tidy-up the e and g names;
We also have ATR-24180
Reconstruction jobs:
R15 (Topo cluster) - Done
MON r1003: https://bigpanda.cern.ch/task/27142789/
AOD r1003: https://bigpanda.cern.ch/task/27134932/
R22 (SC with offline electron):
MON r2004:
AOD r2004: https://bigpanda.cern.ch/task/27146961/
R22 (SC with Rel21 online calibration):
MON r3004:
AOD r3004: https://bigpanda.cern.ch/task/27146958/Joao Victor Da Fonseca PintoJoao Victor Da Fonseca Pintohttps://gitlab.cern.ch/atlas/athena/-/merge_requests/47278Unify TLA-specific Stream and EventBuildType identifiers2021-10-18T21:45:55+02:00Marco MontellaUnify TLA-specific Stream and EventBuildType identifiersThis merge requests replaces the individual Stream and EventBuildType identifiers for Jet and Photon chains with a single TLA-universal set of identifiers.
**EventBuildType / DataScoutIdentifier:**
JetDS --> PhysicsTLA
PhotonDS --> Ph...This merge requests replaces the individual Stream and EventBuildType identifiers for Jet and Photon chains with a single TLA-universal set of identifiers.
**EventBuildType / DataScoutIdentifier:**
JetDS --> PhysicsTLA
PhotonDS --> PhysicsTLA
**Stream tag:**
JetDS --> TLA
PhotonDS --> TLA
Note that there was no fundamental reason for the DSI and the Stream tag to bear the same name, as they did before this MR. Given the confusion that this would previously cause both within and outside the TLA group, we are opting to differentiate the two (PhysicsTLA for DSI vs TLA for stream tag).
**Derivative changes:**
- Name and stream identifier of all TLA chains in LS2_v1
- EBT/DSI identifier for TLA containers as defined I TrigEDMRun3
- EBT/DSI reference values in JetChainConfiguration/PhotonChainConfiguration for which the menu adds the TLA step
----
The Run 3 TLA Team,https://gitlab.cern.ch/atlas/athena/-/merge_requests/47212adding tau trigger test chain without clusters outside of the ROI2021-10-14T15:43:40+02:00Antonio De Mariaadding tau trigger test chain without clusters outside of the ROIfollowing from https://gitlab.cern.ch/atlas/athena/-/merge_requests/46978
Creating "tracktwoMVAClus" tau trigger chain test; main difference compared to the other chains, only difference is the possibility to exclude clusters which are ...following from https://gitlab.cern.ch/atlas/athena/-/merge_requests/46978
Creating "tracktwoMVAClus" tau trigger chain test; main difference compared to the other chains, only difference is the possibility to exclude clusters which are outside the ROI in the HLT tau trigger reconstruction.
These chains will be used for validation and rate comparison as discussed also here:
https://its.cern.ch/jira/browse/ATR-23454
tagging @iriu, @carquin and @martindlhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46966TrigEDMConfig: write HLT tau track impact parameters to AOD2021-10-07T14:29:38+02:00Bertrand Martin Dit LatourTrigEDMConfig: write HLT tau track impact parameters to AODHello,
This MR is adding HLT tau track impact parameters and significances (4 new floats per track) to the Run3 trigger EDM file, for one container (`HLT_tautrack_MVA`), so that these variables are available in AOD.
These variables are ...Hello,
This MR is adding HLT tau track impact parameters and significances (4 new floats per track) to the Run3 trigger EDM file, for one container (`HLT_tautrack_MVA`), so that these variables are available in AOD.
These variables are dynamic variables that will be needed to train RNN tau ID for Run3 tau triggers: `d0TJVA`, `d0SigTJVA`, `z0sinthetaTJVA`, `z0sinthetaSigTJVA`.
The others in the list are static Aux variables that were already kept by default.
The only Aux variable not appearing in the list is `bdtScores`, which is no longer used in R22 (neither offline nor online).
From 40 q221 events,
```
checkFile myAOD.pool.root | grep HLT_tautrack_MVA
1.400 kb 0.311 kb 0.008 kb 0.000 40 (B) HLT_tautrack_MVA
16.202 kb 1.406 kb 0.035 kb 0.000 40 (B) HLT_tautrack_MVAAuxDyn.viewIndex
6.772 kb 3.437 kb 0.086 kb 0.000 40 (B) HLT_tautrack_MVAAuxDyn.d0TJVA
6.826 kb 3.443 kb 0.086 kb 0.000 40 (B) HLT_tautrack_MVAAuxDyn.z0sinthetaSigTJVA
6.812 kb 3.448 kb 0.086 kb 0.000 40 (B) HLT_tautrack_MVAAuxDyn.z0sinthetaTJVA
6.787 kb 3.459 kb 0.086 kb 0.000 40 (B) HLT_tautrack_MVAAuxDyn.d0SigTJVA
74.975 kb 12.182 kb 0.305 kb 0.000 40 (B) HLT_tautrack_MVAAux.
```
Hopefully the size increase is acceptable.
For completeness, I have updated the q221 digest reference file to reflect the new AOD content, although currently the CI test seems to [ignore the L1 and HLT trigger content](https://gitlab.cern.ch/atlas-sit/CI/-/blob/master/TestConfig/q221xAODDigestTest.citest#L84).
I guess that's why people don't bother updating this file when the trigger content changes, and must explain why non-tau trigger changes are reported.
Tagging @ademaria , @iriu , @okuprash .
Cheers,
Bertrandhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46725include ringer cells info into AOD file using ringerReFexFlags2021-09-29T15:43:27+02:00Juan Lieber Marininclude ringer cells info into AOD file using ringerReFexFlagsThis implementation concerns about the QT on JIRA: ATR-23217. It will allow to dump the cells used by Ringer algorithm to perform studies for others ring topologies.
Pinging: @fernando @pamachad @cjmeyer @jodafons @efurtado @eegidiopThis implementation concerns about the QT on JIRA: ATR-23217. It will allow to dump the cells used by Ringer algorithm to perform studies for others ring topologies.
Pinging: @fernando @pamachad @cjmeyer @jodafons @efurtado @eegidiopJuan Lieber MarinJuan Lieber Marinhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46662Allowing jet trigger preselection for large-R jets2021-10-06T15:45:59+02:00Marco ValenteAllowing jet trigger preselection for large-R jetsThis MR enables emtopo preselections to be applied on large-R pflow jet chains. Right now, the code is structured in a way that uncalibrated R=1.0 antikt jets are used the the calo-only preselection. Numberous test chains are added to th...This MR enables emtopo preselections to be applied on large-R pflow jet chains. Right now, the code is structured in a way that uncalibrated R=1.0 antikt jets are used the the calo-only preselection. Numberous test chains are added to the LS2_v1 menu.
Tagging @ayana, @khoo @cantelMarco ValenteMarco Valentehttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46596B-physics trigger: fix Tag-and-Probe chains from BphysPEB stream (ATR-23615)2021-09-21T15:42:52+02:00Vladimir LyubushkinB-physics trigger: fix Tag-and-Probe chains from BphysPEB stream (ATR-23615)This MR re-enables chains like 'HLT_mu6_bJpsimutrk_MuonTrkPEB_L1MU5VF'.
The chain consists of the following steps:
* l2io muon is built from L1 item, pure muon steps
* build extended RoI around EF muon and perform fast and precise trac...This MR re-enables chains like 'HLT_mu6_bJpsimutrk_MuonTrkPEB_L1MU5VF'.
The chain consists of the following steps:
* l2io muon is built from L1 item, pure muon steps
* build extended RoI around EF muon and perform fast and precise tracking in it
* build J/psi candidate from l2io muon and tracks from the same SG::View, check chi2 and mass of the xAOD::TrigBphys objects
The xAOD::TrigBphys now has link to the single muon, so that no need to handle the problem described in ATR-23615
CC: @abartonhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46591Updated HI HLT Photon Trigger Framework2021-11-17T15:43:03+01:00Berenice GarciaUpdated HI HLT Photon Trigger FrameworkI have implemented the framework for the Heavy-Ion HLT photon triggers. I have used the UE subtracted calo-clusters to reconstruct HLT photons. I have also updated the HI Photon trigger menu. @mrybarI have implemented the framework for the Heavy-Ion HLT photon triggers. I have used the UE subtracted calo-clusters to reconstruct HLT photons. I have also updated the HI Photon trigger menu. @mrybarhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46447Switching off use of cached eventViews2022-01-14T15:25:32+01:00Debottam Bakshi GuptaSwitching off use of cached eventViewsAs mentioned ATR-24052 (also related ATR-24027) this MR will add a Flag to switch off the use of cached eventViews when required. Adding @tamartin and @gipezzulAs mentioned ATR-24052 (also related ATR-24027) this MR will add a Flag to switch off the use of cached eventViews when required. Adding @tamartin and @gipezzulhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46446TriggerMenuMT Retrieve & use HLT jet collection name in HLT Bjet2021-10-09T19:08:10+02:00Claire AntelTriggerMenuMT Retrieve & use HLT jet collection name in HLT Bjet[ATR-22333](https://its.cern.ch/jira/browse/ATR-22333)
# Purpose
Currently the b-tag related output containers are named the same irrespective of which jet collection they were produced from. We want output containers named based on t...[ATR-22333](https://its.cern.ch/jira/browse/ATR-22333)
# Purpose
Currently the b-tag related output containers are named the same irrespective of which jet collection they were produced from. We want output containers named based on the full jet collection name. This MR implements this in two steps:
- (a) Jet changes: Function to retrieve full jet container name from jet chain dictionary.
- (b) Bjet changes: Use of full jet container name in output collection names.
Basically
- Old container name: `HLT_bJets`
- New container name: `HLT_AntiKt4EMPFlowJets_subresjesgscIS_ftf_bJets`
Also
- Old container name: `HLT_BTagging`
- New container name: `HLT_AntiKt4EMPFlowJets_subresjesgscIS_ftf_BTagging`
etc.
# Details
## Jet changes
Function to retrieve the full jet container implemented in `TriggerMenuMT/JetChainConfiguration.py` . Uses as far as possible pre-existing functions to assemble jet name. Jet name retrieved via so
```python
jet_cfg = JetChainConfiguration(chainDict)
jet_name = jet_cfg.jetName
```
## Bjet changes
* `GenerateBjetChainDefs` calls `jet_cfg.jetName` function to retrieve and pass jet collection name through to bjet slice.
* `BjetChainConfiguration`, `BjetMenuSequences`, `BjetFlavourTaggingConfiguration` adapted to use new jet name structure.
* `TriggerEDMRun3` updated.
* Conditions DB alias update in `runHLT_standalone.py`
# This affects...
- Affects `TriggerMenuMT` Jet and Bjet python configuration files.
- Affects `TrigEDMConfig`: Adds new b-tag collections (EMTopo & PFlow based), removes old ones.
- Adaptations needed in b-jet monitoring and derivation framework.
# Tests run
`runHLT_standalone.py`
```
athena.py -l INFO -c "setMenu='LS2_v1'; forceEnableAllChains=True;doEmptyMenu=True;doBjetSlice=True;doWriteBS=True;doWriteRDOTrigger=False;" --imf --perfmon --threads=1 --evtMax=10 --filesInput=/cvmfs/atlas-nightlies.cern.ch/repo/data/data-art/TriggerTest/valid1.410000.PowhegPythiaEvtGen_P2012_ttbar_hdamp172p5_nonallhad.merge.RDO.e4993_s3214_r11315/RDO.17533168._000001.pool.root.1 TriggerJobOpts/runHLT_standalone.py
athena.py -l INFO -c "setMenu='Cosmic_run3_v1'; forceEnableAllChains=True;doEmptyMenu=True;doBjetSlice=True;doWriteBS=True;doWriteRDOTrigger=False;" --imf --perfmon --threads=1 --evtMax=10 --filesInput=/cvmfs/atlas-nightlies.cern.ch/repo/data/data-art/TriggerTest/valid1.410000.PowhegPythiaEvtGen_P2012_ttbar_hdamp172p5_nonallhad.merge.RDO.e4993_s3214_r11315/RDO.17533168._000001.pool.root.1 TriggerJobOpts/runHLT_standalone.py
athena.py -l INFO -c "setMenu='LS2_v1'; forceEnableAllChains=True;doEmptyMenu=True;doWriteBS=True;doWriteRDOTrigger=False;" --imf --perfmon --threads=1 --evtMax=10 --filesInput=/cvmfs/atlas-nightlies.cern.ch/repo/data/data-art/TriggerTest/valid1.410000.PowhegPythiaEvtGen_P2012_ttbar_hdamp172p5_nonallhad.merge.RDO.e4993_s3214_r11315/RDO.17533168._000001.pool.root.1 TriggerJobOpts/runHLT_standalone.py
```
minimal `runTrigART.py`
```
runTrigART.py -m -j4
```
Only WARNINGS (not linked to my changes in any obvious way).
`ctests`: All passhttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46421Adding isolation variables to electron and photons in HLT at TrigEDM2021-10-06T21:42:44+02:00Fernando MonticelliAdding isolation variables to electron and photons in HLT at TrigEDMThis MR is to make the decorations made by the TrackIsolation tool available on electrons and photons at HLT, which are needed for DataQuality, Monitoring and debugging.
Relates to ATR-23728This MR is to make the decorations made by the TrackIsolation tool available on electrons and photons at HLT, which are needed for DataQuality, Monitoring and debugging.
Relates to ATR-23728https://gitlab.cern.ch/atlas/athena/-/merge_requests/46266Disable Asym Ringer Reconstruction code and add flags2021-09-07T03:04:47+02:00Joao Victor Da Fonseca PintoDisable Asym Ringer Reconstruction code and add flagsThis MR will turn-off the ringer asymmetric code and include job flags to turn-on by preInclude (test purpose)
ping: @cjmeyer ,@dbakshig , @jlieberm , @eegidiop , @efurtado , @pamachadThis MR will turn-off the ringer asymmetric code and include job flags to turn-on by preInclude (test purpose)
ping: @cjmeyer ,@dbakshig , @jlieberm , @eegidiop , @efurtado , @pamachadJoao Victor Da Fonseca PintoJoao Victor Da Fonseca Pintohttps://gitlab.cern.ch/atlas/athena/-/merge_requests/46101Redesign of disappearing and large dEdx track trigger hypos (ATR-21591 and AT...2021-09-01T03:03:14+02:00Kunihiro NaganoRedesign of disappearing and large dEdx track trigger hypos (ATR-21591 and ATR-21590) and fix for disappering track hypo thread safety- Redesign of disappearing track and large dE/dx trigger hypos (Alg/Tool) as needed for hit-based DV (discussed at ATR-23923, ATR-23688)
- Fix for thread safety for disappearing track trigger hypo as needed for hit-based DV (discussed at...- Redesign of disappearing track and large dE/dx trigger hypos (Alg/Tool) as needed for hit-based DV (discussed at ATR-23923, ATR-23688)
- Fix for thread safety for disappearing track trigger hypo as needed for hit-based DV (discussed at ATR-24022)https://gitlab.cern.ch/atlas/athena/-/merge_requests/46088TriggerEDM: Don't try to save CaloCellContainer#SCell to ByteStream HLT payload2021-08-27T03:08:05+02:00Rafal Bielskirafal.bielski@cern.chTriggerEDM: Don't try to save CaloCellContainer#SCell to ByteStream HLT payloadRemove the "BS" target for "CaloCellContainer#SCell" in the Trigger EDM list, which was just a configuration mistake. This should fix ATR-24059.
*MR submitted from GitLab Web Editor, so the branch is on the main repo*Remove the "BS" target for "CaloCellContainer#SCell" in the Trigger EDM list, which was just a configuration mistake. This should fix ATR-24059.
*MR submitted from GitLab Web Editor, so the branch is on the main repo*https://gitlab.cern.ch/atlas/athena/-/merge_requests/45896Schedule decoding of phase-1 MUCTPI DAQ ROB in offline reconstruction2021-08-24T16:34:51+02:00Rafal Bielskirafal.bielski@cern.chSchedule decoding of phase-1 MUCTPI DAQ ROB in offline reconstructionThe `xAOD::MuonRoIContainer#LVL1MuonRoIs` in the Run-3 path is produced during the HLT, then serialised and saved to ByteStream. Offline reconstruction decodes it from ByteStream with all the rest of HLT containers and saves to ESD/AOD. ...The `xAOD::MuonRoIContainer#LVL1MuonRoIs` in the Run-3 path is produced during the HLT, then serialised and saved to ByteStream. Offline reconstruction decodes it from ByteStream with all the rest of HLT containers and saves to ESD/AOD. This container is produced during HLT by decoding the MUCTPI data which arrived via the RoIBuilder ROB. There is no need to decode these data again in offline reconstruction, because we just read what HLT read online.
However, in ATR-23992 a wish was expressed to decode the MUCTPI DAQ ROB data during offline reconstruction. This change is implemented here. The same tool is used as online, but the input is the DAQ ROB and the output container is named `LVL1MuonRoIsDAQ`. It is also configured to be saved to ESD/AOD, so in the end we will have both `LVL1MuonRoIs` and `LVL1MuonRoIsDAQ` in the AOD.
cc @masato, @armbrust
Note: This is mostly useful for the reconstruction of actual data straight from P1. In the HLT Reprocessing workflow, the MUCTPI RoIB ROB is overwritten during HLT rerunning with a simulated output, but the DAQ ROB is not and still contains the original data from the original run at P1. Therefore in HLT Reprocessing output these two ROBs correspond to different MUCTPI decisions.https://gitlab.cern.ch/atlas/athena/-/merge_requests/45820Fixing: Online el->caloCluster() method returns always nullptr2021-08-24T16:34:51+02:00Debottam Bakshi GuptaFixing: Online el->caloCluster() method returns always nullptrAs described in ATR-24000 Online el->caloCluster() method currently returns nullptr. Making the final writeHandle of EMClusterTool recordable so it propagates to the reconstruction and xAOD::Electron can link itself to the recorded handl...As described in ATR-24000 Online el->caloCluster() method currently returns nullptr. Making the final writeHandle of EMClusterTool recordable so it propagates to the reconstruction and xAOD::Electron can link itself to the recorded handle. Adding @jodafons , @tbold , @tamartin , @christoshttps://gitlab.cern.ch/atlas/athena/-/merge_requests/45719Integrate eTau and jTau EDM into HLTSeeding2021-08-12T03:04:05+02:00Rafal Bielskirafal.bielski@cern.chIntegrate eTau and jTau EDM into HLTSeedingIntegrate eFex Taus and jFex Taus into the HLTSeeding code, part of ATR-22762.
Changes include:
* Link the (e/j)FexTau containers to L1TriggerResult in L1TriggerResultMaker.
* Implement (e/j)FexTau threshold tools - dummy implementat...Integrate eFex Taus and jFex Taus into the HLTSeeding code, part of ATR-22762.
Changes include:
* Link the (e/j)FexTau containers to L1TriggerResult in L1TriggerResultMaker.
* Implement (e/j)FexTau threshold tools - dummy implementation for now, logic to be filled by L1Calo experts, ATR-23290.
* Implement (e/j)FexTau "RoI unpacker" tools - largely a copy of the eFexEM one. The code duplication can be reduced later once we have more mature implementations of everything, but for now it's fine to have a few very similar tools.
* Integrate the new tools and EDMs in HLTSeeding python configuration.
The jFex Tau tools are commented out from the python configuration for now, because the jTAU thresholds are not yet defined in the L1Menu and running the tools leads to errors. They will be uncommented once the thresholds are available in the menu.
cc @dzanzi, @afaulknehttps://gitlab.cern.ch/atlas/athena/-/merge_requests/45651HLT jet reconstruction for heavy ion events in release 222021-10-09T19:07:56+02:00Yeonju GoHLT jet reconstruction for heavy ion events in release 22This MR is for heavy-ion style HLT jet reconstruction including CaloTower-based HICluster reconstruction and underlying event subtraction with Event Plane. Most part of the implementation have been performed in a new dedicated python fil...This MR is for heavy-ion style HLT jet reconstruction including CaloTower-based HICluster reconstruction and underlying event subtraction with Event Plane. Most part of the implementation have been performed in a new dedicated python file of 'TriggerMenuMT/HLTMenuConfig/Jet/JetHIConfig.py'. Please take a look, @valentem, @ayana and @mrybar. Thank you.https://gitlab.cern.ch/atlas/athena/-/merge_requests/45563B-physics migration of combined dielectron+muon chains, e.g. 'HLT_e9_lhvloose...2021-09-14T21:42:39+02:00Vladimir LyubushkinB-physics migration of combined dielectron+muon chains, e.g. 'HLT_e9_lhvloose_e5_lhvloose_bBeeM6000_mu4_L1BPH-0M9-EM7-EM5_MU6' (ATR-23839)* TrigMultiTrkComboHypo is adopted to look for close-by electrons originated from the same EM cluster (chains with 'L1BPH-0DR3-EM7J15')
* combined dielectron+muon are added to LS2_v1 menu, but we are still waiting for ATR-23965;
hack of ...* TrigMultiTrkComboHypo is adopted to look for close-by electrons originated from the same EM cluster (chains with 'L1BPH-0DR3-EM7J15')
* combined dielectron+muon are added to LS2_v1 menu, but we are still waiting for ATR-23965;
hack of the auto-generated IMEmptyMuonSeq1_Electron can be used in the meantime (add ~lyubushk/public/Trigger/fixIMEmptySeq_bBeeM6000.py to --postInclude option, see ~lyubushk/public/Trigger/test_bBeeM6000.sh for example);
* add more options for Bmumux decays of B_c+ and fix some bugs;
* add entry for di-electron chains in EDM;
* some improvements in the coding style are taken from !44579
CC: @abarton