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
Split up GEM and ME0 customizations #13963
Split up GEM and ME0 customizations #13963
Conversation
A new Pull Request was created by @dildick (Sven Dildick) for CMSSW_8_1_X. It involves the following packages: Configuration/StandardSequences @smuzaffar, @civanch, @Dr15Jones, @cvuosalo, @mdhildreth, @cmsbuild, @franzoni, @deguio, @slava77, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
object.simMuonME0Digis = cms.PSet( | ||
initialSeed = cms.untracked.uint32(1234567), | ||
engineName = cms.untracked.string('HepJamesRandom') | ||
) | ||
|
||
from Configuration.StandardSequences.Eras import eras | ||
eras.run3_GEM.toModify( RandomNumberGeneratorService, func=_modifyRandomNumberGeneratorServiceForRun3 ) |
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.
These can now be expressed more simply
eras.run3_GEM.toModify(RandomNumberGeneratorService, simMuonGEMDigis = dict(
initialSeed = cms.untracked.uint32(1234567),
engineName = cms.untracked.string('HepJamesRandom')) )
+1 |
Pull request #13963 was updated. @smuzaffar, @civanch, @Dr15Jones, @cvuosalo, @mdhildreth, @dmitrijus, @cmsbuild, @franzoni, @deguio, @slava77, @vanbesien, @davidlange6 can you please check and sign again. |
Rebased onto CMSSW_8_1_X_2016-04-28-2300. I took out the phase1Pixel and trackingPhase1 from the Phase2 era to resolve merge conflicts https://github.com/cms-sw/cmssw/pull/14180/files#diff-9a04431149d3c6b0186fe8a0216a8463 |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 |
eras.phase2_muon.toModify( RecoLocalMuonFEVT, func=_modifyRecoLocalMuonEventContentForPhase2 ) | ||
eras.phase2_muon.toModify( RecoLocalMuonRECO, func=_modifyRecoLocalMuonEventContentForPhase2 ) | ||
eras.phase2_muon.toModify( RecoLocalMuonAOD, func=_modifyRecoLocalMuonEventContentForPhase2 ) | ||
def _updateOutput( era, outputPSets, commands): |
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.
for the next PR... this should just get moved to normal cff that manage the event content. If the collections are not produced, they won't be part of the event content
@dildick
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.
@davidlange6 Which file is that?
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.
its in fact this same one.. RecoLocalMuon/Configuration/python/RecoLocalMuon_EventContent_cff.py - we hopefully can avoid era statements in the event content
On Apr 29, 2016, at 4:19 PM, Sven Dildick notifications@github.com wrote:
In RecoLocalMuon/Configuration/python/RecoLocalMuon_EventContent_cff.py:
from Configuration.StandardSequences.Eras import eras
-eras.phase2_muon.toModify( RecoLocalMuonFEVT, func=_modifyRecoLocalMuonEventContentForPhase2 )
-eras.phase2_muon.toModify( RecoLocalMuonRECO, func=_modifyRecoLocalMuonEventContentForPhase2 )
-eras.phase2_muon.toModify( RecoLocalMuonAOD, func=_modifyRecoLocalMuonEventContentForPhase2 )
+def _updateOutput( era, outputPSets, commands):@davidlange6 Which file is that?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
+1
|
@slava77 Thanks for prompt response. @kpedro88 @davidlange6 Can we have this integrated soon? Thanks! |
@davidlange6 Thanks! |
As requested by @slava77 in #13880 (comment) this PR splits up the GEM and ME0 customizations. GEMs will be enabled starting Run3 (GE1/1), with (possibly) an extension in Phase2 (GE2/1). ME0 will only be enabled starting Phase2. Including GEMs in the Run2_2017 era may be done in the future if the GE1/1 slice test goes well.
HGCal and DT fail at the DIGI and L1 step respectively in the simulation unfortunately. However, the simple cmsDriver command below does produce a syntactically correct configuration (see #13880 (comment))
@calabria, @jshlee