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
Keep GEMDigiSimLinks after the DIGI step #30257
Keep GEMDigiSimLinks after the DIGI step #30257
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30257/16159
|
A new Pull Request was created by @dildick (Sven Dildick) for master. It involves the following packages: SimMuon/Configuration @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.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 @dildick , if StripDigiSimLink is not used, then drop it with the next occasion independently on size |
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. @silviodonato, @dpiparo (and backports should be raised in the release meeting by the corresponding L2) |
PR description:
RAW and RECO simulated data currently keep the
StripDigiSimLink
objects for GEMs. They are actually not that useful. However, theGEMDigiSimLink
is much more useful as it properly links the GEMSimHit
with theGEMDigi
This PR adds it to the event content after the DIGI step. The size is about the same as theStripDigiSimLink
. After running WF 23234.0:If the
GEMDigiSimLink
takes up too much space, I would propose to dropStripDigiSimLink
, which is not used in the simulation AFAIK.PR validation:
Tested with WF 23234.0
@jshlee