1. Drift velocity and tracking Michele Faucci Giannelli, Mike Green, Fabrizio Salvatore

2. Drift velocity Several suggestion, no definitive answer. –Scatter plot –Ratio –Sum of consecutive chambers –Recursive methods –… The fact is this is a system with 8 equations and 10 variables. Some approximations are needed.

3. Drift velocity ECal DC1 DC2 DC3DC4 t1t1 t2t2 t3t3 t4t4 All quantity have to be considered averaged Offset between DC1-DC2 and DC3- DC4 is 0.2mm, negligible on first approximation Y should be easier because of the better alignment: –OffY DC should be very small

4. X ECAL vs t DC

5. (36-X ECAL )/t DC

6. (T 1 +T 2 )/L

7. Results First method abandoned, in case fit a 2D Gauss and take the axis. Second method (X only) Third method, v1=v2 and v3=v4 (Y too) RunEnergyDC1DC2DC3DC4 23009730,03050,02840,03460,303 23009810,0310,02820,03860,0292 23009920,03050,02840,0350,0303 23010040,03050,02820,03450,0302 23010160,03030,02820,03420,0301 23010450,03010,02780,0340,0299 2302551,50,02990,02780,03390,0294 DC1-2 X0,0296 DC1-2 Y0,0303 DC3-4 X0,0327 DC3-4 Y0,0273

8. New proposal Get the mean from DC hits and Ecal hits from 1000 events Plot similar to scatter plot but insensible to beam spread The problem is the Ecal, the mean of the distribution is 19 while should be 0.

9. Suggestion for tracking software TDCXXX TrackerHit TBTrackProjection TBTrack MCDATA DriftChamberDigitizationDriftChambertoTrack TBTrackCombiner DataBase DBHandler The LCIO class LCVector (DESY) TDCContainer (CERN) DriftChamberParameters +GetDriftVelocity() +GetOffsetX() +GetOffsetY() +Set… -DriftVelocity: real -Errors: real matrix -OffsetX: real -OffsetY: real +GetXatEcal() +GetXatHcal() +GetXatTC() +GetErrorX…() +GetXatZ(real) -Theta: real -Offset: real -Error: real matrix -XTracks: TBTrackProjectionVec -YTracks: TBTrackProjectionVec +NTrack: integer +GetX() +GetY() +GetNTracks() +GetXTrack(int) +GetYTrack(int)

10. In details Database: –has to contain efficiency parameter? TBTrackProjection: –Get value and error at calorimeters –Get value and error at Z TBTrack: –Number of tracks –Get best X and Y projection –Get requested X and Y projection

11. Processors DCDigitization: –Need DB interaction to get drift velocity and intrinsic resolution, more news after Roman-Anne Marie meeting. –Re-Check that the hit is well selected DCtoTrack: –New output –New fit class as to be used –How to clean bad hits? I’m using only 34<t<2*peak, any better idea?

12. Processors(2) TrackCombiner: –Has to be written from scratch –What to do if X has 2 good tracks and Y only 1? DBHandler: –No idea if it has to be rewritten or if we can use the old one.