Documentation of Appmodule QaBetaTools/QaTrack
$Id: QaTrack.html,v 1.3 1998/05/31 00:59:38 dyaeb Exp $
Benchmark
- The standard QA run is 041617 (B0 -> K+ pi-) but it should also work well on generic BaBar data.
Input
- two BtaCandidate lists from the event, "trackCandidates" and "truthCandidates"
- the defaults for the parameters are set to "ChargedTracks" and "MCTruth" respectively.
Method
- accumulate an ntuple of measured and generated helix parameters and momentum components along with the fitted helix parameter errors.
- truth is judged according to the "Default" BtaMcAssoc list
- using a .kumac, derive pull plots
Output
- QaTrack_plot1_RELEASE_041617.ps (helix parameters) and QaTrack_plot2_RELEASE_041617.ps (px, py, pz)
- Means and widths of pulls from Paw fits shown on the above plots
Detailed Information
The module produces an Ntuple which can be analysed by Qatrack.kumac
Since the Ntuple Id depends on the modules involved in the execution, you need to specify the ID of the Ntuple when you execute the KUMAC file.
exec Qatrack#check1 [NTUPLE_ID] shows pull plots for the track parameters.
exec Qatrack#check2 [NTUPLE_ID] shows the momentum pull for the tracks.
Maintained by Mehdi Benkebil.
Please send corrections, additions and (polite) suggestions to:
benkebil@SLAC.Stanford.Edu
|
