Add tracking hit-finding efficiency from HitPattern #11290
Conversation
Hit Efficiency for all Tracker components are (naively) derived starting from the Hit Pattern that is associated to each reconstructed track. The efficiency is computed using the standard DQMGenericClient, using as numerator the number of valid hits for each tracker component, and as denominator the sum of valid and missing hits. All categories of missing hits are considered. Hits flagged as inactive or bad are not taken into account, but anyway recorded in other histograms, in case we want to monitor also their efficiencies. The efficiencies are computed wrt the number of good vertices found in each event. The selection of "good vertex" is the recommended one: ndof>=4 and isFake is False. Only events with at least one good vertex are monitored. The code is active by default in Tier-0 processing and, in general, everytime standard DQM Tracking is active. Both generalTracks and highPurityTracks/pt_1 are monitored separately. The Tracker Geometry has been used as much as possible to make the code Upgrade friendly.
|
A new Pull Request was created by @rovere (Marco Rovere) for CMSSW_7_6_X. Add tracking hit-finding efficiency from HitPattern It involves the following packages: DQM/TrackingMonitor @cmsbuild, @danduggan, @deguio can you please review it and eventually sign? Thanks. |
|
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: |
|
+1 |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_6_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
cmsbuild
added
dqm-approved
fully-signed
and removed
dqm-pending
pending-signatures
labels
|
+1 |
Add tracking hit-finding efficiency from HitPattern
Hit Efficiency for all Tracker components are (naively) derived starting
from the Hit Pattern that is associated to each reconstructed track. The
efficiency is computed using the standard DQMGenericClient, using as
numerator the number of valid hits for each tracker component, and as
denominator the sum of valid and missing hits. All categories of missing
hits are considered. Hits flagged as inactive or bad are not taken into
account, but anyway recorded in other histograms, in case we want to
monitor also their efficiencies. The efficiencies are computed wrt the
number of good vertices found in each event. The selection of "good
vertex" is the recommended one: ndof>=4 and isFake is False. Only events
with at least one good vertex are monitored. The code is active by
default in Tier-0 processing and, in general, everytime standard DQM
Tracking is active. Both generalTracks and highPurityTracks/pt_1 are
monitored separately. The Tracker Geometry has been used as much as
possible to make the code Upgrade friendly.