[g13] sc calibration

Pawel Nadel-Turonski turonski at jlab.org
Thu Dec 16 00:32:31 EST 2010


Hi Danny,

Having the TOF 1 ns off is too much. If you can't make the 54730-54750 
run range to work, maybe we can skip it during the bulk of g13a cooking 
and do those 20 runs later? Maybe an adjustment of tag2tof would be 
needed for that range?

I am still curious, however, about the runs around 54162. Did you try to 
cook them with constants from adjacent ranges? And if so, did it help?

Cheers,

     Pawel

On 12/15/2010 4:24 PM, martdann at jlab.org wrote:
> The plots for the g13a recalibration are posted
> http://jlab.org/~martdann/TOF_analisis/g13a/
>
> There is not much improvement except for some paddles like 44 in sector 6
> (bottom right), although the double peaking problem persists.
> I do not see big improvements in the forward region.
>
> As extra stuff in the same directory, I was checking run range 54730-54750
> for g13b, but again, even with the change in Tagger constants, the paddles
> are not aligned with zero, instead jumping around (see bottom
> fit_54743_new and rck).
>
> Cheers,
>
> Danny
>
>> Actually, which paddles were fixed?  Were you mostly fixing back angle
>> paddles in these regions, or forward angle paddles (1 - 23) also?
>> Because if it's only 24 and back the EC won't change...
>>
>>    - Paul
>>
>> On Dec 14, 2010, at 12:03 PM, martdann at jlab.org wrote:
>>
>> 53539 non stop 'till 53742. run 53333 alone. There is still a small
>> range
>> to check according to your list, below 53539.
>>
>>
>>
>>> Can you let me know which run ranges were recalibrated for g13a (and
>>> if they're finished)?  That way I can redo EC for those regions.
>>> Thanks!
>>>
>>>   - Paul
>>>
>>
>
> _______________________________________________
> g13 mailing list
> g13 at jlab.org
> https://mailman.jlab.org/mailman/listinfo/g13


More information about the g13 mailing list