-
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
Make repack process be able to generate new data tiers: L1SCOUT, HLTSCOUT #44380
Make repack process be able to generate new data tiers: L1SCOUT, HLTSCOUT #44380
Conversation
A new Pull Request was created by @haozturk for CMSSW_14_0_X. It involves the following packages:
@fabiocos, @davidlange6, @antoniovilela, @cmsbuild, @rappoccio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
cms-bot internal usage |
Pull request #44380 was updated. @rappoccio, @davidlange6, @cmsbuild, @antoniovilela, @fabiocos can you please check and sign again. |
backport of #44381 |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-a5a44e/38169/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_1_X is complete. This pull request will be automatically merged. |
@drkovalskyi @germanfgv |
PR description:
This PR updates the REPACK process such that it is able to generate two new data tiers:
HLTSCOUT
andL1SCOUT
in addition toRAW
. I've updated the event content ofHLTSCOUT
andL1SCOUT
such that they inherit their output commands fromHLTriggerRAW
andL1TriggerRAW
respectively. Additionally, I've included the output commands of L1SCOUT and HLTSCOUT in the output module of the Repack process.I've coordinated with @drkovalskyi @germanfgv @dynamic-entropy on this work.
Related tickets:
PR validation:
I used
Configuration/DataProcessing/test/RunRepack.py
for testing. I added a new option to this scriptIf 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:
Original PR: #44381