[Rga_calib] [EXTERNAL] Re: RGA-Spring2018-Timelines & next steps of calibrations

[Marco Mirazita]

Hello,
the RICH timelines show in all the runs a multi-peak pattern in the time 
distributions, with the peak position separated by about 2 ns.
I investigated a bit the problem at PMT level (the statistics is not 
enough to look at channel level) and it looks like that each PMT shows a 
different multi-peak pattern, and that this pattern changes with time.

This is an expected behavior. In fact, in September 2018, right after 
the end of rga spring 2018, a new RICH firmware was released to fix a 
bug in the initialization of the FPGAs. This bug was generating random 
offsets every time the DAQ was started.
The result is that for rga spring 2018 (and older) data the RICH time 
calibration needs to be performed on every run individually. And because 
of the high statistics required, it can be done only at the end of the 
cooking, when full runs will be available.

Therefore, my plan is to run the RICH time calibration suite on one or 
two full runs as soon as they are available, to check that a good 
calibration can be obtained also for these data, and postpone the 
systematic calibration of the whole data set at the end of pass1.

Marco




Il 2021-04-20 02:37 Nikolay Markov ha scritto:
> Dear all,
>  for HTCC I will need
>  3270
>  3505
>  3946
>  4202
>  Nick.
> 
> -------------------------
> 
> From: Rga_calib <rga_calib-bounces at jlab.org> on behalf of L Smith
> <lcs1956 at me.com>
> Sent: Saturday, April 17, 2021 1:21 PM
> To: Latifa Elouadrhiri <latifa at jlab.org>
> Cc: Nicholaus Trotta <nicholaus.trotta at uconn.edu>; rga_calib at jlab.org
> <rga_calib at jlab.org>
> Subject: [Rga_calib] [EXTERNAL] Re: RGA-Spring2018-Timelines & next
> steps of calibrations
> 
> Dear Latifa,
> 
> I will need runs 3216 and 3260 cooked for ECAL timing calibration
> since my original run range loaded in February started at run 3304.  I
> extended the range down to 3210 so the cooking will need an updated
> timestamp.
> 
> Regards,
> Cole
> 
>> On Apr 16, 2021, at 9:52 AM, Latifa Elouadrhiri <latifa at jlab.org>
>> wrote:
>> 
>> Dear all,
>> 
>> Please find below the latest timelines of RGA-Spring2018
>> https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/ [1]
>> 
>> This is after the first round of FTOF calibrations. Dan has
>> completed the analysis of FTOF timelines and the calibrations are
>> good see below his observations of FTOF calibrations:
>> 
>> ===========================
>> _"1) p1b is good over the full range starting at r3210 (before that
>> is not useable for production), eliminating_
>> _the run ranges for FT studies and RND trigger runs. All other runs
>> have vertex times within +/-10 ps of zero._
>> 
>> _2) p1a is acceptable for nearly the full range with vertex times
>> within +/-20 ps of zero. But there is one small_
>> _run range that has a shift out to 30 ps that I would like to
>> improve. The relevant run range is 3734-3778. I_ _would ask that run
>> 3752 be cooked for further FTOF calibrations_."
>> 
>> ===========================
>> So we are ready for all you to review your subsystem and let us
>> know by Tuesday what runs you will need for us to process in order
>> to complete your subsystem calibrations.
>> 
>> Please let me know if you have any questions,
>> 
>> Best regards,
>> 
>> Latifa
>> 
>>> 
>> _______________________________________________
>> Rga_calib mailing list
>> Rga_calib at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/rga_calib
> 
> 
> 
> Links:
> ------
> [1] https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/
> _______________________________________________
> Rga_calib mailing list
> Rga_calib at jlab.org
> https://mailman.jlab.org/mailman/listinfo/rga_calib