- kikola's home page
- Posts
- 2023
- 2021
- 2017
- December (1)
- 2016
- 2015
- 2014
- December (2)
- November (2)
- October (3)
- September (1)
- August (3)
- July (2)
- June (2)
- April (3)
- February (3)
- January (1)
- 2013
- December (2)
- October (4)
- September (2)
- August (2)
- July (2)
- June (3)
- April (4)
- March (4)
- February (1)
- January (2)
- 2012
- December (2)
- October (2)
- September (3)
- August (3)
- July (7)
- June (1)
- April (1)
- March (2)
- February (2)
- January (1)
- 2011
- 2010
- 2009
- 2008
- My blog
- Post new blog entry
- All blogs
QA for Au+Au 200GeV run 7 - Multiplicity vs. Vz
QA - Stability of Multiplicity vs. Vz
These results follow up the heavy flavor hypernews discussion about centrality selection for Au+Au Run 7: http://www.star.bnl.gov/HyperNews-star/protected/get/heavy/2050/1/1/1/1.html
- Data set: 42.4 M events of AuAu 200GeV run 7, "2007ProductionMinBias" (P08ic)
- Trigger ID: 200013 (ZDC coincidence+VPD cut at 5 cm. Killer bits off.)
- Event cuts: only events with bad vertex removed
- Global track cuts: similar to cuts for Reference Multiplicity
- No. Fit Pts > 10
- |η| < 0.5
- Vertex 3D-Dca < 3cm
General conclusion: Refenrence Mult. and No. of global tracks with cuts similar to Refenrence Mult. have similar behavior.
Fig 1: Mean of Reference Multiplicity and No. of. global tracks (with cuts like for RefMult) vs Vertex-Z position
Fig 2: Reference Multiplicity for different classes of Vz
Fig 3: No. of global tracks (with cuts like for RefMult) for different classes of Vz
Fig. 4: Reference Multiplicity vs Vz
Fig. 5: No. of global tracks with cuts like for RefMult vs Vz
Fig. 6: Vz of primary (highest ranked) vertex
Fig. 7: No. of primary vertices per event.
- kikola's blog
- Login or register to post comments