- 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
Minutes for HF PWG meeting on 2016/1/8
Pile-up protection for min-bias trigger in Run 16
- slide 4,5 - at high ZDC rate -> efficiency loss seen
- slide 6: eff. loss seems to be faster for data w/o pileup protection
- slide 7: double ratio ~ 1 -> no visible effect on HFT/TPC ratio, some effect for larger ZDC
- slide 10/11 - no significant effect on DCA
- the main effect is on the TPC tracking, 5-6% for single track, ~12% for D, may be important for Lambda_c (15-18% eff. lost)
- pileup-protection is on both past and future, so if we run only the future protection, then we could have only half of the effect.
- a possible solution -> loosen the protection conditions
- can we reach both HFT and MTD goals w/o pileup protection? (maybe, but this is difficult)
Zhenyu sent summary slides with updated HFT and MTD projections. We are collecting input till Friday evening PST.
protection tuning - the most efficient way is to wait for collisions and then adjust the parameters.
Zach's presentation on B->e/NPE ratio
- I lost my audio and could not follow the discussion.
- kikola's blog
- Login or register to post comments