- fisyak's home page
- Posts
- 2024
- November (1)
- October (4)
- September (3)
- August (6)
- July (3)
- June (3)
- March (1)
- February (4)
- January (2)
- 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
Run XIX trigger T0
I have checked trigger T0 offset for Run XIX Collider samples:
Sample T0 dT ddT freq
{"2019/RF/AuAu200" , 2.3904,-0.0482, 0.0201, 9383180},
{"2019/RF/19GeV" , 2.3675,-0.0023, 0.0106, 9341081},
{"2019/RF/14p5GeV" , 2.3904, 0.0070, 0.0122, 9307123},
{"2019/RF/9p2GeV" , 2.3904, 0.0141, 0.0152, 9188688},
{"2019/RF/7p7GeV" , 2.3904, 0.0362, 0.0144, 9104517}
where T0 trigger time taken from DataBase, dT +/- ddT is the measured difference between z of primary vertices reconstructed using West or East parts of TPC only, respectively, expressed in μs (microseconds).
I do see that triggerT0 (μs) = T0 + dT = (0.1 +/- 0.5) μs + (21.2 +/- 5.4) time buckets (with kind of strange point at 14p5 GeV) i.e. roughly speaking our trigger decision is coming in 21 time buckets from the collision.
- fisyak's blog
- Login or register to post comments