ePIC pfRICH mailing list

[Grzegorz Kalicy <kalicy AT cua.edu>]

Hi Alexander,

We asked Roman to take a quick look, here is his feedback:

"There are two issues I noticed.
In the standalone simulation for ePIC we always use theta range of
[24,161] degree (which correspond to eta of [-1.55,1.79] ) but in the
macro it is [-1.64, 1.25] (
https://github.com/eic/irt/blob/main/delphes/scripts/delphes-dirc.C#L33
). Also the Cherenkov tracking resolution map (ctr_map_p1_0.95.root) was
created for [25, 153] degree, so one should take care of out of boundary
values of theta (e.g. if (theta < 25) theta = 25; if (theta > 153) theta
= 153;)

The second issue is the radius of the DIRC. It should be changed to
729.6 mm ( at
https://github.com/eic/irt/blob/main/delphes/scripts/delphes-dirc.C#L44 )"

Cheers,

Greg

On Fri, Nov 11, 2022 at 11:04 AM Kiselev, Alexander <ayk AT bnl.gov> wrote:

  Greg, Joe,

  (Cc to the pfrich list)

  for pfRICH performance validation we are going to use a hybrid of EICrecon (tracks) and a Delphes-like add-on for PID detectors like it was written for ATHENA a year ago.

  I think it would make perfect sense to re-create a Dephes parameterization for the ePIC DIRC as well, to see what happens in the overlap region around eta ~ -1.5 .

  Can you please have a look at this ATHENA script (I believe the format is self-explaining)

https://github.com/eic/irt/blob/main/delphes/scripts/delphes-dirc.C

  and tell me how to adjust the parameters for ePIC, to the best of your understanding? In particular, can I use the same ctr_map_p1_0.95.root file?

  Thank you,

    Alexander.