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
Adding general track to ALCARECO for muonalign #15221
Adding general track to ALCARECO for muonalign #15221
Conversation
A new Pull Request was created by @lpernie (Luca) for CMSSW_8_1_X. It involves the following packages: Alignment/CommonAlignmentProducer @ghellwig, @franzoni, @cerminar, @fabozzi, @cmsbuild, @srimanob, @mmusich, @hengne, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are list here #13028 |
Should I rebase it? |
@lpernie, yes, this needs a rebase, but be careful that in your current version there are regressions in |
f03ac4a
to
a047260
Compare
Done! |
@lpernie,
can you please get it back? Marco |
@@ -75,9 +75,6 @@ | |||
from Calibration.HcalAlCaRecoProducers.ALCARECOHcalCalNoise_cff import * | |||
#HCAL calibration iterative PhiSym | |||
from Calibration.HcalAlCaRecoProducers.ALCARECOHcalCalIterativePhiSym_cff import * | |||
# HCAL isolated bunch | |||
from Calibration.HcalAlCaRecoProducers.ALCARECOHcalCalIsolatedBunchFilter_cff import * | |||
|
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.
@lpernie also this needs to get back
Ok, I just added it back. I hope I did correctly. |
@@ -170,10 +167,12 @@ | |||
pathALCARECOHcalCalIsoTrkFilter = cms.Path(seqALCARECOHcalCalIsoTrkFilter) | |||
pathALCARECOHcalCalNoise = cms.Path(seqALCARECOHcalCalNoise) | |||
pathALCARECOHcalCalIterativePhiSym = cms.Path(seqALCARECOHcalCalIterativePhiSym*ALCARECOHcalCalPhisymDQM) | |||
pathALCARECOHcalCalIsolatedBunchFilter = cms.Path(seqALCARECOHcalCalIsolatedBunchFilter) |
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.
@lpernie this one as well!
thanks! should be in a testable shape now |
@cmsbuild please test |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Hi @lpernie, @mmusich, @franzoni, I have run an additional check regarding the change of the ALCARECO troughput at commit c03b999: I modified workflow 1000, to take SingleMuon and DoubleMuon datasets as input and compared the file sizes of the produced output of the Used input events: 500 Selected events (before #15221):
Selected events (after #15221):
Event size (before #15221):
Event size (after #15221):
relative throughput change = (file_size(after) - file_size(before))/file_size(before)
Hope this helps to judge this PR in terms of ALCARECO throughput. -Gregor |
To be more specific: I used the following datasets: |
+1 thanks @ghellwig for the study |
@lpernie in view of a possible reprocessing of 2016 data can you please backport to 80x as well? |
Sure. |
Indeed. Thanks! |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
+1 |
steps['RECOCOS']=merge([{'-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlCalIsolatedMu,DQM','--scenario':'cosmics'},stCond,step3Defaults]) | ||
steps['RECOHAL']=merge([{'-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlCalIsolatedMu,DQM','--scenario':'cosmics'},step3Up2015Hal]) | ||
steps['RECOCOS']=merge([{'-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlGlobalCosmics,DQM','--scenario':'cosmics'},stCond,step3Defaults]) | ||
steps['RECOHAL']=merge([{'-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlBeamHalo+MuAlBeamHaloOverlaps,DQM','--scenario':'cosmics'},step3Up2015Hal]) | ||
steps['RECOCOS_UP15']=merge([{'--conditions':'auto:run2_mc_cosmics','-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlCalIsolatedMu,DQM','--scenario':'cosmics'},step3Up2015Hal]) |
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.
@lpernie this line here shall be changed as done above:
https://github.com/cms-sw/cmssw/pull/15221/files#diff-819af2ec677272fddf1fef50e788a88bR1195"
this currently breaks wf 1307.0 @MengqingWu
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.
@mmusich Do you mean like RECOHAL?
steps['RECOCOS']=merge([{'-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlBeamHalo+MuAlBeamHaloOverlaps,DQM','--scenario':'cosmics'},stCond,step3Defaults])
Or like it was in the past (ALCA:MuAlCalIsolatedMu)?
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.
@lpernie no I mean to change:
steps['RECOCOS_UP15']=merge([{'--conditions':'auto:run2_mc_cosmics','-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlCalIsolatedMu,DQM','--scenario':'cosmics'},step3Up2015Hal])
to:
steps['RECOCOS_UP15']=merge([{'--conditions':'auto:run2_mc_cosmics','-s':'RAW2DIGI,L1Reco,RECO,ALCA:MuAlGlobalCosmics,DQM','--scenario':'cosmics'},step3Up2015Hal])
Hi @mmusich,
This the the new PR on the addition of general tracks to the ALCARECO stream for muon alignment you requested.