Station 5 Analysis

• Calibration • Decoding • Data • Analysis Application • Results • Conclusions / Next Steps M.Ellis - Tracker Meeting - 20th April 2007 1

Calibration

• LED Calibration data was taken twice during the data taking period. • I’ve used the second set of data (no LVDS issues) and at FNAL produced a calibration file.

• Aron has gone over the fits and identified 61 channels (out of 1024 ) that need re fitting.

• For now, I use the existing calibration file.

M.Ellis - Tracker Meeting - 20th April 2007 2

Decoding

• As usual a lot of work has gone here.

• We have verified that the data path from the AFEIIT to the VLSB was correct and that the code in G4MICE that makes hits (with an AFE, MCM and Channel) are correct.

• We identified a change in the numbering scheme of the D0 warm end connectors on the external waveguides with respect to the D0 system that is used for reconstructing the data, and this has now been fixed and commited to CVS (Aron again).

M.Ellis - Tracker Meeting - 20th April 2007 3

Decoding contd.

• The internal and external waveguides and the station body itself were

VERY

well labelled (thanks!!!!!!) which made assembly easy (apart from the missing nuts and bolts ;-) • We should be aware for the real trackers, however, that we can’t have 10 different sets of waveguides numbered 1-5 each. (This is probably already defined, I’ve just lost track of it) M.Ellis - Tracker Meeting - 20th April 2007 4

Data

• Apart from the debugging (self injection) and calibration (LED pulser) data we have three main sets: – Self trigger set 1. This was found to have had some bad LVDS connections, likely due to people stepping on the cables while other work was carried out in the area.

– Self trigger set 2. This appears to be good data and is what I’ve analysed for this talk.

– External trigger set 1. The data from the LHB is good, but unfortunately the data from the RHB is not due to a timing issue so this data is not analysed.

M.Ellis - Tracker Meeting - 20th April 2007 5

Analysis Application

• For this talk I used the Station5Test application in G4MICE with the default data cards on the data that can be found from the second period on the web here: – – http://www.mice.iit.edu/scratch/ • The logbook which identifies the runs is here: http://www.mice.iit.edu/scratch/station5log.txt

• I analysed runs 43 – 91 which is a total of 941,910 triggers!

• I set the threshold for making clusters at 5 PE as a quick and easy way to ensure that in the duplets the “other” cluster always has at least 5 PE.

• Apart from this change, the analysis was from the version that is in CVS with no modifications, so can be easily reproduced by anyone else.

M.Ellis - Tracker Meeting - 20th April 2007 6

Number of Clusters and Points

M.Ellis - Tracker Meeting - 20th April 2007 7

Point Positions & Internal Resid.

M.Ellis - Tracker Meeting - 20th April 2007 8

Plane V

M.Ellis - Tracker Meeting - 20th April 2007 9

Plane X

M.Ellis - Tracker Meeting - 20th April 2007 10

Plane W

M.Ellis - Tracker Meeting - 20th April 2007 11

Fibre in Triplets and one Channel

M.Ellis - Tracker Meeting - 20th April 2007 12

Conclusions – Next Steps

• Looking at clusters in Duplets, all 3 planes seem to have a peak at about 10.5 – 11.0 PE.

• Triplet internal residual distribution looks too flat to me, I suspect an alignment or similar issue somewhere means we are not selecting good triplets at the moment.

• Will investigate triplets in detail now that we think decoding is understood and correct and hopefully fix whatever might be left to fix there and re-run all of the self triggered data set 2.

• In parallel will sort out re-fitting in the Calibration application and produce a final calibration file for this data.

M.Ellis - Tracker Meeting - 20th April 2007 13