-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Disabled looper reconstruction in HI Eras for Run3_pp_on_PbPb and Run2… #38288
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
Disabled looper reconstruction in HI Eras for Run3_pp_on_PbPb and Run2… #38288
Conversation
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38288/30445 ERROR: Unable to merge PR. See log https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38288/30445/cms-checkout-topic.log |
…Pb_and_Run2_pp_on_AA_2018_trackingNoLoopers
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38288/30446
|
|
A new Pull Request was created by @sayanchatterjee38 (SAYAN CHATTERJEE) for master. It involves the following packages:
@cmsbuild, @perrotta, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
type tracking |
|
assign reconstruction |
|
please test |
|
New categories assigned: reconstruction @jpata,@slava77,@clacaputo you have been requested to review this Pull request/Issue and eventually sign? Thanks |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-21c301/25365/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
|
|
If I recall correctly, the discussion in the previous PR was if this should also be disabled for the other years in Run2. |
I think the PR as is can go, but it would still be nice to check on the other periods and adjust accordingly if possible. |
|
Hi Marco, Joosep, From my side, I think it is best if we could focus our efforts in the HI tracking group on getting everything ready for Run 3 at the moment. Checking the earlier eras will take a little time, so I would suggest we proceed forward with this PR for now and then revisit the other earlier, lower priority, eras at a later date. Perhaps we could create an issue on github so that we do not forget in the future? |
Sure that's the spirit of my earlier comment #38288 (comment).
There's already an open issue about it: #35758. |
|
+reconstruction
|
|
+1 |
|
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 be automatically merged. |
PR description:
Title: Disabled looper reconstruction in HI Eras for Run 3_pp_on_PbPb and Run2_2018_pp_on_AA
Description: This PR has disabled looper reconstruction from HI Eras after checking timing and CPU usage, tracking efficiency, fake, multiple, non-primary reconstructions fractions for peripheral and central events. Also, the same checks were performed in the MinimumBias dataset produced for 1000 events. Please, see slides 1-9 from here [1].
No significant changes were observed in event and track variables while removing the No-Looper condition except for the Hit count distribution.
An issue had been raised already regarding disabling looper reconstruction for HeavyIons. Please look here [2] for detail.
Link for the HI Trackin POG:
[1] https://indico.cern.ch/event/1153062/contributions/4841907/attachments/2429416/4159748/NoLooper_HITracking.pdf
Link for the issue:
[2] #35758
PR validation:
Run time observations and a detailed study of each track variable have been performed with enabling and disabling trackingNoLoopers. We have also performed a detailed comparison of tracking efficiency, fake, multiple, and nonprimary reconstruction fractions for central, peripheral, and minimum bias events with enabling and disabling trackingNoLoopers.
If this PR is a backport please specify the original PR and why you need to backport that PR:
N/A
cc: @mandrenguyen, @abaty, @CesarBernardes