-
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
pass isRepacked flag to config builder if set in a scenario #12326
pass isRepacked flag to config builder if set in a scenario #12326
Conversation
…to true (unless an override is provided)
…(more parameters and changes need to be made in WMCore and in T0 projects), only for local tests
@cmsbuild please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @slava77 (Slava Krutelyov) for CMSSW_7_5_X. pass isRepacked flag to config builder if set in a scenario It involves the following packages: Configuration/DataProcessing @cmsbuild, @franzoni, @davidlange6 can you please review it and eventually sign? Thanks. |
-1 Tested at: a8875ad ---> test TestConfigDP had ERRORS you can see the results of the tests here: |
oops, fix is coming soon |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Pull request #12326 was updated. @cmsbuild, @franzoni, @davidlange6 can you please check and sign again. |
no changes appear in jenkins tests as expected. |
@@ -29,6 +29,8 @@ def __init__(self): | |||
self.alcaRecos = None | |||
self.PhysicsSkims = None | |||
self.dqmSeq = None | |||
self.setRepacked = False | |||
self.isRepacked = False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slava77 - I think this would be more consistent if the default of isRepacked here is True (as that is default elsewhere in the PR)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On 11/10/15 12:04 AM, David Lange wrote:
In Configuration/DataProcessing/test/RunPromptReco.py
#12326 (comment):@@ -29,6 +29,8 @@ def init(self):
self.alcaRecos = None
self.PhysicsSkims = None
self.dqmSeq = None
self.setRepacked = False
self.isRepacked = False
@slava77 https://github.com/slava77 - I think this would be more
consistent if the default of isRepacked here is True (as that is default
elsewhere in the PR)
I'm not sure I understand the logic.
As defined here, the defaults in this file leave it to the corresponding
scenarios to set their values.
The isRepacked has no effect if setRepacked is false.
If the defaults need to be reset (the main purpose of these flags here),
and so far it's only needed in HI, it would be reset to false.
I can change, if you confirm that you still want it at a true value.
(the file is useful only in local tests; in T0 perspective, these flags
are invisible)
—
Reply to this email directly or view it on GitHub
https://github.com/cms-sw/cmssw/pull/12326/files#r44378627.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah - good point. Ok - thanks
…gn626/hiRepackSettings pass isRepacked flag to config builder if set in a scenario
The python config Configuration/DataProcessing/test/RunPromptReco.py, which is useful in local tests,
has options --isRepacked or --isNotRepacked to override the isRepacked parameter.
Passing arguments to the T0 setup is more complicated and the flexibility to choose repacked or non-repacked inputs is not available with this PR.
The easiest is to introduce a new scenario (e.g. HeavyIonsRun2frompp )