Difference between revisions of "Track Finding/Fitting 2006"

From GlueXWiki
Jump to: navigation, search
(May 22, 2006)
Line 12: Line 12:
 
* Resolutions seen by Level-3 trigger
 
* Resolutions seen by Level-3 trigger
  
=
+
= Non-uniform B-field =
  
 +
One of the problems with the current tracking code is that it is not terribly accurate at determining the particle's
 +
momentum. This is because the fit is a pure helix and the momentum is derived from the radius of the helix and
 +
the theta angle.
  
 
[[Image:bfield_cdc_fdc.gif]]
 
[[Image:bfield_cdc_fdc.gif]]

Revision as of 14:56, 22 May 2006

May 22, 2006

In preparation for the GlueX presentation at PAC 30, I have started looking at what kind of tracking resolutions can be obtained from the current GlueX track finding code. This is built on the earlier work documented in [GlueX Note 528] .

It is important to note that the goal of the code used here is to find tracks and give initial parameters for input to the final (Kalman) fitter. The final fitter is not yet written. Resolutions obtained from the simple helical fits of the track finder are useful for:

  • Upper limits on tracking resolutions
  • Resolutions seen by Level-3 trigger

Non-uniform B-field

One of the problems with the current tracking code is that it is not terribly accurate at determining the particle's momentum. This is because the fit is a pure helix and the momentum is derived from the radius of the helix and the theta angle.

Bfield cdc fdc.gif Ro vs theta no sin theta.gif File:Ro vs theta 1GeVpi+.gif Ro vs theta ConstField.gif Ro vs theta FieldMap.gif Ro vs theta FieldMap z-cut.gif