-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add GEN-SIM information to resonant di-muon TkAl ALCARECO producers #45357
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45357/40778
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@cmsbuild, @consuegs, @perrotta, @saumyaphor4252 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b7006c/40182/summary.html
Comparison SummarySummary:
|
+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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The goal of this PR is to add
GEN-SIM
related branches to the outputs of several Tracker Alignment ALCARECO producers (using resonant di-muon inputs).The main goal is to be able to produce MC-truth based validations like the ones shown here readily from ALCARECO samples instead of relying on scarce and not very easily available
GEN-SIM-RECO
samples.A similar request was done for analysis purposes e.g. in this ticket.
To limit the output size, we don't add the whole
genParticles
collection, but just the particles withabs(pdgId) == 13
.In order to do that some gymnastics with the
outputCommands
is required. A simpler solution might entail adding directly a new event contentGeneratorInterfaceALCARECO
here.The increase of data volume (limited by construction only to the MC samples, since the added branches are not available in data) is marginal (estimated in less than 1% on 100 input events).
PR validation:
Run the following command:
runTheMatrix.py --what upgrade -l 12842.0 -t 4 -j 8 --nEvents=100
to produce an input file, then analyzed withSagittaBiasNtuplizer
(introduced back then at PR #44282) by using this patch:and analyzed with:
cmsRun SagittaBiasNtuplizer_cfg.py myfile=file:../../../12842.0_ZMM_13+2024/TkAlDiMuonAndVertex.root
. Finally the resulting output ntuple has been checked for having appropriate branches filled.If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport, but can be backported if there's interest for the 2024 MC production.