hardcoded list of L1T algorithms to monitor in L1TStage2uGTTiming

[mmusich]

The L1T DQM module L1TStage2uGTTiming is configured such that it takes the list of algorithms to monitor from a static python configuration file:

cmssw/DQM/L1TMonitor/python/L1TStage2uGTTiming_cfi.py

Lines 12 to 23 in 6edd3ed

	"L1_SingleMu22_BMTF",
	"L1_SingleMu22_OMTF",
	"L1_SingleMu22_EMTF",
	"L1_SingleIsoEG28er1p5",
	"L1_SingleIsoEG32er2p5",
	"L1_SingleEG40er2p5",
	"L1_SingleEG60",
	"L1_SingleTau120er2p1",
	"L1_SingleJet180",
	"L1_ETMHF130",
	"L1_HTT360er",
	"L1_ETT2000"

This implies that whenever we start exercising offline a workflow that didn't employ a L1T menu including these algorithms, that module becomes very noisy, complaining about:

 Algo "L1_XXX" not found in the trigger menu L1Menu_YYYY. Could not retrieve algo bit number.

This issue was discussed already a couple of times in the past in scattered cmssw PR-s, e.g.: #41629 (comment) or #41972 (comment) or #43378 (comment).

A possibility to reduce the amount of log is of course to silence the warning. Otherwise some smarter algorithm to retrieve the list of algos to monitor could be devised (e.g. process modifier / era steered plain configuration files or directly a list stored int he conditions DB).

[cmsbuild]

A new Issue was created by @mmusich Marco Musich.

@makortel, @smuzaffar, @rappoccio, @Dr15Jones, @antoniovilela, @sextonkennedy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[mmusich]

assign DQM/L1TMonitor

[cmsbuild]

New categories assigned: dqm

@rvenditti,@syuvivida,@tjavaid,@nothingface0,@antoniovagnerini you have been requested to review this Pull request/Issue and eventually sign? Thanks

[mmusich]

@cms-sw/l1-l2 FYI

[mmusich]

While investigating issue #46526, I saw in the log of that tarball, a lot of messages akin to the ones discussed here, of the type:

%MSG
%MSG-w L1TStage2uGTTiming:   L1TStage2uGTTiming:l1tStage2uGTTiming@streamBeginRun 27-Oct-2024 17:08:03 CET  Run: 387326 Stream: 0
Algo "L1_SingleIsoEG28er1p5" not found in the trigger menu L1Menu_CollisionsHeavyIons2024_v1_0_5. Could not retrieve algo bit number.
%MSG
%MSG-w L1TStage2uGTTiming:   L1TStage2uGTTiming:l1tStage2uGTTiming@streamBeginRun 27-Oct-2024 17:08:03 CET  Run: 387326 Stream: 0
Algo "L1_SingleTau120er2p1" not found in the trigger menu L1Menu_CollisionsHeavyIons2024_v1_0_5. Could not retrieve algo bit number.
%MSG
%MSG-w L1TStage2uGTTiming:   L1TStage2uGTTiming:l1tStage2uGTTiming@streamBeginRun 27-Oct-2024 17:08:03 CET  Run: 387326 Stream: 0
Algo "L1_ETMHF130" not found in the trigger menu L1Menu_CollisionsHeavyIons2024_v1_0_5. Could not retrieve algo bit number.
%MSG
[...]

PR #45242 (mostly) solved the issue for standard pp 2024.
Can we have a similar PR also the HIon case?
Cc: @cms-sw/l1-l2 @eyigitba @slaurila @icali @mandrenguyen

[cmsbuild]

cms-bot internal usage

[mmusich]

Can we have a similar PR also the HIon case?

I proposed something at #46590