-
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
[13_0_X] Add L1 Stage2 Digis to Cosmics AOD event content #41150
[13_0_X] Add L1 Stage2 Digis to Cosmics AOD event content #41150
Conversation
A new Pull Request was created by @eyigitba for CMSSW_13_0_X. It involves the following packages:
@perrotta, @rappoccio, @epalencia, @cecilecaillol, @cmsbuild, @aloeliger, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #41149 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-86e0cb/31547/summary.html Comparison SummarySummary:
|
+l1 |
can this be merged as well since #41149 got merged? |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_13_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_1_X is complete. This pull request will be automatically merged. |
PR description:
As discussed in PPDC meeting we want to have L1 objects in Cosmics AOD event content. This PR adds required L1 stage2 digis to cosmics AOD event content.
This will make L1 displaced muon performance studies much easier to perform with cosmics data.
PR validation:
Validated by running reconstruction on cosmics RAW data from 2022 using:
cmsDriver.py reco -s RAW2DIGI,RECO --data --scenario cosmics --eventcontent AOD --filein /store/data/Run2022G/Cosmics/RAW/v1/000/362/363/00000/887de473-401c-4b6d-a9bb-66a32e35f446.root --fileout testAOD.root --conditions 124X_dataRun3_Prompt_v4 -n 1000 --era=Run3
I verified that the required digis now exist in the event content after the changes
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:
This is the backport of #41149