So called "live time corrections" applied twice by M. Williams is nonsense. <div><font face="arial, sans-serif" class="Apple-style-span">CLAS has no problem with live time corrections. g11 group found that the</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">normalized to the photon flux yield is current dependent. Accidentally this</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">correction was found to be very close to the live time correction. However it doesn't mean</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">that the reason for inefficiency at high current is live time. Personally I think that</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">at high current we have problem with the track reconstruction inefficiency due to</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">the background hits in DC, TOF etc. e1-dvcs study of this phenomena showed that</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">including the background hits (measured by CLAS) to MC data decreases the track</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">reconstruction efficiency by about 15% for 2 track events. it affects all high intensity</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">CLAS experiments. </font></div><div><font face="arial, sans-serif" class="Apple-style-span"><br>
</font></div><div><font face="arial, sans-serif" class="Apple-style-span">The g12 trigger has no dead time at all.</font></div><div><font face="arial, sans-serif" class="Apple-style-span">The only week signal in the g12 trigger is signal MOR. If this logical signal has no dead time</font></div>
<div><font face="arial, sans-serif" class="Apple-style-span">(as it is supposed to be) we do not have problem with g12 trigger.</font></div><div><font face="arial, sans-serif" class="Apple-style-span"><br>
</font></div><div><font face="arial, sans-serif" class="Apple-style-span">Valery</font></div><div><font face="arial, sans-serif" class="Apple-style-span"><br>
</font></div><div><font face="arial, sans-serif" class="Apple-style-span"><br></font></div><div><div class="gmail_quote">On Tue, Feb 8, 2011 at 3:04 PM, Eugene Pasyuk <<a href="mailto:pasyuk@jlab.org">pasyuk@jlab.org</a>> wrote:<br>
<blockquote class="gmail_quote">Gflux was not corrected for anything and I don't see what is there to<br>
correct.<br>
This is a misconception that the live time correction has been applied<br>
twice. It is true that g11 discovered necessity to apply additional rate<br>
dependent correction to the cross section. In fact g11 was the only run<br>
that had to do that.<br>
EG3 was running with very high intensity as well I am not aware they<br>
needed to do something similar to what g11 did.<br>
I believe the problem is not in the live time but in the rate dependent<br>
trigger inefficiency and it turned out that this correction<br>
quantitatively is similar to the live time correction. G11 had other<br>
trigger inefficiency corrections as well.<br>
<br>
Do you need to apply additional corrections to g12 cross sections? I<br>
don't know the answer. This has to be studied.<br>
Just to remind you, photon flux is just one out of several ingredients<br>
for the cross section. You also have to look at yield extraction,<br>
acceptance, trigger efficiency etc.. The hardware trigger setup for g12<br>
was completely different compared to g11.<br>
<font color="#888888"><br>
-Eugene<br>
</font><div><div></div><div class="h5"><br>
On 02/08/11 10:03, Paul Eugenio wrote:<br>
> Hi Eugene,<br>
><br>
> We are looking into several issues we have regarding cross section estimates. One concern we have is with the photon normalizations. I agree that the MOR is not the viable estimate of any intensity depend sag to the live time. G12 ran with the highest photo intensity of any run, and earlier studies using g11 data showed a gflux calculated live time which had a dependence on the beam flux. In order to correct this, the live time corrections where applied twice (as shown by M. Williams). I do not know if gflux code was corrected or if it needed to be corrected. Should we apply this correction twice for g12?<br>
><br>
><br>
> --<br>
> Prof. Paul Eugenio<br>
> Florida State University<br>
> Department of Physics<br>
> Tallahassee, Florida, USA 32306<br>
><br>
> (850) 644-2585<br>
> <a href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a><br>
><br>
><br>
><br>
> On Feb 8, 2011, at 9:38 AM, Eugene Pasyuk wrote:<br>
><br>
>> We also have individual EPICS scalers for every tagger PMT.<br>
>> They are better monitor than MOR.<br>
>><br>
>> -Eugene<br>
>><br>
>><br>
>> On 02/08/11 09:33, John Price wrote:<br>
>>> Sounds like we need the output of gflux as a function of beam current...<br>
>>><br>
>>> On Tue, 2011-02-08 at 06:29 -0800, Eugene Pasyuk wrote:<br>
>>>> MOR rate is not reliable intensity monitor. It is logical OR, it is NOT<br>
>>>> arithmetic sum of all counters.<br>
>>>> It saturates and eventually goes down when you increase flux.<br>
>>>><br>
>>>> -Eugene<br>
>>>><br>
>>>><br>
>>>> On 02/08/11 09:24, Paul Eugenio wrote:<br>
>>>>> Hi,<br>
>>>>><br>
>>>>> I dug out the data from the beam intensity study which was done during the run. Performing a linear fit to the first few points shows that at 60 nA the MOR rate sags by about 8%.<br>
>>>>><br>
>>>>> <a href="http://clasweb.jlab.org/rungroups/g12/wiki/index.php/Beam_Intensity_vs_MOR_rate">http://clasweb.jlab.org/rungroups/g12/wiki/index.php/Beam_Intensity_vs_MOR_rate</a><br>
>>>>><br>
>>>>> --<br>
>>>>> Prof. Paul Eugenio<br>
>>>>> Florida State University<br>
>>>>> Department of Physics<br>
>>>>> Tallahassee, Florida, USA 32306<br>
>>>>><br>
>>>>> (850) 644-2585<br>
>>>>> <a href="mailto:eugenio@fsu.edu">eugenio@fsu.edu</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> G12 mailing list<br>
>>>>> <a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
>>>>> <a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
>>>> _______________________________________________<br>
>>>> G12 mailing list<br>
>>>> <a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
>>>> <a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
>> _______________________________________________<br>
>> G12 mailing list<br>
>> <a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
>> <a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
><br>
> _______________________________________________<br>
> G12 mailing list<br>
> <a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
> <a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
_______________________________________________<br>
G12 mailing list<br>
<a href="mailto:G12@jlab.org">G12@jlab.org</a><br>
<a href="https://mailman.jlab.org/mailman/listinfo/g12">https://mailman.jlab.org/mailman/listinfo/g12</a><br>
</div></div></blockquote></div><br></div>