Add BeamSpotOnline tags to the Prompt GT

[francescobrivio]

Description

As reported in Issue#41456, the BeamSpotFromDB is one of the main offenders concerning the LogErrors and LogWarning emitted during Prompt reco.

Solution

As nicely debugged by @mmusich in #41456 (comment), and after some private discussion, it was decided that the best way to fix this is to include the BeamSpotOnline tags (which are already present in the HLT/Express GTs) in the Prompt GT:

• BeamSpotOnlineHLT, Rcd: BeamSpotOnlineHLTObjectsRcd
• BeamSpotOnlineLegacy, Rcd: BeamSpotOnlineLegacyObjectsRcd

FYI @gennai @dzuolo

[francescobrivio]

assign alca,db

[cmsbuild]

New categories assigned: db,alca

@francescobrivio,@francescobrivio,@saumyaphor4252,@saumyaphor4252,@tvami,@tvami you have been requested to review this Pull request/Issue and eventually sign? Thanks

[cmsbuild]

A new Issue was created by @francescobrivio .

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

cms-bot commands are listed here

[tvami]

It's a bit counterintuitive to add HLT tags to the Prompt GT. Was this decided so there is no need for code changes (which I guess would be the more intuitive solution)?

[mmusich]

Was this decided so there is no need for code changes

The need of adding the HLT tags originates from the need of monitoring in prompt the difference between the online and offline beamspots.
When in Run2 the online BS was saved in the scalers RAW data, there was no need for that. Now that the arbitration mechanism at HLT uses the online tags that's the only reliable way to get the information as consumed online.
The alternative of course is dropping the monitoring (which I am not super keen about) or find a different mechanism to save post-facto the onlineBS (suggestions are welcome).

[francescobrivio]

The need of adding the HLT tags originates from the need of monitoring in prompt the difference between the online and offline beamspots. When in Run2 the online BS was saved in the scalers RAW data, there was no need for that. Now that the arbitration mechanism at HLT uses the online tags that's the only reliable way to get the information as consumed online. The alternative of course is dropping the monitoring (which I am not super keen about) or find a different mechanism to save post-facto the onlineBS (suggestions are welcome).

Thanks Marco, indeed in the description I forgot to mention that this will restore the possibility to monitor in prompt the difference between online and PCL/offline.

[mmusich]

being tested in dmwm/T0#4817

[mmusich]

This issue is ready to be signed (and closed).

• Update run3 data GTs #41609 provides the needed conditions in the master release
• Update production Prompt GT to 130X_dataRun3_Prompt_v3 dmwm/T0#4820 updated the Tier-0 production configuration accordingly

[francescobrivio]

+1

• see Add BeamSpotOnline tags to the Prompt GT #41459 (comment)

[cmsbuild]

This issue is fully signed and ready to be closed.