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
Introduce Run3 (post-LS2) workflow #19889
Conversation
A new Pull Request was created by @kpedro88 (Kevin Pedro) for master. It involves the following packages: Configuration/Eras @civanch, @Dr15Jones, @vazzolini, @dmitrijus, @kmaeshima, @ianna, @kpedro88, @fabozzi, @cmsbuild, @kkousour, @franzoni, @mdhildreth, @GurpreetSinghChahal, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 03417eb The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: You can see the results of the tests here: I found follow errors while testing this PR Failed tests: RelVals
When I ran the RelVals I found an error in the following worklfows: runTheMatrix-results/11624.0_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2019_GenSimFull+DigiFull_2019+RecoFull_2019+ALCAFull_2019+HARVESTFull_2019/step3_TTbar_13+TTbar_13TeV_TuneCUETP8M1_2019_GenSimFull+DigiFull_2019+RecoFull_2019+ALCAFull_2019+HARVESTFull_2019.log
There was error running material budget tests. The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
relval failure was expected, seems to be due to pixel Phase 1 DQM changes (ongoing investigation, discussion in #19811) |
(NB: this ran fine in |
+1 |
+1 |
+1 |
+1 |
@fabozzi please sign |
@fabozzi ping |
+1 |
from Configuration.Eras.Modifier_phase2_common_cff import phase2_common | ||
phase2_common.toReplaceWith(localreco, _phase2_localreco) | ||
phase2_common.toReplaceWith(localreco_HcalNZS, _phase2_localreco_HcalNZS) | ||
_run3_localreco = localreco.copyAndExclude([castorreco]) |
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.
Hi @kpedro88 - was this choice based on some discussion?
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.
The post-LS2 beampipe requires CASTOR to be removed.
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.
@hvanhaev
please confirm that there will be no running with castor after LS2.
Thank you.
@@ -0,0 +1,70 @@ | |||
<?xml version="1.0"?> |
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.
what is the idea behind copying this file? Does it reflect a detector change?
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.
L37 is different to reflect the addition of GEMS:
<PartSelector path="//GE.*"/>
merge |
It appears this pull request added workflow 11626 to the nightly IB and that workflow is failing: the exception being thrown is some variation of a request out of bounds
|
@Dr15Jones ah, the short matrix only runs 11624... I'll investigate |
@Dr15Jones see #20104 |
Dear Slava,
Indeed, at the moment there are no data taking plans with CASTOR after LS2.
Cheers,
Hans
On 8 Aug 2017, at 17:07, Slava Krutelyov <notifications@github.com<mailto:notifications@github.com>> wrote:
@slava77 commented on this pull request.
________________________________
In Configuration/StandardSequences/python/Reconstruction_cff.py<#19889 (comment)>:
@@ -50,16 +50,16 @@
localreco = cms.Sequence(bunchSpacingProducer+trackerlocalreco+muonlocalreco+calolocalreco+castorreco)
localreco_HcalNZS = cms.Sequence(bunchSpacingProducer+trackerlocalreco+muonlocalreco+calolocalrecoNZS+castorreco)
…-_phase2_localreco = localreco.copyAndExclude([castorreco])
-_phase2_localreco_HcalNZS = localreco_HcalNZS.copyAndExclude([castorreco])
-from Configuration.Eras.Modifier_phase2_common_cff import phase2_common
-phase2_common.toReplaceWith(localreco, _phase2_localreco)
-phase2_common.toReplaceWith(localreco_HcalNZS, _phase2_localreco_HcalNZS)
+_run3_localreco = localreco.copyAndExclude([castorreco])
@hvanhaev<https://github.com/hvanhaev>
please confirm that there will be no running with castor after LS2.
Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#19889 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEgkFyQOqXC6yr8G07z0Pu0wSuNpB6IKks5sWHnJgaJpZM4OhnqF>.
|
This PR introduces a Run3 workflow for the post-LS2 detector (including GE1/1 and HB upgrades, along with Castor removal). The Run2_2018 GT is used for now. Because HCAL conditions don't exist yet for the post-LS2 geometry, the hardcode conditions are used (via the new modifier setup introduced in #19712).
A few modifications are made to the GEM geometry based on phase2 developments (discussed with experts). In addition, I had to fix some logic in a muon DQM analyzer to prevent a crash; with GE1/1 included, we apparently get some muons that fail all the conditions
isGlobalMuon()
,isTrackerMuon()
,isRPCMuon()
,isStandAloneMuon()
. For now, those muons are just skipped. Muon experts may want to improve this handling in the future.attn: @calabria, @bsunanda, @ianna