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
Pixel Stuck TBM simulation: check conditions in digitizer initialization #25700
Conversation
…o present in SiPixelStatusScenariosRcd and throw if not
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25700/8076
Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25700/8076/git-diff.patch You can run |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25700/8078
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages: SimTracker/SiPixelDigitizer @cmsbuild, @civanch, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready @slava77 comparisons for the following workflows were not done due to missing matrix map:
Comparison Summary:
|
@civanch can you please check and eventually sign? This would be needed to have a working set of "stuck TBM" simulation relvals in IB (currently there are broken, see PR description) |
+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) |
code-checks |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-25700/8139
|
+1 |
As pointed out in #25524 (comment), the conditions used for the stuck-TBM simulation tests (wf: 10824.7,10842.7) are inconsistent as there are some non-zero probabilities (in
SiPixelStatusScenarioProbabilityRcd
) assigned to certain scenarios which are not included in the scenario DB object (SiPixelStatusScenariosRcd
).The new payload proposed in eb2c2ec fixes this, while commit 986a13d takes care of throwing in case of an inconsistent sets of conditions at the pixel digitizer initialization instead that starting the job and eventually failing later randomly.
Tested in CMSSW_10_5_X_2019-01-17-1100 (architecture:
slc7_amd64_gcc700
) via:(as in the failing tests: link )