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
Add impact parameter significance histograms to tracking DQM (74X) #10660
Conversation
A new Pull Request was created by @makortel (Matti Kortelainen) for CMSSW_7_4_X. Add impact parameter significance histograms to tracking DQM (74X) It involves the following packages: DQM/TrackingMonitor @cmsbuild, @danduggan, @deguio can you please review it and eventually sign? Thanks. |
@deguio , @davidlange6 it would be very useful to have this in next prod (patch) release |
ciao @makortel |
please test |
@Degano The original PRs were in 75x :) |
Sorry, that should have been @deguio (being too quick with the tab) |
ups, you are right. it was before the 76x times. |
+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_7_4_X IBs once checked with relvals in the development release cycle of CMSSW or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs once checked with relvals in the development release cycle of CMSSW or unless it breaks tests. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs once checked with relvals in the development release cycle of CMSSW (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
+1 |
Add impact parameter significance histograms to tracking DQM (74X)
Backport of #8410 and #9099:
Add following histograms for impact parameter significances
Add a new flag doSIPPlots to control if they're filled or not. By default it is set to False, and enabled when PCA histograms are.
Tested in 748patch1, expecting only the addition of the "SIP*" histograms.
@VinInn @rovere