- devika's home page
- Posts
- 2018
- May (1)
- 2017
- 2016
- December (1)
- November (1)
- October (1)
- September (4)
- June (2)
- May (2)
- April (5)
- March (4)
- January (3)
- 2015
- 2014
- November (4)
- September (3)
- August (4)
- July (1)
- June (7)
- May (1)
- April (2)
- March (1)
- February (4)
- January (7)
- 2013
- My blog
- Post new blog entry
- All blogs
Run 13 W analysis : Understanding the W reconstruction code
Access MuDsts
Code : St2011W_accessMuDst.cxx [ code ]2. Access Trigges : StMuTriggerIdCollection *tic=&(muEve->triggerIdCollection());
wEve class : Events which passes L2BW triigers
/* $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
*/
- devika's blog
- Login or register to post comments