Difference between revisions of "Track Finding/Fitting 2006"
From GlueXWiki
| Line 1: | Line 1: | ||
| − | |||
===May 22, 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 | ||
| + | [[http://argus.phys.uregina.ca/cgi-bin/private/DocDB/ShowDocument?docid=528&version=1 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 | ||
[[Image:bfield_cdc_fdc.gif]] | [[Image:bfield_cdc_fdc.gif]] | ||
Revision as of 13:28, 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
