-
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
Lepton time-life info for NanoAOD #43525
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43525/38107
|
A new Pull Request was created by @mbluj for master. It involves the following packages:
@cmsbuild, @vlimant, @jfernan2, @simonepigazzini, @mandrenguyen can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable nano |
hell @mbluj are you able to present this at the upcoming xpog meeting (dec 13) ? |
PhysicsTools/NanoAOD/plugins/LeptonTimeLifeInfoTableProducer.cc
Outdated
Show resolved
Hide resolved
I am participating at L1 workshop, but I can try to prepare a short presentation. |
I prepared a couple of slides, could you, please, give me a slot in agenda of the meeting? |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43525/38289
|
The two last commits address review comments (hopefully):
If the changes in this PR are accepted I will add newly added variables to NanoAOD DQM as this is still missing. |
@vlimant, I wonder if you have had time to review update of this PR? Do you have any further comments? |
PhysicsTools/NanoAOD/plugins/LeptonTimeLifeInfoTableProducer.cc
Outdated
Show resolved
Hide resolved
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4f2664/37588/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
+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 now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
please prepare the backport PR asap |
OK. Can I backport the new typed value map table producer together with this development or two separate PR should be prepared? Or the producer is already backported? |
backport both at the same time please |
For reference: backported to 14_0_X in #44040. |
+1 |
please work on a PR with a test workflow in the nano matrix for this feature ; following the example for MUO, EGM, etc (no need to have it in backport though) |
PR description:
This PR adds a customization to add lepton time-life related information to NanoAOD. The information contains:
All those variables are used in the measurement of CP structure of the Higgs-tau Yukawa coupling and related analyses, e.g. measurement of polarization of Z in decays to taus.
Technically all lepton time-life variables are stored in a newly introduced data-format
TrackTimeLifeInfo
produced by a new producerPATLeptonTimeLifeInfoProducer
(a template class instantiated forpat::Electron
,pat::Muon
andpat::Tau
) and then added by an instance of simple table producer. The PV with BS information is stored with a new instance (forreco::Vertex
) of a simple table producer.In the case of Run-2 input samples the PV with the BS constraint is produced with a custom producer (
PATRefitVertexProducer
) with miniAOD inputs (a newreco::Vertex
collection with one item) as vertices with BS are not available in those samples.In case a given new variable is not computed, e.g. SV for 1-prong taus or variables for a lepton is not passing selection, zeros are stored which are then effectively compressed in an output file.
PR validation:
Validated using 2022 and 2018 TTbar samples with customized default NanoAOD workflow obtained as follows:
Added variables increase size of NanoAOD by ~8.5% (wrt 14_0_0_pre1 default) which is distributed between taus (~3%), electrons and muons (~2% each) and PV with BS (~1%)
In the current setup the variables are added to default workflow with
LepTimeLife
customization defining extended NANO step like this--step NANO:@LepTimeLife
.Presentation at the XPOG meeting: link
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:
It is foreseen to backport to 14_0_X.