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
decouple EventContent_cff load from general purpose use of Merge.py #22937
decouple EventContent_cff load from general purpose use of Merge.py #22937
Conversation
A new Pull Request was created by @slava77 (Slava Krutelyov) for CMSSW_10_1_X. It involves the following packages: Configuration/DataProcessing @cmsbuild, @franzoni, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@cmsbuild please test forgotten commit is not in place |
The tests are being triggered in jenkins. |
Pull request #22937 was updated. @cmsbuild, @franzoni, @fabiocos, @davidlange6 can you please check and sign again. |
hi @slava77 - who is importing Merge.py that leads to this affecting RunPromptReco.py? That is not a coupling that one would naively expect |
On 4/11/18 1:37 PM, David Lange wrote:
hi @slava77 <https://github.com/slava77> - who is importing Merge.py
that leads to this affecting RunPromptReco.py? That is not a coupling
that one would naively expect
Configuration/DataProcessing/python/Scenario.py
and it goes on from there into the T0 setup
|
Thanks! I didn't find that from lxr for some reason. That solves the mystery from before/during dinner..
… On Apr 11, 2018, at 10:42 PM, Slava Krutelyov ***@***.***> wrote:
On 4/11/18 1:37 PM, David Lange wrote:
> hi @slava77 <https://github.com/slava77> - who is importing Merge.py
> that leads to this affecting RunPromptReco.py? That is not a coupling
> that one would naively expect
>
Configuration/DataProcessing/python/Scenario.py
and it goes on from there into the T0 setup
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Comparison job queued. |
Comparison is ready Comparison Summary:
|
backport of #22938 |
bugfix |
tested in master, see comments there |
+operations |
This pull request is fully signed and it will be integrated in one of the next CMSSW_10_1_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_10_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This should resolve #22933
The immediate problem is for Configuration/DataProcessing/python/Scenario.py, which defines the T0 config driver for production workflows:
This fix simply restricts loading of the EventContent_cff in the Merge.py only in merging context for NANO AOD purposes.
Tests:
python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunMerge.py --input-files file:a.root --output-file file:b.root --mergeNANO
and then config dump to see that the result is as expected. The RunMerge is also made aware of mergeNANO.
python $CMSSW_BASE/src/Configuration/DataProcessing/test/RunPromptReco.py --scenario ppEra_Run2_2017_pp_on_XeXe --reco --aod --miniaod --dqmio --global-tag 92X_dataRun2_Express_v7 --lfn=file:raw.root
and then dump to see that _hiCentrality name actually shows up in the keep statements