60 likes | 151 Views
This report details the implementation of TRD acceptance definition in the Tracker system, including positioning tubes, introducing contours, and applying cuts for performance studies before and after acceptance cut. It also highlights the impact on TRD hit counts and proton detection in various layers.
E N D
Basic idea: • There are 20 layers of TOF (each has 2 sublayers in Z) • One has to use nominal position of tubes (ladders) and define a geometrical cut applied to TrTrack object.
What has been done? • Geometrical position of each 5248 tubes was extracted from gbatch geometry. • The contours which corresponds to ladders dimensions has been introduced for each TRD layer ( same contour for 2 sublayers ). • Cut has been implemented in AMS02Cut. • Classname: TrdAcceptanceCut( const char* name, Int_t *p_trk_id, Double_t fiducial)
Tracker tracks on TRD z levels Before TRK TrdAcceptacne cut After TRK TrdAcceptacne cut
TRD hits All hits in event Hits which belongs to TrdTrack
TRD perfomance studies:average number of the TRD Raw hits on TRD track Protons [3, 500] GV, Ntrd Hits in layers [0-3]>2, [4-15]>8, [16-19]>2 Beforte acceptance cut (last week): After acceptance cut: The only way to remove lat-long dependance is ask for R>20 GV events After acceptance and R>20 GV cut: