<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Dear Marco,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you for the evaluation of the timeline calibrations of the RICH based on the RGA_Spring 2018 data. I have the following questions:</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<ol>
<li>Once the data pass1 is completed and you perform the RICH calibrations, can you reprocess the RICH engine by itself to take into account the new calibration constants? </li><li style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
What is the timeline to complete such process?<br>
</li><li style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Do you need any specific/additional outputs to perform such calibration that we have to take into account when we process the data.</li><li style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We are in the process of cooking several runs for the calibrations of the other CLAS12 subsystems I would like you to go ahead and calibrate all of them that we demonstrate that your procedure is working on Spring2018 data. We will let you know about the location
of the files as soon as they are available.<br>
</li></ol>
<div>Best regards,</div>
<div><br>
</div>
<div>Latifa</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div>
<div id="appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Marco Mirazita <Marco.Mirazita@lnf.infn.it><br>
<b>Sent:</b> Thursday, April 22, 2021 6:46 AM<br>
<b>To:</b> Nikolay Markov <markov@jlab.org><br>
<b>Cc:</b> Lee Smith <lcs1956@me.com>; Latifa Elouadrhiri <latifa@jlab.org>; rga_calib@jlab.org <rga_calib@jlab.org>; Nicholaus Trotta <nicholaus.trotta@uconn.edu>; Valery Kubarovsky <vpk@jlab.org>; marco contalbrigo <mcontalb@fe.infn.it><br>
<b>Subject:</b> Re: [Rga_calib] [EXTERNAL] Re: RGA-Spring2018-Timelines & next steps of calibrations</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Hello,<br>
the RICH timelines show in all the runs a multi-peak pattern in the time <br>
distributions, with the peak position separated by about 2 ns.<br>
I investigated a bit the problem at PMT level (the statistics is not <br>
enough to look at channel level) and it looks like that each PMT shows a <br>
different multi-peak pattern, and that this pattern changes with time.<br>
<br>
This is an expected behavior. In fact, in September 2018, right after <br>
the end of rga spring 2018, a new RICH firmware was released to fix a <br>
bug in the initialization of the FPGAs. This bug was generating random <br>
offsets every time the DAQ was started.<br>
The result is that for rga spring 2018 (and older) data the RICH time <br>
calibration needs to be performed on every run individually. And because <br>
of the high statistics required, it can be done only at the end of the <br>
cooking, when full runs will be available.<br>
<br>
Therefore, my plan is to run the RICH time calibration suite on one or <br>
two full runs as soon as they are available, to check that a good <br>
calibration can be obtained also for these data, and postpone the <br>
systematic calibration of the whole data set at the end of pass1.<br>
<br>
Marco<br>
<br>
<br>
<br>
<br>
Il 2021-04-20 02:37 Nikolay Markov ha scritto:<br>
> Dear all,<br>
> for HTCC I will need<br>
> 3270<br>
> 3505<br>
> 3946<br>
> 4202<br>
> Nick.<br>
> <br>
> -------------------------<br>
> <br>
> From: Rga_calib <rga_calib-bounces@jlab.org> on behalf of L Smith<br>
> <lcs1956@me.com><br>
> Sent: Saturday, April 17, 2021 1:21 PM<br>
> To: Latifa Elouadrhiri <latifa@jlab.org><br>
> Cc: Nicholaus Trotta <nicholaus.trotta@uconn.edu>; rga_calib@jlab.org<br>
> <rga_calib@jlab.org><br>
> Subject: [Rga_calib] [EXTERNAL] Re: RGA-Spring2018-Timelines & next<br>
> steps of calibrations<br>
> <br>
> Dear Latifa,<br>
> <br>
> I will need runs 3216 and 3260 cooked for ECAL timing calibration<br>
> since my original run range loaded in February started at run 3304. I<br>
> extended the range down to 3210 so the cooking will need an updated<br>
> timestamp.<br>
> <br>
> Regards,<br>
> Cole<br>
> <br>
>> On Apr 16, 2021, at 9:52 AM, Latifa Elouadrhiri <latifa@jlab.org><br>
>> wrote:<br>
>> <br>
>> Dear all,<br>
>> <br>
>> Please find below the latest timelines of RGA-Spring2018<br>
>> <a href="https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/">https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/</a> [1]<br>
>> <br>
>> This is after the first round of FTOF calibrations. Dan has<br>
>> completed the analysis of FTOF timelines and the calibrations are<br>
>> good see below his observations of FTOF calibrations:<br>
>> <br>
>> ===========================<br>
>> _"1) p1b is good over the full range starting at r3210 (before that<br>
>> is not useable for production), eliminating_<br>
>> _the run ranges for FT studies and RND trigger runs. All other runs<br>
>> have vertex times within +/-10 ps of zero._<br>
>> <br>
>> _2) p1a is acceptable for nearly the full range with vertex times<br>
>> within +/-20 ps of zero. But there is one small_<br>
>> _run range that has a shift out to 30 ps that I would like to<br>
>> improve. The relevant run range is 3734-3778. I_ _would ask that run<br>
>> 3752 be cooked for further FTOF calibrations_."<br>
>> <br>
>> ===========================<br>
>> So we are ready for all you to review your subsystem and let us<br>
>> know by Tuesday what runs you will need for us to process in order<br>
>> to complete your subsystem calibrations.<br>
>> <br>
>> Please let me know if you have any questions,<br>
>> <br>
>> Best regards,<br>
>> <br>
>> Latifa<br>
>> <br>
>>> <br>
>> _______________________________________________<br>
>> Rga_calib mailing list<br>
>> Rga_calib@jlab.org<br>
>> <a href="https://mailman.jlab.org/mailman/listinfo/rga_calib">https://mailman.jlab.org/mailman/listinfo/rga_calib</a><br>
> <br>
> <br>
> <br>
> Links:<br>
> ------<br>
> [1] <a href="https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/">https://clas12mon.jlab.org/rga/pass0/v2.2.36/tlsummary/</a><br>
> _______________________________________________<br>
> Rga_calib mailing list<br>
> Rga_calib@jlab.org<br>
> <a href="https://mailman.jlab.org/mailman/listinfo/rga_calib">https://mailman.jlab.org/mailman/listinfo/rga_calib</a><br>
</div>
</span></font></div>
</div>
</body>
</html>