-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Raising clusterChecker threshhold slightly for Heavy Ion collisions #25189
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25189/7190 |
A new Pull Request was created by @abaty for master. It involves the following packages: RecoTracker/TkSeedGenerator @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
I looked at the slides and this appears to be a somewhat straightforward "+1" |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
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) |
+1 |
Backport of #25189 (raising cluster checker threshold for HI events) for 10_3_X
We have found that the default parameter 'maxNumberOfCosmicClusters' is causing a few very central heavy ion collisions to bail on the tracking, although these events appear to be good physics events. We would like to raise this threshhold from 400k to 500k to prevent any bias to physics. More information on the investigation of these very large events that the tracking is bailing on is given here:
https://www.dropbox.com/s/pgfp21e2329ly69/MonsterEventInvestigation_Nov10.pdf?dl=0
Two of these events, which normally have the tracking not run, as well as a RECO config for testing can be found here:
/afs/cern.ch/user/a/abaty/public/forClusterCheckPR
A backport PR for 10_3_1 will follow shortly.
@mandrenguyen @icali @echapon @mverwe