-
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
HGCAL: Change ToA to global time in DIGI #39720
HGCAL: Change ToA to global time in DIGI #39720
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39720/32554
|
A new Pull Request was created by @stahlleiton (Andre Stahl) for master. It involves the following packages:
@Martin-Grunewald, @civanch, @missirol, @clacaputo, @cmsbuild, @AdrianoDee, @srimanob, @mdhildreth, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
-1 Failed Tests: RelVals RelVals
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39720/32556
|
Pull request #39720 was updated. @Martin-Grunewald, @civanch, @missirol, @clacaputo, @cmsbuild, @AdrianoDee, @srimanob, @mdhildreth, @mandrenguyen can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b0cd36/28304/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+reconstruction |
+hlt One question, @stahlleiton : (just for my own understanding)
Why/how does this number of calls change? (I fail to see it from the PR's diff) |
+1 |
Since the value of the time-of-arrival (toa) was changed in the digitizer, then the calls to the random engine changes in:
And since the engine is a pointer to a global engine used across all CMSSW and the seed is changed every time the engine is used, then changing the number of calls to the engine produces different pseudo-random results. |
+1 |
@upgrade-l2 : is there any pending change on this PR for upgrade sign-off? |
+Upgrade |
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. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR changes the definition of the time of arrival at DIGI level to represent the global time at which the signal is detected in the HGCAL hit (instead of been back-propagated to (0,0,0)). To ensure the time distribution is sampled within 25 ns window, a delay on the global time is added depending on the sub-detector equal to: EE=-9 ns, HEfront=-11 ns, HEback=-14 ns and HFNose=-33 ns.
These time delays are checked in the following plot:
The ToA definition is not changed at RECO level, thus the time of reconstructed HGCAL clusters and tracksters is still the time back-propagated to the center (as currently used), to simplify the review of the DIGI changes. The uncalibrated rechit algorithm takes care of the back-propagation and the removal of the time delay.
This is part of the set of updates already announced in the HGCAL DPG meeting (see https://docs.google.com/presentation/d/11AHfmXCauuNehVb7wZkH5JLHSSI_rbgjducatd0IJwU/edit?usp=sharing).
PR validation:
PR was validated using the following cmsDriver command:
cmsDriver.py TTbar_14TeV_TuneCP5_cfi --conditions auto:phase2_realistic_T21 -n 10 --era Phase2C18I13M9 --eventcontent FEVTDEBUG -s GEN,SIM,DIGI --datatier GEN-SIM-DIGI --beamspot HLLHC14TeV --geometry Extended2026D94 --fileout file:step12_HF.root --customise SLHCUpgradeSimulations/Configuration/aging.customise_aging_3000
The expected changes include:
@pfs @rovere @felicepantaleo