Option to write out all ALCTs and CLCTs

[dildick]

PR description:

Current CSC trigger simulation only allows for max 2 ALCTs and max 2 CLCTs per chamber. MC studies are ongoing that investigate possibilities to trigger on exotic signatures which produce >2 ALCTs or >2 CLCTs. Such signatures may include long-lived particles that decay to multiple muons.

This PR introduces an option in the CSC trigger to write out specific ALCT and CLCT collections with the label "All" for such exotica studies. These collections are only useful when MAX_ALCTS_PER_PROCESSOR and MAX_CLCTS_PER_PROCESSOR is greater than 2. By default the option is turned off, so there is no change in the trigger performance.

PR validation:

Tested it with a 2026 runTheMatrix command.

if this PR is a backport please specify the original PR:

N/A

@tahuang1991

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28467/12904

• This PR adds an extra 28KB to repository

Code check has found code style and quality issues which could be resolved by applying following patch(s)

• code-format:
  https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28467/12904/code-format.patch
  e.g. curl https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28467/12904/code-format.patch | patch -p1
  You can also run scram build code-format to apply code format directly

[dildick]

I fixed this in my last commit.

[dildick]

@fabiocos Is the cmsbuild state machine stuck in this PR?

[fabiocos]

code-checks

[cmsbuild]

The code-checks are being triggered in jenkins.

[cmsbuild]

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-28467/12965

• This PR adds an extra 8KB to repository

[cmsbuild]

A new Pull Request was created by @dildick (Sven Dildick) for master.

It involves the following packages:

L1Trigger/CSCTriggerPrimitives

@cmsbuild, @rekovic, @benkrikler can you please review it and eventually sign? Thanks.
@valuev, @ptcox, @Martin-Grunewald this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

[fabiocos]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/3696/console Started: 2019/11/29 15:04

[cmsbuild]

+1
Tested at: 2118774
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6369c1/3696/summary.html

[fabiocos]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/3819/console Started: 2019/12/05 16:52

[fabiocos]

@rekovic could you please have a look?

@dildick this PR in its default configuration does not modify anything. What is the expected increase in output size in case the flags are switched to true?

[dildick]

That depends on the scenario. In low-pileup scenarios the "All" CLCT and ALCT collections will be just copies of the standard CLCT and ALCT collections. At PU200, there could be many more CLCTs and ALCTs per chamber... So the size could increase with a factor 2 to perhaps even 5. But in any case, the flags writeOutAllCLCTs and writeOutAllALCTs should not be set to True for any official MC production.

[cmsbuild]

+1
Tested at: 2118774
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6369c1/3819/summary.html

[cmsbuild]

Comparison job queued.

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6369c1/3819/summary.html

Comparison Summary:

• No significant changes to the logs found
• Reco comparison results: 0 differences found in the comparisons
• DQMHistoTests: Total files compared: 34
• DQMHistoTests: Total histograms compared: 2800084
• DQMHistoTests: Total failures: 1
• DQMHistoTests: Total nulls: 0
• DQMHistoTests: Total successes: 2799742
• DQMHistoTests: Total skipped: 341
• DQMHistoTests: Total Missing objects: 0
• DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
• Checked 147 log files, 16 edm output root files, 34 DQM output files

[rekovic]

+1

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2)

[fabiocos]

+1