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
Sensitive detectors update 7 #23625
Sensitive detectors update 7 #23625
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-23625/5258 |
A new Pull Request was created by @civanch (Vladimir Ivantchenko) for master. It involves the following packages: SimG4CMS/Forward @cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+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) |
@civanch I understand that this is the latest code migration you are planning for 10_2_X. Concerning the timing detectors, MtdSD was almost a clone of FastTimerSD, that should be dropped as soon as we get rid of the old scenario. Anyway I fear that many, if not all, of these SD are not really tested in the short matrix (for instance not MTD). Did you check offline the identity of the output? Is this expected? In your communication you were also mentioning an issue with the order in which particles are processed in the timing detectors. Is this addressed as well or not in this PR? |
partly answering myself, in 2018 the geometry includes ZDC, and scenario D21 probed in the matrix touches FastTimerSD |
@fabiocos , I agree with your comment on usage and validation of forward SD. The reason of this clean-up is to reduce code duplication, which make a problem for newcomer and provoke copy/paste of old code and propagation of old patterns from class to class. Forward SD classes , of course, do not affect CPU performance of situation but in this modification minor problems in hits are fixed, namely fastest particle is chosen for a hit, hit position and exit point of a hit is computed and filled correctly. The rest is pure technical - implementation of CMS code rules. This is the last general PR for developments for 10_2. |
+1 |
for timing detectors for Phase2 we may have a closer dedicated check later on, in any case that code is still under potential development |
This is the last PR for clean up of Geant4 sensitive detector classes. Only forward detectors are updated:
Run-1 and run-2 workflows are expected to be unchanged.