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-gex43 Remove double declaration of the same constant #32407
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32407/20275
|
A new Pull Request was created by @bsunanda (Sunanda Banerjee) for master. It involves the following packages: Geometry/CMSCommonData @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
+1 |
+1 |
+1 |
@bsunanda - It seems like a significant change. Are you sure that increasing the thickness by 0.5 mm corresponds to the engineering drawing and does not introduce new overlaps? |
Comparison results are now available Comparison Summary:
|
+upgrade |
Pull request #32407 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @kpedro88 can you please check and sign again. |
@cmsbuild Please test |
unhold |
+1 |
Comparison results are now available Comparison Summary:
|
+1 |
+1 |
Thanks @bsunanda! Just wanted to confirm, because, if there are two constants defined, one would need to check which one is taken into consideration: the first or the latter. If it's the first, removing it would change the constant value. <Constant name="BeampipeThickness4" value="2.0*mm"/>
<Constant name="BeampipeThickness4" value="2.5*mm"/> |
+upgrade |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Remove double declaration of the same constant
PR validation:
Use cfg's in some test areas
if this PR is a backport please specify the original PR and why you need to backport that PR:
Nothing special