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

Phase2-gex11 Add a scenario D66 and workflow 30634 with 16 strip GE21 #31451

Merged
merged 2 commits into from Sep 18, 2020

Conversation

bsunanda
Copy link
Contributor

PR description:

Add a scenario D66 and workflow 30634 with 16 strip GE21

PR validation:

Test using runTheMatrix using the workflow 30634.0

if this PR is a backport please specify the original PR and why you need to backport that PR:

Nothing special

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@bsunanda
Copy link
Contributor Author

@slomeo @watson-ij Just made a workflow still using ME0 for 16 strip GE21. Once this is accepted will make the one when GE0 replaces ME0

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-31451/18333

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @bsunanda for master.

It involves the following packages:

Configuration/Geometry
Configuration/PyReleaseValidation
Configuration/StandardSequences
Geometry/CMSCommonData

@civanch, @Dr15Jones, @jordan-martins, @chayanit, @cvuosalo, @wajidalikhan, @ianna, @mdhildreth, @cmsbuild, @makortel, @franzoni, @silviodonato, @kpedro88, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks.
@fabiocos, @vargasa, @makortel, @felicepantaleo, @GiacomoSguazzoni, @rovere, @VinInn, @Martin-Grunewald, @lecriste, @mtosi, @dgulhan, @slomeo this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 13, 2020

The tests are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

+1
Tested at: d70c4f6
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05f346/9294/summary.html
CMSSW: CMSSW_11_2_X_2020-09-12-1100
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-05f346/9294/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2620306
  • DQMHistoTests: Total failures: 1
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2620283
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 34 files compared)
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@@ -88,5 +88,6 @@ Several detector combinations have been generated:
* D63 = T21+C11+M4+I11+O5+F4
* D64 = T22+C11+M4+I11+O5+F4
* D65 = T23+C11+M4+I11+O5+F4
* D66 = T17+C11+M8+I11+O5+F4
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bsunanda T17 is soon to be decommissioned (next week). I would suggest to use T21 as new baseline instead of T17. @emiglior FYI

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed T17 to T21

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mmusich while I agree for new scenarios it's better to use a more modern tracker, what is the intention for the 6 scenarios currently using T17 when it is "decommissioned"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose they should all be migrated to T21. @emiglior is preparing a PR about that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless of course some other subsystem explicitly wants to keep T17 around.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's move to #30512

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 18, 2020

The tests are being triggered in jenkins.
Tested with other pull request(s) #31507
Test Parameters:

@cmsbuild
Copy link
Contributor

+1
Tested at: e8ea499
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1c7c86/9429/summary.html
CMSSW: CMSSW_11_2_X_2020-09-18-1100
SCRAM_ARCH: slc7_amd64_gcc820

@cmsbuild
Copy link
Contributor

Comparison job queued.

@kpedro88
Copy link
Contributor

+upgrade

@dildick
Copy link
Contributor

dildick commented Sep 18, 2020

Looks good. GEM warnings are gone. HGCal remain. From step2_TTbar_14TeV+2026D66+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal.log

18-Sep-2020 17:49:44 CEST  Initiating request to open file file:step1.root
18-Sep-2020 17:49:45 CEST  Successfully opened file file:step1.root
create data set info Default
create data set info Default
create data set info Default
create data set info Default
Begin processing the 1st record. Run 1, Event 1, LumiSection 1 on stream 0 at 18-Sep-2020 17:50:57.424 CEST
%MSG-w HGCalTriggerGeometry:  HGCalVFEProducer:hgcalVFEProducer  18-Sep-2020 17:51:08 CEST Run: 1 Event: 1
Found missing wafer (layer=35 u=1 v=1) in trigger modules mapping
%MSG
...
%MSG-w HGCalTriggerGeometry:  HGCalVFEProducer:hgcalVFEProducer  18-Sep-2020 17:52:43 CEST Run: 1 Event: 10
Found missing wafer (layer=35 u=3 v=-10) in trigger modules mapping
%MSG
18-Sep-2020 17:52:46 CEST  Closed file file:step1.root

=============================================

MessageLogger Summary

@kpedro88
Copy link
Contributor

Yes, I noticed the HGCal warnings earlier today and opened #31506. Those are unrelated to this PR.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1c7c86/9429/summary.html

@slava77 comparisons for the following workflows were not done due to missing matrix map:

  • /data/cmsbld/jenkins/workspace/compare-root-files-short-matrix/data/PR-1c7c86/30634.0_TTbar_14TeV+2026D66+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 4 differences found in the comparisons
  • DQMHistoTests: Total files compared: 35
  • DQMHistoTests: Total histograms compared: 2540471
  • DQMHistoTests: Total failures: 7
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2540442
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 34 files compared)
  • Checked 149 log files, 22 edm output root files, 35 DQM output files

@bsunanda
Copy link
Contributor Author

@silviodonato Could you merge this PR?

@silviodonato
Copy link
Contributor

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will be automatically merged.

@cmsbuild cmsbuild merged commit b16771b into cms-sw:master Sep 18, 2020
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

9 participants