- yezhenyu's home page
- Posts
- 2022
- April (1)
- 2021
- 2020
- 2019
- December (1)
- November (2)
- October (1)
- September (3)
- August (1)
- July (2)
- June (3)
- April (2)
- March (1)
- January (1)
- 2018
- 2017
- November (2)
- September (2)
- August (4)
- July (2)
- June (3)
- May (2)
- April (3)
- March (2)
- February (2)
- January (10)
- 2016
- December (3)
- November (2)
- October (2)
- September (3)
- August (3)
- July (1)
- June (1)
- May (2)
- April (2)
- March (2)
- February (3)
- January (2)
- 2015
- December (2)
- November (6)
- October (1)
- September (5)
- August (3)
- July (6)
- June (1)
- May (7)
- April (3)
- March (1)
- February (7)
- 2014
- 2013
- May (1)
- My blog
- Post new blog entry
- All blogs
HF PWG Meeting Minutes by Zhenyu - 2016/12/22
1) Consistency check between D0 and NPE v2 - Long Zhou
slide 3: PHENIX used BBC+ZDC for reaction plane construction, and thus much reduced non-flow
slide 6: three scenarios of B v2 correspond to 1) b quark v2=light quark v2 and full caolscence 2) 0 b quark v2 and full coalscence 3) 0 b quark v2 and 0 coalscence
slide 17/18: less than 2 sigma difference for low pT if combining the first few data points.
2) Run11 Au+Au Upsilon->ee - Zaochen ye
slide 12: in the fit function, Yield1S and Yield2S3S are raw yields, Eff2S3S is put there to keep the 2S3S PDF normalization equal one
slide 13: Shuai used STAR published pp 1S+2S+3S cross-section, and world average 1S:2S+3S ratio to get 2S+3S p+p reference. Zaochen used STAR published pp 1S cross-section, and world average 1S:2S+3S ratio to get 2S+3S p+p reference
slide 14: Rongrong: bbbar to DY ratio fluctuates drastically among different centrality bins. Maybe one needs to constrain their relative contribution in the fit. Zaochen: here it uses Pythia default bbbar. When using decorrelated bbbar, the bbbar/DY ratio changes significantly and the effect on Upsilon will be assigend as a systematic uncertainty. The data does not allow to constrain the bbbar and DY relative contributions.
slide 15: Comparable statistics between Run10 and Run11 data with Vz<30 cuts, while Run10 fits unlike and like-sign simultaneously while Run11 fit unlike-like. Run11 results can be improved by 1) widen vertex cut from 30 -> 100 cm 2) use mixed event background 3) optimize cuts separately for 1S and 2S+3S
- yezhenyu's blog
- Login or register to post comments