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
Reduced muon validation for PhaseII Upgrade high PU scenarios (90X) #16669
Reduced muon validation for PhaseII Upgrade high PU scenarios (90X) #16669
Conversation
A new Pull Request was created by @calabria (Cesare) for CMSSW_9_0_X. It involves the following packages: Validation/RecoMuon @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Pull request #16669 was updated. @civanch, @mdhildreth, @dmitrijus, @cmsbuild, @vanbesien, @davidlange6 can you please check and sign again. |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
|
+1 |
+1
See more notes on technical performance in #16670 (comment) |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
@davidlange6 |
@@ -58,6 +58,13 @@ def customiseFor14833(process): | |||
producer.includeME0 = cms.bool(False) | |||
return process | |||
|
|||
def customiseFor16670(process): |
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.
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.
we plan to migrate the HLT menu to CMSSW 9.0.x once pre1 is out.
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.
any reason a fillDescription does not work here? (with the nice feature of being desirable for the long term)
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.
it's a typical problem of no easy fix.
There is not fillDescriptions for this tool.
It's an ESProducer, it currently gets a tool to be configured from the plugin factory during ::produce call, the needed parameter is a sub-tool of the tool to be configured.
So, some significant development and some refactoring might be necessary.
@Dr15Jones do we have an example of what to do in this case?
I don’t follow the complexity (yet) It looks like ESSources support fillDescriptions. Is the the HLT config not a standalone ESSource as it is in
TrackingTools/TrackAssociator/python/DetIdAssociatorESProducer_cff.py - but ok, I haven’t tried this myself...
in fact, is this parameter in the menu at all? I don’t really see it aside from here
https://github.com/cms-sw/cmssw/blob/53327033fb356b2a704464439ce79fa47a9d1678/HLTrigger/HLTanalyzers/python/HLT_ES_cff.py
is this somehow derived from online menus or editable in the release (unedited since <62x)
… On Nov 29, 2016, at 2:59 PM, Slava Krutelyov ***@***.***> wrote:
@slava77 commented on this pull request.
In HLTrigger/Configuration/python/customizeHLTforCMSSW.py:
> @@ -58,6 +58,13 @@ def customiseFor14833(process):
producer.includeME0 = cms.bool(False)
return process
+def customiseFor16670(process):
it's a typical problem of no easy fix.
There is not fillDescriptions for this tool.
It's an ESProducer, it currently gets a tool to be configured from the plugin factory during ::produce call, the needed parameter is a sub-tool of the tool to be configured.
So, some significant development and some refactoring might be necessary.
@Dr15Jones do we have an example of what to do in this case?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
At HLT we have currently exactly 5 parameters for any
So any missing parameters must either already be inserted by fillDescriptions, or via existsAs treated in the code, or conditionally on the value of |
@slava77 to my knowledge, we've never come up with a satisfactory mechanism of dealing with configuration parameters from internal plugins of modules. |
Indeed. Would it make sense to add a static |
@davidlange6 |
I'd rather we finally have a general way of handling plugins, say in a month or so, and live with a python customisation in the meantime. |
after the discussion in the ORP, we just decided to keep this PR as it is..
… On Nov 29, 2016, at 4:56 PM, Slava Krutelyov ***@***.***> wrote:
@davidlange6
would existsAs solution be acceptable to you?
(it was suggested by @Martin-Grunewald )
This is simple enough that I can see it implemented quickly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
+1 |
@fwyzard I don't have any plans for a 'general way' of handling plugins. The difficulty is the validator object created in the The extremely wide diversity of how plugins are configured (on top of the pervasiveness of plugins) makes a general solution extremely difficult. |
@kpedro88