Fix z0 calculation in emerging jets trigger
The z0 calculation in TrigJetEJsHypoTool
did not take into account the beamspot z position which led to large rates for periods with significant beamspot shifts (see ATR-27603). The implementation now aligns with the recommended way to compute z0 (see https://twiki.cern.ch/twiki/bin/view/AtlasProtected/TrackingCPRecsRun2Final#Calculating_z0_and_d0_significan)
This will lead to rate changes. I am not sure the exact protocol for updating active chains so please let me know if there are additional approvals or discussions needed.
Tagging @cpollard, @jmasik, @strom, @dguest, @ggustavi, @mgenest
Merge request reports
Activity
added 23.0 JetEtmiss Trigger TriggerJet review-pending-level-1 labels
mentioned in merge request !63288 (closed)
CI Result SUCCESS (hash 26d4cfb9)Athena externals cmake make tests Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 71931]added urgent label
Thanks @jburzyns - you're right that this will change chain counts in general, if not in the limited number of data events we test in the CI. Will apply the label manually here. But no other updates are needed in this case.
added changes-trigger-counts label
added review-approved label and removed review-pending-level-1 label
added review-approved-point1 label
mentioned in commit 77acdeb7
mentioned in merge request !63310 (merged)
mentioned in commit 7d6bdf0d
mentioned in merge request !63505 (closed)