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
Remove SiStripDetInfoFileReader as an edm::Service #27292
Remove SiStripDetInfoFileReader as an edm::Service #27292
Conversation
…cDet (to replace some SiStripDetInfoFileReader uses)
…oFileReader to SiStrip DetId list
…of SiStripDetInfoFileReader to SiStrip DetId list
… instead of SiStripDetInfoFileReader
…tead of as an edm::Service
…f DetIds from GeometricDet
…(and simplify, removing inheritance)
…ripDetInfoFileReader
Comparison is ready Comparison Summary:
|
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
As pointed out by @makortel the SiStripDetInfoFileReader service was violating framework policy by providing "physics data" (the list of strip tracker modules, and the number of APVs and strip length for each), so this is an attempt to remove it where it was used in that way.
The same information can be obtained also from the geometry (GeometricDet on the IdealGeometryRecord for the list of DetIds, TrackerGeometry on the TrackerDigiGeometryRecord for the full information), so for the cases where that was available anyway (or could easily be added) I moved to that.
There are a few cases (the SiStripCondObjBuilderFromDb service, and ES producers of with "fake" content - e.g. set with parameters, random - of conditions that do not depend on any of these records). Those I changed to use their own SiStripDetInfoFile instance.
PR validation:
Compiled and ran unittests. Also checked that the configs for standalone use of the GeometricDet/TrackerGeometry work and give the same information, see here.
I did however not run all configs that I edited (many are for standalone tests, production of conditions etc., and several looked quite outdated), so it would be great if the relevant people (Strip online/DAQ, tracker DQM etc.) could have a look at those.