Run 13 W analysis : Understanding the W reconstruction code

Updated on Fri, 2017-01-06 12:40. Originally created by devika on 2013-03-26 21:45.

Access MuDsts

Code : St2011W_accessMuDst.cxx [ code ]

1. Access MuDst events : StMuEvent* muEve = mMuDstMaker->muDst()->event();

2. Access Trigges : StMuTriggerIdCollection *tic=&(muEve->triggerIdCollection());

wEve class : Events which passes L2BW triigers

3. Access vertex : StMuPrimaryVertex* V= mMuDstMaker->muDst()->primaryVertex(iv);

Track Flags :

/* $STAR/StRoot/StEvent/StTrack.h

* mFlag=zxyy, where z = 1 for pile up track in TPC (otherwise 0)

* x indicates the detectors included in the fit and

* yy indicates the status of the fit.

* Positive mFlag values are good fits, negative values are bad fits.

* The first digit indicates which detectors were used in the refit:

* x=1 -> TPC only

* x=3 -> TPC + primary vertex

* x=5 -> SVT + TPC

* x=6 -> SVT + TPC + primary vertex

* x=7 -> FTPC only

* x=8 -> FTPC + primary

* x=9 -> TPC beam background tracks

* The last two digits indicate the status of the refit:

* = +x01 -> good track

* = -x01 -> Bad fit, outlier removal eliminated too many points

* = -x02 -> Bad fit, not enough points to fit

* = -x03 -> Bad fit, too many fit iterations

* = -x04 -> Bad Fit, too many outlier removal iterations

* = -x06 -> Bad fit, outlier could not be identified

* = -x10 -> Bad fit, not enough points to start

* = +x11 -> Short track pointing to EEMC

Groups:

The STAR experiment