- fisyak's home page
- Posts
- 2024
- 2023
- December (2)
- November (1)
- October (2)
- September (3)
- August (3)
- July (2)
- June (4)
- April (2)
- March (2)
- February (1)
- January (2)
- 2022
- 2021
- December (2)
- October (2)
- September (1)
- August (2)
- June (3)
- May (1)
- April (2)
- March (3)
- February (5)
- January (4)
- 2020
- 2019
- 2018
- 2017
- December (3)
- October (2)
- September (1)
- August (7)
- July (3)
- May (2)
- April (1)
- February (1)
- January (2)
- 2016
- 2015
- November (1)
- October (2)
- September (4)
- August (1)
- July (1)
- June (2)
- May (4)
- April (1)
- March (1)
- February (3)
- January (1)
- 2014
- 2013
- 2012
- 2011
- 2010
- My blog
- Post new blog entry
- All blogs
Track by track and hit by hit analyses for dev and SL24y (Alignment2024) for AuAu200_2016 sample
Updated on Tue, 2024-09-17 10:58. Originally created by fisyak on 2024-09-17 10:58.
In this post I am trying to answer the question "How effect the code changes due to new TPC alignment schema on old production with old alignment ?"
- The codes changes due to new alignment schema (Alignment2024) with "old" alignment do not affect the drifting hits. There is an effect on the prompt hits which should be addressed later.
- No changes in the track parameters have been observed.
- The hit sharing between tracks has been lost during the last merging with TFG (~2014). The hit sharing adds ~4% to track reconstruction efficiency and this is main source of ~10% increase of yield in the reconstruction of strange particle decays observed in comparison P24ia and TFG24c/d productions.
https://www.star.bnl.gov/~fisyak/star/TbyT/dev_SL24y_AuAu200_2016/
»
- fisyak's blog
- Login or register to post comments