-
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
[12.4.X] Fix to "Update SiStrip and TkAlignment ALCARECO event content for Run3" #38591
[12.4.X] Fix to "Update SiStrip and TkAlignment ALCARECO event content for Run3" #38591
Conversation
type trk,bugfix |
urgent |
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_4_X. It involves the following packages:
@malbouis, @yuanchao, @cmsbuild, @francescobrivio, @ChrisMisan, @tvami 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-c38956/25973/summary.html Comparison SummarySummary:
|
+alca
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_5_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #38590
PR description:
Unfortunately PR #38416 aimed to update the event content of the input
ALCARECO
event contents to use S/W FED 1023 information instead of SCAL for all the relevant SiStrip and TkAlignment alcas contained two bugs:A
is assigned to another variableB
, if an operation is done onB
, the attributes ofA
are changed as well. This has resulted in applying the removal of the content of the_run3_common_removedCommands
list even for eras <= Run2.ConfigBuilder
uses the*_noDrop
version of theALCARECO
event content to build the list of products to keep, so the instructions gated via therun3_common
modifier were not effective.cmssw/Configuration/Applications/python/ConfigBuilder.py
Line 1298 in 36d3f6f
As a result of the two bugs, the list of event products to be kept is now wrong for all eras.
This PR resolves the issue.
PR validation:
Test running:
runTheMatrix.py -l 1000.0, 136.874, 138.4 --ibeos
and checked the event content of the
SiStripCalMinBias
ALCARECO file, in order to test the Run1, Run2 and Run3 eras.In addition I've also produced ALCARECO data, starting from RAW and the ConfigDP machinery using the command:
python3 Configuration/DataProcessing/test/RunExpressProcessing.py --nThreads 8 --scenario ppEra_Run3 --global-tag 124X_dataRun3_Express_v3 --lfn root://eoscms.cern.ch//eos/cms/tier0/store/data//Run2022A/MinimumBias/RAW/v1/000/352/929/00000/18df5589-67c8-45e5-ac84-7fd2472de50a.root --fevt --dqmio --alcarecos SiStripCalMinBias
and obtained the right event content:
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:
verbatim backport of #38590