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
Added SiStrip Report maps for each error flag separately #16521
Conversation
thanks @lmoreels , when you are ready with the 81X PR, please report the PR number here |
A new Pull Request was created by @lmoreels for CMSSW_8_0_X. It involves the following packages: DQM/SiStripMonitorClient @cmsbuild, @dmitrijus, @vanbesien, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
PR for 81X: #16529 |
@dmitrijus could you please start the tests? thanks. |
+1 |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @smuzaffar |
Comparison job queued. |
Is there a particular reason that this PR is not merged while the 81X one is? Please let me know if there is anything I need to do |
+1 |
The current SiStrip Report Summary indicates the good detector fraction when taking into account a number error flags. If the good detector fraction is not 100%, it is not directly clear which error caused this. The additional Report maps take into account one error flag only, such that in case of problems, the origin can be quickly identified.
A PR for 81X is being prepared.