Skip to content

Conversation

@cvuosalo
Copy link
Contributor

@cvuosalo cvuosalo commented Nov 17, 2021

The file Geometry/VeryForwardData/data/CTPPS_Pixel_2021/Modules/v2/ppstrackerMaterials.xml contains PPS materials that are not used anywhere, as far as I can tell. Some of the composite materials are defined in the wrong order, which could cause problems in the future. It is planned to require that all components of a composite material be defined before the material itself is defined, but we can't make that change as long as there are existing composite materials defined in the wrong order. The PPS materials in this file are the only materials in the Run 3 geometry that are defined in the wrong order. Since they are not even used, it is fairly simple to just remove them.

Another unused material PPS_Epoxy is deleted from the RP_Materials.xml file in this PR.

After this PR, a new big XML file should be created and uploaded to the DB, but that should probably wait until 12_3.

PR validation:

The DD4hep XML workflow, 11634.911, was run successfully with this PR.

No backport is needed.

@@ -0,0 +1,126 @@
<?xml version="1.0"?>
Copy link
Contributor Author

@cvuosalo cvuosalo Nov 17, 2021

Choose a reason for hiding this comment

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

The only changes in this new version is the removal of the ppstrackerMaterials.xml file and composite material PPS_Epoxy.

@@ -1,7 +1,7 @@
import FWCore.ParameterSet.Config as cms
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't quite understand why this Python config is in a versioned directory. I'm not sure if a new v5 directory is required for this new version of the file. Since the change is so minor, maybe no new version directory is needed.

Copy link
Contributor

Choose a reason for hiding this comment

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

Indeed, I tend to agree that we could keep v4 in this particular case, since this is a matter of removing a spurious line.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @diemort
I think it is a matter of organizing the code. In the same as v2 which is defined as a bug fix, I think we should have v5, instead of edit inside v4. And maybe we just use geometryRPFromDD_2021_cfi.py (outside vN) directly, not just a link to vN.geometryRPFromDD_2021_cfi

Copy link
Contributor

Choose a reason for hiding this comment

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

@srimanob, using geometryRPFromDD_2021_cfi.py outside vN is more prone to errors in case someone forgets to apply the changes that were made in the latest vN and we avoid duplicating files. I'll submit another PR because other non-dd4hep files have to be updated with v5.

Copy link
Contributor

Choose a reason for hiding this comment

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

@diemort , will the PR that you are announcing here imply a creation of a Geometry/VeryForwardGeometry/python/dd4hep/v5 area, which will contain a link to a (possibly modified)
Geometry/VeryForwardGeometry/data/dd4hep/v5/geometryRPFromDD_2021.xml?

If so, do you plan to revert Geometry/VeryForwardGeometry/python/dd4hep/v4/geometryRPFromDD_2021_cfi.py to point to Geometry/VeryForwardGeometry/data/dd4hep/v4/geometryRPFromDD_2021.xml?

In that case, it looks to me cleaner and less error prone to introduce a Geometry/VeryForwardGeometry/python/dd4hep/v5 area since now, and modifying it afterwards, so that v4 will remain unchanged by construction.

At the contrary, if you plan to create a brand new Geometry/VeryForwardGeometry/data/dd4hep/v6/geometryRPFromDD_2021.xml, you can link it from the new Geometry/VeryForwardGeometry/python/dd4hep/v5 area (and Geometry/VeryForwardGeometry/python/dd4hep/v4 will link the fixed Geometry/VeryForwardGeometry/data/dd4hep/v5/geometryRPFromDD_2021.xml, as it is now). In this second case we can merge this PR as it is coded now: just let us know.

Copy link
Contributor

Choose a reason for hiding this comment

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

@perrotta I partially agreed with @srimanob that we should follow the convention and make the changes into a v5, keeping v4 untouched. So I agree with your cleaner suggestion and introduce v5 now. OTOH, I'd still keep the link outside the vN folder pointing to v5, which is the latest geometry description.

Besides, my next PR will update the entry for v5/RP_Materials.xml in Geometry/VeryForwardGeometry/python/v3/geometryRPFromDD_202*.xml (new v3) and update the links at Geometry/VeryForwardGeometry/python/geometryRPFromDD_202*.xml

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@diemort I was planning to include your changes in this PR, but if you want to submit a separate PR, that would be fine. I may not be able to make the changes until Monday. I was figuring that there is still time for changes since this PR should wait until it can go into 12_3.

Copy link
Contributor

Choose a reason for hiding this comment

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

@cvuosalo no problem, I can make a separate PR as soon as this one is merged.

@cvuosalo
Copy link
Contributor Author

@fabferro Please check whether this removal of references to the ppstrackerMaterials.xml file is OK.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36163/26714

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @cvuosalo (Carl Vuosalo) for master.

It involves the following packages:

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

@civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob can you please review it and eventually sign? Thanks.
@missirol, @fabferro, @jan-kaspar, @kpedro88, @Martin-Grunewald, @bsunanda, @vargasa, @fabiocos, @slomeo 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

@fabferro
Copy link
Contributor

@diemort please have a look

@diemort
Copy link
Contributor

diemort commented Nov 18, 2021

@fabferro @cvuosalo dropping ppstrackerMaterials.xml is OK from my side.

@cvuosalo
Copy link
Contributor Author

There's another unused material whose removal I will be adding to this PR.

@@ -0,0 +1,68 @@
<?xml version="1.0"?>
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 only change for this file is the deletion of unused composite material PPS_Epoxy.

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36163/26735

@cmsbuild
Copy link
Contributor

Pull request #36163 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob can you please check and sign again.

@cvuosalo
Copy link
Contributor Author

@cmsbuild please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0a12ff/20619/summary.html
COMMIT: 2b92f71
CMSSW: CMSSW_12_2_X_2021-11-18-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/36163/20619/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: 8 differences found in the comparisons
  • DQMHistoTests: Total files compared: 42
  • DQMHistoTests: Total histograms compared: 3327156
  • DQMHistoTests: Total failures: 11
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3327122
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.004 KiB( 41 files compared)
  • DQMHistoSizes: changed ( 312.0 ): -0.004 KiB MessageLogger/Warnings
  • Checked 177 log files, 37 edm output root files, 42 DQM output files
  • TriggerResults: no differences found

@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)

@perrotta
Copy link
Contributor

@cvuosalo if the merging of this (rather technical) PR has to wait for 12_3, then better to put it on hold till next week, and perhaps also write somehow "12_3_X" in the title, so that it is crystal clear

@cvuosalo
Copy link
Contributor Author

@perrotta This PR makes a minor, technical change to the geometry, but it does change the geometry nonetheless. For consistency, the DD4hep geometry in the DB should also be changed to match, which would mean uploading a new big XML file to the DB and creating a new Global Tag. I was thinking all these steps should wait for 12_3.

If you want to merge this PR into 12_2, I suppose that would be OK, though it would introduce a trivial inconsistency between the DD4hep XML and DB geometry in 12_2 that would be rectified in 12_3.

@cvuosalo
Copy link
Contributor Author

hold

@cmsbuild
Copy link
Contributor

Pull request has been put on hold by @cvuosalo
They need to issue an unhold command to remove the hold state or L1 can unhold it for all

@cvuosalo
Copy link
Contributor Author

I'm going to include the geometryRPFromDD_2021_cfi.py changes in this PR in the next few hours and then it can be merged.

updating DD files with v5 after removing PPS materials. First step. Will require more revision
@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36163/27032

  • This PR adds an extra 44KB to repository

@cmsbuild
Copy link
Contributor

Pull request #36163 was updated. @civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob can you please check and sign again.

@cvuosalo
Copy link
Contributor Author

Closing in favor of #36307.

@cvuosalo cvuosalo closed this Nov 30, 2021
cmsbuild added a commit that referenced this pull request Dec 1, 2021
[DD4hep] Remove unused PPS materials from Run 3 2021 (replaces #36163)
@cvuosalo
Copy link
Contributor Author

-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.

7 participants