[13_0_X] Prevent producing EMTFTrack if only muon shower was unpacked

[eyigitba]

PR description:

This is a quick PR to fix something I missed in #41993. I should have made it so that no EMTFTrack is produced for muon shower only DAQ blocks. Now this is fixed.

This is a backport of #42172

I don't know which release will be used when LHC restarts, but this backport might be necessary for some re-emulation studies with 2023 data.

PR validation:

Validated by running on recent data, behaves expectedly.

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

[cmsbuild]

A new Pull Request was created by @eyigitba for CMSSW_13_0_X.

It involves the following packages:

• EventFilter/L1TRawToDigi (l1)

@epalencia, @cmsbuild, @aloeliger can you please review it and eventually sign? Thanks.
@dinyar, @missirol, @thomreis, @Martin-Grunewald this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

• Backported from Prevent producing EMTFTrack if only muon shower was unpacked #42172

[aloeliger]

backport of #42172

[aloeliger]

please test

[cmsbuild]

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-10ca9d/33801/summary.html
COMMIT: 2c77272
CMSSW: CMSSW_13_0_X_2023-07-20-1100/el8_amd64_gcc11
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/42319/33801/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

• You potentially removed 3 lines from the logs
• Reco comparison results: 7 differences found in the comparisons
• DQMHistoTests: Total files compared: 49
• DQMHistoTests: Total histograms compared: 3287688
• DQMHistoTests: Total failures: 6
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 3287660
• DQMHistoTests: Total skipped: 22
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
• Checked 213 log files, 164 edm output root files, 49 DQM output files
• TriggerResults: no differences found

[aloeliger]

@eyigitba Same question as #42322:

Is this dependent on having backported the fix to bx-vectors in #42214 ? Would you like me to prepare a backport of that for these PRs to run with?

[eyigitba]

@aloeliger , same answer as well. We should backport that PR too

Hi @aloeliger yes, that should also be backported along with this. I forgot about that. Thanks for reminding

[aloeliger]

@eyigitba Same question as #42322:

Is this dependent on having backported the fix to bx-vectors in #42214 ? Would you like me to prepare a backport of that for these PRs to run with?

Ahh, I put this on the wrong PR, this is not an issue for this PR, but for #42321. In any case, the BX vector check fix is backported and going through tests now, so this PR should be fine.

[aloeliger]

+l1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_3_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

[eyigitba]

and I also responded without checking the PR :). You're right it's related to the other one

[perrotta]

+1

• 13_1_X backport was already merged