Regex fix for HI Run chains in muon monitoring

Correct regex for HLT chains to allow for HI chains to not be excluded in muon offline monitoring.

added bugfix label

assigned to @vippolit, @okumura, @sshaw, and @pdougan

Possible Fix for ATR-27787

This merge request affects 1 package:

• Trigger/TrigMonitoring/TrigMuonMonitoring

This merge request affects 1 file:

• Trigger/TrigMonitoring/TrigMuonMonitoring/python/TrigMuonEfficiencyMonConfig.py

added 23.0 DQ Trigger review-pending-level-1 labels

CI Result SUCCESS (hash 38bbcb71)

	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 77229]

Changes look fine from L1 perspective - Approving.

Cheers, Steffen (L1)

added review-approved label and removed review-pending-level-1 label

Hi @pdougan, thanks for the MR. Can you just add to the description what set of chains this MR addresses? It removes any 2mu chains wrt 2mu14 before but what are the chains L1MU[:letter:]? cheers Jiri

@jmasik the idea is to make sure muon trigger monitoring is configured correctly also for HLT chains devised for the heavy-ions run. The current regexps are not general enough to work for HLT_2mu4_L12MU3V (code crashes), and for chains where the L1 seed does not end with a number - for example, L1_MU3V_VTE50 mistakenly is considered as L1_MU3V_VTE.

As a reference, the offline monitoring for heavy ions run is supposed to monitor the following chains:

HLT_mu6_L1MU3V
HLT_mu8_L1MU5VF
HLT_mu10_L1MU8F
HLT_2mu4_L12MU3V
HLT_mu4_mu4noL1_L1MU3V
HLT_mu4_L1MU3V_VTE50
HLT_mu4_L1MU3V_VjTE50
HLT_mu4_L1MU3V_VjTE50_GAP_AANDC

Let me know if I answered your question.

added review-approved-tier0 label

resolved all threads

added review-approved-point1 label

mentioned in commit 03749f68

merged

mentioned in merge request !65510 (merged)

mentioned in merge request !65591 (merged)