-
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
MTD geometry: update tests to scenario D88, update DDFilteredView::parameters() accordingly #36970
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36970/28336
|
A new Pull Request was created by @fabiocos (Fabio Cossutti) for master. It involves the following packages:
@civanch, @Dr15Jones, @makortel, @cvuosalo, @ianna, @mdhildreth, @cmsbuild, @AdrianoDee, @srimanob, @clacaputo, @slava77, @jpata can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test with cms-data/Geometry-TestReference#10 |
Hi @fabiocos |
@srimanob the external is needed just to get the final comparison in the MTD unit tests correct, I run the configuration and use its output as the new reference. For any other purpose the external is useless. After this PR step2 still crashes anyway:
|
Hi @fabiocos |
Page 11-12 of https://indico.cern.ch/event/1127757/contributions/4733494/attachments/2389568/4085879/20220211-Phase2SWPlan.pdf includes the testing of running DD4hep GEN-SIM ⇒ DDD DIGI-HLT ⇒ DD4hep RECO. I will try to turn DT-alignment off and the this fixed MTD to see what is the next :) |
@srimanob merging this PR should be enough, you need the external just when you issue a |
@srimanob in any case the simplest way to test also the external is to redefine |
I've tested this PR in RECO step, we can pass issue of MTD reco geometry construction now. I've updated the doc https://docs.google.com/document/d/1es0C2gH8KVt87iDoPRpdq8VVDjuEKtdd4kPjTsfW_RU/edit?usp=sharing |
+Upgrade This PR can't be tested with DD4hep workflow because we have several issues to run. To test, I've done the local test using The following doc is updated, |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4c0807/22430/summary.html The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Comparison SummarySummary:
|
How should we interpret the test results? Why were additional merge-commits included? |
please test |
@perrotta without the external update included any MTD unit test will fail, but this does not mean it did not work, just that the final output comparison included in it was done with the incorrect (D76) reference |
please test with cms-data/Geometry-TestReference#10 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-4c0807/22462/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+1 |
+reconstruction |
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) |
+1 |
PR description:
This PR addresses the issue #36837 (comment) reported at the simulation meeting https://indico.cern.ch/event/1127757/contributions/4733494/attachments/2389568/4085879/20220211-Phase2SWPlan.pdf slide 12 by @srimanob .
All the MTD standalone geometry tests are moved to the latest D88 scenario, and in order to cope with boolean solids, the
DetectorDescription/DDCMS
package is update in theDDFilteredView::parameters()
method, to accomodate also polycones as possible components of a boolean solid.The unit tests need the appropriate reference cms-data/Geometry-TestReference#10 to correctly run.
PR validation:
MTD geometry unit tests run smoothly and provide the expected geometry dump (as in scenario D77 with only a z shift in ETL sensors position).