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

Run3-gex90 Make unique material names as default for all Run3 scenarios #34983

Merged
merged 2 commits into from Aug 25, 2021

Conversation

bsunanda
Copy link
Contributor

PR description:

Make unique material names as default for all Run3 scenarios

PR validation:

Use the runTheMatrix test workflows

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

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34983/24825

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master.

It involves the following packages:

  • Configuration/Geometry (geometry, upgrade)
  • Geometry/CMSCommonData (geometry, upgrade)

@civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @kpedro88, @cmsbuild, @AdrianoDee, @srimanob, @mdhildreth can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @fabiocos, @slomeo, @vargasa this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@bsunanda bsunanda changed the title RUn3-gex90 Make unique material names as default for all Run3 scenarios Run3-gex90 Make unique material names as default for all Run3 scenarios Aug 23, 2021
@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fa06a7/17971/summary.html
COMMIT: 78e336b
CMSSW: CMSSW_12_1_X_2021-08-23-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/34983/17971/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 39
  • DQMHistoTests: Total histograms compared: 3000352
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3000330
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 38 files compared)
  • Checked 165 log files, 37 edm output root files, 39 DQM output files
  • TriggerResults: no differences found

@cvuosalo
Copy link
Contributor

@bsunanda Could you change an additional line in Configuration/Geometry/python/dict2021Geometry.py? As in my PR #34974, change:
''Geometry/TrackerCommonData/data/PhaseI/v2/pixbarmaterial.xml', to'Geometry/TrackerCommonData/data/PhaseI/v3/pixbarmaterial.xml', `
for "T3".
Then I can remove this change from #34974.
After that, we merge #34974 first, followed by this PR.

@bsunanda
Copy link
Contributor Author

bsunanda commented Aug 23, 2021 via email

@bsunanda
Copy link
Contributor Author

@cvuosalo Can I also take the v3/pixbarmaterial.xml. Without that the PR won't be complete

@bsunanda
Copy link
Contributor Author

@cvuosalo So you need to remove the changes in dict2021geometry.py and remove the addition to pixbarmaterial.xml

@bsunanda
Copy link
Contributor Author

@cvuosalo Please confirm

@bsunanda
Copy link
Contributor Author

@cvuosalo Or I can take your advice that let your PR get merged and then I can get this PR tested

@civanch
Copy link
Contributor

civanch commented Aug 23, 2021

@bsunanda , @cvuosalo, I think that #34974 should be merged first, at least, this would be an ideal sequence.

@bsunanda
Copy link
Contributor Author

bsunanda commented Aug 23, 2021 via email

@civanch
Copy link
Contributor

civanch commented Aug 24, 2021

urgent

@bsunanda
Copy link
Contributor Author

@cmsbuild Please test

@bsunanda
Copy link
Contributor Author

@civanch @perrotta @qliphy I tested against the latest IB and I think it is OK

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-fa06a7/18001/summary.html
COMMIT: 28b3036
CMSSW: CMSSW_12_1_X_2021-08-24-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/34983/18001/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 39
  • DQMHistoTests: Total histograms compared: 3000352
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3000330
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 38 files compared)
  • Checked 165 log files, 37 edm output root files, 39 DQM output files
  • TriggerResults: no differences found

@civanch
Copy link
Contributor

civanch commented Aug 24, 2021

+1

@civanch
Copy link
Contributor

civanch commented Aug 24, 2021

@perrotta, @qliphy tests are fine, would it possible to merge it without upgrade sign - @srimanob is aware about this PR but he may have problem to access these days.

@srimanob
Copy link
Contributor

+Upgrade

@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 now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@qliphy
Copy link
Contributor

qliphy commented Aug 25, 2021

+1

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

6 participants