Treatment of BX in L1T / HLT software for Phase-II

[Martin-Grunewald]

Recently, an inconsistency has been observed in the bunch crossing (BX) usage between L1T and HLT software used in Run 3. Related links:

• CMSHLT Jira issue https://its.cern.ch/jira/browse/CMSHLT-3218
• PR by @missirol to fix Run-3 sw: add BX info to GlobalObjectMap (L1uGT emulation) #47030

The question now is how this is dealt with by Phase-2 (Run-4++) software, both at L1T, emulator and HLT level. In this mattermost thread https://mattermost.web.cern.ch/cms-tsg/pl/nyn8qxmm6pb1bpkz5535i9i1hw @artlbv states that currently (Jan 2025) there is no BX treatment at all.

Even if it is deemed not a priority and to be fixed later, related changes to dataformats and perlocation to downstream modules should be resolved beforehand as it is an intrusive change.

[cmsbuild]

cms-bot internal usage

[cmsbuild]

A new Issue was created by @Martin-Grunewald.

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

cms-bot commands are listed here

[Martin-Grunewald]

assign @cms-sw/l1-l2 @cms-sw/hlt-l2

[Martin-Grunewald]

assign l1,hlt

[cmsbuild]

New categories assigned: l1,hlt

@aloeliger,@epalencia,@Martin-Grunewald,@mmusich you have been requested to review this Pull request/Issue and eventually sign? Thanks

[Martin-Grunewald]

assign upgrade

[cmsbuild]

New categories assigned: upgrade

@Moanwar,@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks