An ND 280 tool Christian Hansen UVic Sep

An ND 280 tool Christian Hansen UVic Sep 2006, Canadian ND 280 Soft Meeting, Triumf 1

Intro • Issei suggested what’s needed for short term studies • I’ve written TOACheating. Track e m a n r e t t e b a estions of g g u S : D E T AN W 2

TOACheating. Track • TOACheating. Track gets a TG 4 Trajectory • A TOATrack is being created from the TG 4 Trajectory (by using TFake. Recon) • Some extra information is saved by using TGeo. Manager – Where and in which volume the track starts – Where and with what momentum it enters the TPC TG 4 Trajectory TFake. Recon TGeo. Manager TOACheating. Track TOATrack More info 3

Header To use my c lasses on ne source /hom ut: e/chansen/m y ND 280/user. S etu p. csh 4

Test • Run 10000 events from neut 03. geant. root • Look only at µ trajectories with ID = 1 • Look only at cheating tracks that enters TPC from starting in FGD • The z-coord of the starting points in FGD 5

Test • The z-coordinates of the first points in TPC are not all at the z-edges of the TPC’s • Understood if x or y dimension were bigger for FGD than TPC? No: max. X_FGD = 899. 158 min. X_FGD = -899. 272 max. X_TPC = 1050 min. X_TPC = -1050 max. Y_FGD = 1049. 99 min. Y_FGD = -849. 811 max. Y_TPC = 1198. 74 min. Y_TPC = -1000 • Does this mean there is not a G 4 point everywhere a trajectory enters a volume? 6

Conclusions and Future Work Short TOACheating. Track Term Longer Term TND 280 Helix • Find out why first points on TPC are not on the TPC edges • Add more cheating info: – Length of track in FGD – Process info, why trajectory stopped • A helix to be used for tracking TOATrack. Helix • Defines a helix from a track RECPACK • Checked out but compilation errors More info In my neut repository • More info here: Beeing debugged In my fate repository on neut /home/chansen/my. ND 280/v 1 r 7 7 http: //hepweb. phys. uvic. ca/~hansen/T 2 K/ND 280 SOFT/analysis. html