Remove l1menu customs plus l1bugfix 74 x #10506
Conversation
|
+1 |
|
print it! |
|
@mulhearn - thanks - thats solves the problem |
…plus-l1bugfix-74X Remove l1menu customs plus l1bugfix 74 x
|
@mulhearn , you have removed the overriding of the L1 menu in the heavy ions workflow, but the corresponding L1 menu is not available in any global tag. |
|
@fwyzard |
| @@ -31,6 +31,8 @@ def Base(process): | |||
| # process.GlobalTag.connect = 'frontier://FrontierProd/CMS_CONDITIONS' | |||
| # process.GlobalTag.pfnPrefix = cms.untracked.string('frontier://Frontie#rProd/') | |||
| # | |||
| process.GlobalTag.snapshotTime = cms.string("9999-12-31 23:59:59.000") | |||
There was a problem hiding this comment.
There is no hope to get a gt with the right snapshot time?
There was a problem hiding this comment.
No: this is for the updated L1 menus versions - we can't wait for the GT PRs,
and some L1T menus will never make a GT (eg, the special LowPU L1T menus).
There was a problem hiding this comment.
Do I understand it correctly that these customs never make it to relval
production workflows? Otherwise we can get conditions changing during
relval production.
On Aug 5, 2015 4:28 AM, "Martin Grunewald" notifications@github.com wrote:
In HLTrigger/Configuration/python/CustomConfigs.py
#10506 (comment):@@ -31,6 +31,8 @@ def Base(process):
process.GlobalTag.connect = 'frontier://FrontierProd/CMS_CONDITIONS'
process.GlobalTag.pfnPrefix = cms.untracked.string('frontier://Frontie#rProd/')
- process.GlobalTag.snapshotTime = cms.string("9999-12-31 23:59:59.000")
No: this is for the updated L1 menus versions - we can't wait for the GT
PRs,
and some L1T menus will never make a GT (eg, the special LowPU L1T menus).—
Reply to this email directly or view it on GitHub
https://github.com/cms-sw/cmssw/pull/10506/files#r36283767.
There was a problem hiding this comment.
I think this is not used in production workflows, as it would need to be explcitely called as customisation function.
This is PR #10413 plus a bugfix to remove problems with postLS1 customizations always configuring for stage 1. Once it is shown to work, the bugfix will have to go into 75X and 76X as well.