Mattione Update 04302014

n3pi Cut Study (Shown at Physics Meeting)

• Run 9003 (no EM background), ~5 MegaEvents, searching for γp→π⁺π⁺π^-(n)

• Reconstructed Signal Combos (DCutAction_ThrownTopology, DCutAction_AllTruePID) (% is Signal Remaining)
  • All is 34361 combos (events) of 59562 thrown n3pi in ~5 MegaEvent sample: 57.7% Acceptance
  • +/- 5σ cut on Thrown <---> Detected matching for DCutAction_AllTruePID.

Alternate n3pi Cut Study

• Run 9003 (no EM background), ~5 MegaEvents, searching for γp→π⁺π⁺π^-(n)

• Reconstructed Signal Combos (DCutAction_ThrownTopology, DCutAction_AllTruePID) (% is Signal Remaining)
  • Originally had 34361 combos (events) of 59562 thrown n3pi in ~5 MegaEvent sample: 57.7% Acceptance
  • +/- 5σ cut on Thrown <---> Detected matching for DCutAction_AllTruePID.

• All Reconstructed Combos (% is Skim Size)

π⁺ PID

• 1D Pulls of skim tracks (t_Thrown - t_{Reconstructed})/σ_{t (Reconstructed)}
  • With DCutAction_ThrownTopology, DCutAction_AllTruePID @ +/- 5 σ matching.
  • TBT is time-based tracking.
  • For track time, order of preference is: BCAL, TOF, FCAL, TBT. Histograms only filled when that detector is selected.
    • Large # of FCAL matches: perhaps track/TOF matching too restrictive?
    • Large # of TBT tracks: no detector match
  • Uncertainties used for pull (and PID) calculations are hard-coded.
  • Histograms from DHistogramAction_PID

BCAL

TOF

TBT

FCAL

• 2D Pulls of π⁺'s (t_Thrown - t_{Reconstructed})/σ_{t (Reconstructed)} with no cuts except +/- 5 σ thrown matching.
  • Yellow line at pull = 0.0 just to guide the eye.
  • low-θ tracks being matched to ST & BCAL hits indicates problems with hit-matching criteria.
  • For track time, order of preference is: BCAL, TOF, FCAL, TBT. Histograms only filled when that detector is selected.
  • Histograms from DHistogramAction_GenReconTrackComparison

BCAL Pull vs p

BCAL Pull vs θ

TBT Pull vs p

TBT Pull vs θ

ST Pull vs p

ST Pull vs θ

TOF Pull vs p

FCAL Pull vs p