Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update GEMPadDigi clustering procedure #27832

Merged
merged 5 commits into from Aug 26, 2019
Merged

Update GEMPadDigi clustering procedure #27832

merged 5 commits into from Aug 26, 2019

Conversation

dildick
Copy link
Contributor

@dildick dildick commented Aug 23, 2019

PR description:

Update of the clustering procedure so it matches the implementation in the GEM optohybrid firmware.

In the current version of the algorithm, cluster finding is segmented into two separate halves of the GE1/1 chambers. Thus, each one of the trigger fibers can transmit clusters only from the half of the chamber that it corresponds to. For GE2/1, there are four separate quarts of the GE2/1 chamber.

This has the downside of being unable to transmit more than 4 clusters when they occur within that side of the chamber, so there will be a slightly higher rate of cluster overflow. For GE2/1 each OH can transmit up to 5 clusters.

Note: GE1/1 does not have 2 physical optohybrids. There is only one optohybrid per chamber, but the firmware sees two independent halves. So nOHGE11_ really means the number of independent optohybrid sectors. On the other hand nOHGE21_ is the actual number of optohybrids on the chamber. However, the emulator should match the firmware, despite this subtle difference.

PR validation:

I tested this pull request on a customized multi-muon gun. I simulated 10 events, each with 100 muons and 100 antimuons propagating between 1.55 < |eta| < 2.15 - to emulate high pileup conditions in the GE1/1 region. Print-outs (not included in the pull request) show

  • Example GE1/1
Analyzing optohybrid 1
	Adding cluster to final collection Re -1 Ri 1 St 1 La 1 Ch 7 Ro 1   bx: 0 pads:  29
	Adding cluster to final collection Re -1 Ri 1 St 1 La 1 Ch 7 Ro 1   bx: 0 pads:  60
	Adding cluster to final collection Re -1 Ri 1 St 1 La 1 Ch 7 Ro 1   bx: 0 pads:  127
	Adding cluster to final collection Re -1 Ri 1 St 1 La 1 Ch 7 Ro 3   bx: 0 pads:  63 64
	Rejecting cluster  Re -1 Ri 1 St 1 La 1 Ch 7 Ro 3   bx: 0 pads:  70 71
Analyzing optohybrid 2
	Adding cluster to final collection Re -1 Ri 1 St 1 La 1 Ch 7 Ro 7   bx: 1 pads:  181
  • Example GE2/1:
Analyzing optohybrid 1
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 2   bx: 0 pads:  207
Analyzing optohybrid 2
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 4   bx: 0 pads:  271 272
Analyzing optohybrid 3
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  61
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  119
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  123
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  244
	Adding cluster to final collection Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  262
	Rejecting cluster  Re 1 Ri 1 St 2 La 1 Ch 11 Ro 5   bx: 0 pads:  265 266 267 268
	Rejecting cluster  Re 1 Ri 1 St 2 La 1 Ch 11 Ro 6   bx: 0 pads:  346
	Rejecting cluster  Re 1 Ri 1 St 2 La 1 Ch 11 Ro 6   bx: 0 pads:  375
Analyzing optohybrid 4

Attention: @tahuang1991 @jiafulow @jshlee

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-27832/11564

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

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

It involves the following packages:

SimMuon/GEMDigitizer

@cmsbuild, @civanch, @kpedro88, @mdhildreth can you please review it and eventually sign? Thanks.
@jshlee, @jhgoh 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

@dildick
Copy link
Contributor Author

dildick commented Aug 23, 2019

This pull request may need to be back-ported for releases targeting Run-3 studies.

@kpedro88
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Aug 23, 2019

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-run-pr-tests/2129/console Started: 2019/08/23 06:05

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1ec19f/2129/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: 2939508
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2939166
  • DQMHistoTests: Total skipped: 341
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 33 files compared)
  • Checked 142 log files, 14 edm output root files, 34 DQM output files

@civanch
Copy link
Contributor

civanch commented Aug 23, 2019

+1

@kpedro88
Copy link
Contributor

+upgrade

@cmsbuild
Copy link
Contributor

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)

@kpedro88
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 4c7700b into cms-sw:master Aug 26, 2019
@dildick dildick deleted the from-CMSSW_11_0_X_2019-08-19-1100-Update-GEM-Cluster-procedure branch September 3, 2019 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants