-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Adding geometry scenarios D59 and D60 implementing ETL version 4 and 5 #30340
Conversation
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30340/16351
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30340/16355
|
-1 Tested at: 0e905af CMSSW: CMSSW_11_2_X_2020-06-24-2300 I found follow errors while testing this PR Failed tests: UnitTests RelVals
I found errors in the following unit tests: ---> test GeometryMTDGeometryBuilderTestDriver had ERRORS
When I ran the RelVals I found an error in the following workflows: runTheMatrix-results/23234.1001_TTbar_14TeV+RecoFullGlobal_TestOldDigi_2026D49+HARVESTFullGlobal_2026D49/step1_TTbar_14TeV+RecoFullGlobal_TestOldDigi_2026D49+HARVESTFullGlobal_2026D49.log20034.0 step3 runTheMatrix-results/20034.0_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D35_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D35+RecoFullGlobal_2026D35+HARVESTFullGlobal_2026D35/step3_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D35_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D35+RecoFullGlobal_2026D35+HARVESTFullGlobal_2026D35.log20434.0 step3 runTheMatrix-results/20434.0_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D41_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D41+RecoFullGlobal_2026D41+HARVESTFullGlobal_2026D41/step3_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D41_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D41+RecoFullGlobal_2026D41+HARVESTFullGlobal_2026D41.log23234.0 step3 runTheMatrix-results/23234.0_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D49_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D49+RecoFullGlobal_2026D49+HARVESTFullGlobal_2026D49/step3_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D49_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D49+RecoFullGlobal_2026D49+HARVESTFullGlobal_2026D49.log21234.0 step3 runTheMatrix-results/21234.0_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D44_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D44+RecoFullGlobal_2026D44+HARVESTFullGlobal_2026D44/step3_TTbar_14TeV+TTbar_14TeV_TuneCP5_2026D44_GenSimHLBeamSpotFull14+DigiFullTrigger_2026D44+RecoFullGlobal_2026D44+HARVESTFullGlobal_2026D44.log |
Comparison not run due to runTheMatrix errors (RelVals and Igprof tests were also skipped) |
The code-checks are being triggered in jenkins. |
@icosivi does the latest commit address the test failure? if not, please make an explicit comment when the PR is expected to work. (As always, please test the PR locally first.) |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30340/16534
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
@kpedro88 not yet, I will make an explicit comment when it will be expected to work, thanks |
@kpedro88 in my understanding from @icosivi this PR was locally tested with the standalone geometry checks, and no obvious issue was found. The failure of the unit test in itself is totally trivial, as ETL DetIds change a new reference needs to be used. What is clearly unexpected is the failure in the old relvals, which is of course something that needs to be verified to work. The test of reading old files with new code and verify that the translation was properly done was done (@icosivi please confirm). But apparently there is some unexpected issue in the chain. The Geant4 step looks ok from the tests I have suggested, while a closer check to DIGIs is needed, and the update of the dumper I asked @icosivi is meant for this. I believe this PR could be put at least on hold. But probably we could have a different strategy: split it into a PR to update ETLDetId, once all checks are completed and problems identified and solved, and another one with the remaining update of new scenarios, that looks less prone to create issues. |
@fabiocos I confirm that the test of reading old files with new code was done |
hold this may be eventually split into a PR for ETLDetId, and another one with the new scenarios (updated for the new work by @bsunanda ) |
<version ClassVersion="3" checksum="1644731879"/> | ||
<ioread sourceClass = "ETLDetId" version="[-4]" targetClass="ETLDetId" source="" target=""> |
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.
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.
while it looks ok reading data from previous versions...
PR description:
This PR implements geometry scenarios D59 and D60:
ETL version 4 was already implemented in scenario D53 (https://indico.cern.ch/event/868736/contributions/3709315/attachments/1978993/3295064/MTDdays_20200131.pdf) and fits in the new Endcap Calorimeter envelope defined in D58.
ETL version 5 implements the latest version of ETL disks, as proposed by N. Koss (https://indico.cern.ch/event/868736/contributions/3706894/attachments/1978848/3294508/20200130_ETL_mechanics_timing_days.pdf).
ETL v5 introduces D-shaped sectors, instead of the quarters used in ETL v4, comprising more than 512 modules, which is the maximum number of modules that could be accommodated using the allocated bits in ETLDetId. Therefore ETLDetId.h has been modified to fix this issue, by adding 2 bits. The new ETLDetId is backward compatible with the older versions, thanks to a dedicated compatibility code implemented in ETLDetId.cc.
Both ETL versions and the backward compatibility issue were presented at the last MTD DPG meeting (https://indico.cern.ch/event/919571/contributions/3864046/attachments/2039610/3415525/MTD_DPG_20200515.pdf )
PR validation: