Skip to content
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

Merged
merged 6 commits into from Aug 9, 2017
Merged

Conversation

kpedro88
Copy link
Contributor

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

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kpedro88 (Kevin Pedro) for master.

It involves the following packages:

Configuration/Eras
Configuration/Geometry
Configuration/PyReleaseValidation
Configuration/StandardSequences
DQMOffline/Muon
Geometry/CMSCommonData
Geometry/MuonSimData
SimGeneral/MixingModule

@civanch, @Dr15Jones, @vazzolini, @dmitrijus, @kmaeshima, @ianna, @kpedro88, @fabozzi, @cmsbuild, @kkousour, @franzoni, @mdhildreth, @GurpreetSinghChahal, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks.
@ghellwig, @barvic, @bellan, @makortel, @felicepantaleo, @abbiendi, @GiacomoSguazzoni, @jhgoh, @VinInn, @Martin-Grunewald, @calderona, @HuguesBrun, @rovere, @ptcox, @battibass, @ebrondol, @trocino, @dgulhan, @rociovilar this is something you requested to watch as well.
@davidlange6 you are the release manager for this.

cms-bot commands are listed here

@kpedro88
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 24, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/21719/console Started: 2017/07/24 21:17

@cmsbuild
Copy link
Contributor

-1

Tested at: 03417eb

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
a1f0a3b
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-19889/21719/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-19889/21719/git-merge-result

You can see the results of the tests here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-19889/21719/summary.html

I found follow errors while testing this PR

Failed tests: RelVals

  • RelVals:

When I ran the RelVals I found an error in the following worklfows:
11624.0 step3

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

  • Material budget:

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:
a1f0a3b
You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-19889/21719/git-log-recent-commits
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-19889/21719/git-merge-result

@cmsbuild
Copy link
Contributor

Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped)

@kpedro88
Copy link
Contributor Author

relval failure was expected, seems to be due to pixel Phase 1 DQM changes (ongoing investigation, discussion in #19811)
no idea about the material budget failure, the log doesn't indicate anything.

@kpedro88
Copy link
Contributor Author

(NB: this ran fine in CMSSW_9_3_0_pre2)

@kpedro88
Copy link
Contributor Author

kpedro88 commented Aug 1, 2017

+1

@ianna
Copy link
Contributor

ianna commented Aug 1, 2017

+1

@civanch
Copy link
Contributor

civanch commented Aug 1, 2017

+1

@dmitrijus
Copy link
Contributor

+1

@kpedro88
Copy link
Contributor Author

kpedro88 commented Aug 2, 2017

@fabozzi please sign

@kpedro88
Copy link
Contributor Author

kpedro88 commented Aug 4, 2017

@fabozzi ping

@fabozzi
Copy link
Contributor

fabozzi commented Aug 5, 2017

+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])
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor

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"?>
Copy link
Contributor

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?

Copy link
Contributor Author

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.*"/>

@davidlange6
Copy link
Contributor

merge

@cmsbuild cmsbuild merged commit 0dee4e3 into cms-sw:master Aug 9, 2017
@Dr15Jones
Copy link
Contributor

It appears this pull request added workflow 11626 to the nightly IB and that workflow is failing:
https://cmssdt.cern.ch/SDT/cgi-bin/buildlogs/slc7_aarch64_gcc700/CMSSW_9_3_X_2017-08-09-1100/pyRelValMatrixLogs/run/11626.0_QCD_Pt_600_800_13+QCD_Pt_600_800_13TeV_TuneCUETP8M1_2019_GenSimFull+DigiFull_2019+RecoFull_2019+ALCAFull_2019+HARVESTFull_2019/step2_QCD_Pt_600_800_13+QCD_Pt_600_800_13TeV_TuneCUETP8M1_2019_GenSimFull+DigiFull_2019+RecoFull_2019+ALCAFull_2019+HARVESTFull_2019.log

the exception being thrown is some variation of a request out of bounds

----- Begin Fatal Exception 09-Aug-2017 13:34:49 CEST-----------------------
An exception of category 'Out of Range' occurred while
   [0] Processing  Event run: 1 lumi: 1 event: 1 stream: 0
   [1] Running path 'digitisation_step'
   [2] Calling method for module HcalTrigPrimDigiProducer/'simHcalTriggerPrimitiveDigis'
Exception Message:
LUT has 1024 entries for (HcalTrigTower v0: -3,50) but 1596 was requested.
----- End Fatal Exception -------------------------------------------------

@kpedro88
Copy link
Contributor Author

kpedro88 commented Aug 9, 2017

@Dr15Jones ah, the short matrix only runs 11624... I'll investigate

@kpedro88
Copy link
Contributor Author

kpedro88 commented Aug 9, 2017

@Dr15Jones see #20104

@hvanhaev
Copy link
Contributor

hvanhaev commented Aug 21, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants