External Silicon Tracker (EST)
Progress and usefull information
Access
- Documentation
- Results
- Get access to and running the code
The code is currently available in my home directory at RCF under the
directory /afs/rhic/star/users/lmartin/public/star/est/StRoot/St_est_Maker
and splitted in several files (the files describing the objects are
located in the Infrastructure subdirectory):
- St_est_Maker.h : header file for the generic methods and objects
- St_est_Maker.cxx : code file for the generic methods and objects
- St_est_Init.cxx : code file for the initializing methods
- St_est_Projection.cxx : code file for the track projection methods
- St_est_Tracking.cxx : code file for the tracking methods
- St_est_TrackSelection.cxx : code file for the track selection methods
- St_est_RefitBranch.cxx : code file for the fitting methods
- St_est_Eval.cxx : code file for the evaluation methods
- St_est_Wafer.hh : header file for the wafer object
- St_est_Hit.hh : header file for the hit object
- St_est_Hit.cc : code file for the hit methods
- St_est_Branch.hh : header file for the branch object
- St_est_Branch.cc : code file for the branch methods
- St_est_Track.hh : header file for the track object
- St_est_Track.cc : code file for the track methods
- St_est_TPCTrack.hh : header file for the TPC track object
- St_est_Const.hh : header file for constante definitions
The code is using the EGR fitting routines
and some of the StarClassLibrary objects
(mostly the StHelix object). The code compiles under Linux and Solaris
using the SL00e release of the STAR
libraries. It does not mean that it does not work for more recent
releases but simply that we did not try to run EST with them.
Once compiled, the main macro to run the code is mysc.C which :
- update on open the evaluation log file (see below) and the root file.
- load the need libraries
- open the event input file
- call the St_est_Maker
The evaluation results as well as the running parameters (mParams and
mSegment) are output to a file named out.log
which is a link to a file to which a version number is appended. This
number is updated like any shared library when a piece of code is
recompiled. It can be convenient for comparing results obtained in
different conditions and especially when playing with the parameters
and optimizing them.
Currently for the input file the macro reads a file containing one
event in xdf format. The structure of the file is the following :
DataSet | DataSets | Tables | Table Types
|
main | tpc_hits | tphit | tcl_tphit
|
tpc_tracks | tptrack | tpt_track
|
mctrk | tte_mctrk
|
evaltrk | tte_eval
|
svt_hits | scs_spt | scs_spt
|
svgpar | config | svg_config
|
geom | svg_geom
|
shape | svg_shape
|
geant | g2t_vertex | g2t_vertex
|
The svg_shape table is not used anymore. It was previously loaded in
order to determine the active area of each wafer. The g2t_vertex table
is used to refit the TPC track with the main vertex information. At
some point, the geant information should be replaced by something like
the main vertex location estimated from EVR. This structure is not
mandatory as far as the information is available to fill the
objects. The code can be easily modified in order to read the tables
from other inputs such as the database for the SVT/SSD geometry.
- Code Documentation
The code is not well documented. Some of the classes and methods
are commented.
A preliminary version of a user manual is available
here : in ps or
pdf
This document is subject to frequent
changes. Any comments on improving it are welcome.
- Results
-
Commented on screen output of EST
-
Marcelo's page on EST results for year-1
-
Some results of EST for year-2a geometry
-
Impact of the main vertex on the track projection
-
Primary versus secondary track
Performances
-
New results of EST for the year 2001
-
Maria's page on the evaluation using the Association Maker.
-
My page on the Est results using maria's technique and the new fz files.
-
My page on the Est results using Est own evaluator and the new fz files.
Lilian MARTIN
Last modified: Fri Apr 6 10:09:21 CEST 2001