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
Run 2, Run3, and Phase2 tracker: adding T27 (geometry with bricked pixels) and support for storing bricked pixel information #34120
Run 2, Run3, and Phase2 tracker: adding T27 (geometry with bricked pixels) and support for storing bricked pixel information #34120
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34120/23314
|
A new Pull Request was created by @adewit for master. It involves the following packages: Alignment/CommonAlignmentMonitor @chayanit, @wajidalikhan, @ianna, @kpedro88, @tlampen, @pohsun, @civanch, @yuanchao, @silviodonato, @cmsbuild, @davidlange6, @Dr15Jones, @cvuosalo, @mdhildreth, @ggovi, @qliphy, @fabiocos, @francescobrivio, @malbouis, @jordan-martins, @makortel, @srimanob can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
-1 Failed Tests: UnitTests AddOn CMS Clang-Tidy warnings: There are Clang-Tidy warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7f0f25/15948/llvm-analysis/cmsclangtidy.txt for details. Unit TestsI found errors in the following unit tests: ---> test GeometryDOMCount had ERRORS ---> test GeometryTrackerGeometryBuilderTestDriver had ERRORS ---> test testTauEmbeddingProducers had ERRORS AddOn Tests
Expand to see more addon errors ...Comparison SummarySummary:
|
this is spurious and due to issue #34112. |
Thanks - I understand all the rest of them apart from the GeometryDOMCount one, which works locally :/ |
} | ||
|
||
edm::ESTransientHandle<GeometricDet> gd; | ||
es.get<IdealGeometryRecord>().get(gd); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please use esConsumes here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
@@ -4001,6 +4001,7 @@ | |||
applyAlignment = cms.bool( True ), | |||
alignmentsLabel = cms.string( "" ) | |||
) | |||
process.TrackerAdditionalParametersPerDetESModule = cms.ESProducer("TrackerAdditionalParametersPerDetESModule") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@adewit, direct modification of the HLT menu are disallowed as per TSG policy.
Please add a customization function in customizeHLTforCMSSW
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
After investigation I don't think this one is related to this PR; the IB |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7f0f25/17287/summary.html CMS StaticAnalyzer warnings: There are 1 inherits from legacy modules warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-7f0f25/17287/llvm-analysis/legacy-mod-sa.txt for details. Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
For the recording, do you plan to fix the warning, |
@cms-sw/db-l2 Could you please consider and sign if everything is OK from your side? Big thanks. |
+1 |
+operations |
+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 be automatically merged. |
Addressed at #34690 |
PR description:
This adds a phase 2 tracker geometry (T27) containing bricked pixels in TEPX&TFPX, as well as the central 1 (3) rod(s) of TBPX L2 (L3 and 4). Because the information about whether a pixel is "bricked" or not should be available at the level of the geometry, a new record to store this information has also been added, as discussed in these slides. Note that wrt that presentation, the record has been renamed
PTrackerAdditionalParametersPerDetRcd
, and it has been made expandable to make it possible to add further bool/int/float per-detID information for the tracker in the future.For now the record is created from the XML, as no Phase 2 geometries are stored in the DB, but a DB writer is also included for future use.
NOTE: the new record
PTrackerAdditionalParametersPerDetRcd
is consumed by the TrackerGeomBuilderFromGeometricDet, which is the same for Runs 2&3 and Phase 2. Therefore this PR also modifies Runs 2&3, by including the new record, which however only contains the default value (False) for the brickedness boolean, as this parameter of course does not exist before Phase 2The new tracker geometry T27 that uses the bricked pixels is part of detector D85. The workflows for D85 only run up to and including the digitization step to avoid having to include changes in the reconstruction code at this point. NOTE: the modifications to the digitzer that are needed to handle bricked pixels are NOT included in this PR ( @franzglessgen will provide that in due course). In the current state the standard digitizer for planar pixels will be used; this is of course not the final configuration but it does not lead to problems.
@emiglior @mmusich fyi
PR validation:
if this PR is a backport please specify the original PR and why you need to backport that PR:
Not a backport