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-hgx348D Update HGCSiliconDetId in view of adding a fourth type of wafer: high density but thicker (backport of #43196) #43207

Merged
merged 1 commit into from
Nov 13, 2023

Conversation

bsunanda
Copy link
Contributor

@bsunanda bsunanda commented Nov 6, 2023

PR description:

Update HGCSiliconDetId in view of adding a fourth type of wafer: high density but thicker (backport of #43196)

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. If this PR will be backported please specify to which release cycle the backport is meant for:

Backport of #43196

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2023

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

It involves the following packages:

  • DataFormats/ForwardDetId (simulation, upgrade)
  • Geometry/HGCalCommonData (geometry, upgrade)
  • Geometry/HGCalGeometry (geometry, upgrade)

@civanch, @cmsbuild, @makortel, @Dr15Jones, @bsunanda, @AdrianoDee, @mdhildreth, @srimanob can you please review it and eventually sign? Thanks.
@youyingli, @rovere, @missirol, @fabiocos, @apsallid this is something you requested to watch as well.
@sextonkennedy, @antoniovilela, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@bsunanda
Copy link
Contributor Author

bsunanda commented Nov 6, 2023

@cmsbuild Please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Nov 6, 2023

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-639d37/35645/summary.html
COMMIT: cb09616
CMSSW: CMSSW_13_3_X_2023-11-06-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/43207/35645/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 96 lines to the logs
  • Reco comparison results: 7 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3363010
  • DQMHistoTests: Total failures: 10
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3362978
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 49 files compared)
  • Checked 214 log files, 167 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@civanch
Copy link
Contributor

civanch commented Nov 7, 2023

+1

@bsunanda
Copy link
Contributor Author

@srimanob Please approve this backport PR

@srimanob
Copy link
Contributor

Could you please clarify the reason of backport? From #43196 (comment), it seems nothing is used. Thx.

@bsunanda
Copy link
Contributor Author

@srimanob This was initially put for 13_3_X. Then due to a delay in signing this PR, the 14_0_X started and Shahzad transferred all unmerged PRs to 14_0_X and asked to request for back porting them to 13_3_X.

@srimanob
Copy link
Contributor

Hi @bsunanda @civanch
I don't think I get answer from above comment, sorry.

My question is that why do you need to merge this PR in 13_3. This PR, alone, will not do anything, if I understand correctly. Do you plan to do more backports for future PR?

  • If yes, could you please share the plan.
  • If no, I assume we don't need the backport.
    In the current plan, 13_3 will not be used for any Phase-2 production. 14_0 or 14_1 (if by April/May) will be the release for the next Phase-2 production.

Thanks for clarification.

@bsunanda
Copy link
Contributor Author

We plan to complete V18 in 14_0_X and backport this to 13_3_X. It is one essential part of that

@srimanob
Copy link
Contributor

I think that is a point I don't understand. Why do we need V18 to be backport? What is the reason behind that.

@srimanob
Copy link
Contributor

+Upgrade

I sign this PR as it is OK to have. However, we should have a clear reason to backport new geometry to unused release, this is the point that I don't understand. See above comment.

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_13_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@rappoccio
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit e0d6139 into cms-sw:CMSSW_13_3_X Nov 13, 2023
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.

5 participants