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
Bugfix in pixel detector's cluster charge re-weighting #23583
Bugfix in pixel detector's cluster charge re-weighting #23583
Conversation
In case no matching template is found, the cluster is stored without re-weighting (was removed before)
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23583/5182 |
A new Pull Request was created by @schuetzepaul (Paul Schuetze) for master. It involves the following packages: SimTracker/SiPixelDigitizer @cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
@schuetzepaul , a minor comment: if you are using LogDebug it is equivalent to #ifdef, #ifdef may be useful if you keep LogInfo |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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 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) |
@civanch Thanks for the quick integration! For my own education, would you mind explaining your comment about #ifdef and LogInfo vs LogDebug? I have some amount of debugging/verbose output in the upcoming FastSim code, and I'd like to know what's the best way to deal with it. Thanks! |
@pmaksim1 just check https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideMessageLogger#LogDebug LogDebug is by default disabled, and is enabled with a proper modification of the MessageLogger options, and defining a flag for the compiler. |
+1 |
Following up on #22911 :
A bug in the re-weighting algorithm of the pixel digitizer was discovered causing the removal of a significant number of clusters.
Technically spoken: If no matching 2D template was found for a cluster, it was removed (all charges set to 0) due to a missing return of the re-weighting function. This happens mainly for low pt tracks, since they have a higher possibility for very large incidence angles, not covered by the templates.
Solution: The re-weighting function returns with an error in case no matching template was found. This pulls the flag
reweighted
tofalse
, causing the signal to be digitized without re-weighting (see here). Therefore the signal is not fully correct in terms of radiation damage, but it's not lost.As noted in #22911 the feature of charge re-weighting is still turned of by default. It can be used with the following lines in the configuration (switching on the Re-weighting and loading the templates via the GT candidate):
The validation of the simulated data with this fix is ongoing.
Interested users: @tvami @tsusa @veszpv @pmaksim1