Add tracking region monitoring to tracking DQM #20378
Conversation
…king regions Region does not have "pT" so that requires using the candidates, so it is more consistent to monitor the eta and phi of the candidates as well. For the tracking region producers that also loop over vertices this probably makes more sense, i.e. the eta and phi of the candidates do not get multiplied by the vertex multiplicity of that event.
|
The code-checks are being triggered in jenkins. |
|
A new Pull Request was created by @makortel (Matti Kortelainen) for master. It involves the following packages: DQM/TrackingMonitor @kmaeshima, @cmsbuild, @vanbesien, @vazzolini, @dmitrijus can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
+code-checks |
|
@cmsbuild, please test |
|
The tests are being triggered in jenkins. |
|
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
|
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 (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
This PR adds simple monitoring of tracking regions to tracking DQM with the following quantities
The monitoring is enabled only for jetCore iteration (the only offline iteration with candidate-seeded regions).
Tested in 9_3_0_pre5, expecting only new histograms and no changes to existing ones.
@rovere @VinInn @mtosi