Allow folder tags to be overriden using the dbOverrides argument

LATOME firmware version v6 (HLS) is currently under testing. Processing data to ensure that there are no simulation mis matches with L1Calo can be done with this monitoring script but changes to the LAr readout mean that a special db tag must be used.

Adding support to --dbOverrides for overriding a tag

Tagging @will @hcai @admilic for information

This merge request affects 1 package:

• Trigger/TrigT1/TrigT1CaloMonitoring

This merge request affects 1 file:

• Trigger/TrigT1/TrigT1CaloMonitoring/share/L1CaloPhase1Monitoring.py

Adding @thompson ,@will as watchers

added 24.0 DQ L1Calo Trigger review-pending-level-1 labels

Thanks @rhowen for creating the MR!

Also tagging @pavol and @ekay here.

CI Result SUCCESS (hash 6311c2ad)

	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 (remote access info)

Just to say I discussed this MR with Rhys and given that there is a very similar argument already, called --dbOverrides, instead we will extend that argument to support specifying a tag to override. So the way you will want to use it is:

--dbOverrides "/LAR/Identifier/LatomeMapping:LARIdentifierLatomeMapping-fw6"

added 1 commit

• 07b3ec5b - Generalise dbOveride

Compare with previous version

changed title from Add option for LAr FW 6 in L1Calo monitoring to Allow folder tags to be overriden using the dbOverrides argument

changed the description

This merge request affects 1 package:

• Trigger/TrigT1/TrigT1CaloMonitoring

This merge request affects 1 file:

• Trigger/TrigT1/TrigT1CaloMonitoring/share/L1CaloPhase1Monitoring.py

Adding @thompson ,@will as watchers

CI Result SUCCESS (hash 07b3ec5b)

	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 (remote access info)