[Halld-pid] TOF Points

[Beni Zihlmann]

Hi All,

It looks like Simon identified the problem. The phase offset parameter
in the data base is wrong. It is set to one while it should be zero.
This has the consequence that about a 1/6 th of all events are off by
20ns.
I am currently checking what the else will go wrong with the phase
parameter is set to zero. I assume the overall timing offset for the TOF
will be off by 4 ns. This is part of Mikes general calibration. Hence I
include him in this email.

cheers,
Beni



On 11/09/2015 09:02 AM, Beni Zihlmann wrote:
> Some Additional Information:
>
> This event 72 has plenty of TOF Hits however the code does not
> make any good TOFPaddleHits out of them and as a consequence
> there are no TOFPoints!
> See below the list of TOFHits that show clearly that there should
> be TOFPaddleHits and TOFPoints in this event!
>
> Another question is, why does the hdview2 display show TOF Points
> indicated by the small circles but the analysis code does not!!!!!!
>
> 72 NO TOF POINT FOUND around -56 / -52.8306   0
> TOF POINTS: 0
> TOF PADDLE HITS: 0
> TOF HITS:
> 1    14    0    21.9892    0.00180846
> 1    19    0    18.9116    0.00340961
> 1    14    1    15.9522    0.00282884
> 1    19    1    20.0516    0.00300154
> 0    13    0    22.5638    0.00196538
> 0    19    0    -24.383    3.38461e-05
> 0    26    0    21.1689    0.00260192
> 0    27    0    21.1554    0.00268269
> 0    29    0    177.607    0.000225769
> 0    13    1    16.8317    0.00314423
> 0    26    1    18.682    0.00251154
> 0    27    1    18.361    0.00305077
> 0    29    1    181.224    0.000116923
> 1    14    0    -1.1103    0
> 1    16    0    2657.98    0
> 1    17    0    2148.19    0
> 1    19    0    -6.62601    0
> 1    21    0    2656.27    0
> 1    19    0    1301.28    0
> 1    26    0    449.838    0
> 1    14    1    -8.18142    0
> 1    16    1    2657.57    0
> 1    17    1    2148.19    0
> 1    19    1    -4.21791    0
> 1    19    1    1301.18    0
> 1    21    1    2656.77    0
> 1    26    1    451.372    0
> 0    13    0    -1.64007    0
> 0    26    0    -4.20047    0
> 0    27    0    -4.11068    0
> 0    29    0    154.786    0
> 0    13    1    -7.93381    0
> 0    23    1    2655.92    0
> 0    26    1    -6.16121    0
> 0    27    1    -6.42895    0
> 0    29    1    158.365    0
>
>
>
>
> On 11/09/2015 08:06 AM, Beni Zihlmann wrote:
>> Hi All,
>> attached is a screen shot of event 72 of run 3179. There are 2 tracks
>> that go forward and hit the FCAL. There are also several TOF paddles hit
>> as indicated by the viewer. However non of the DTOFPoints that are
>> calculated from the TOF paddle hits overlap with any of the FCAL hits
>> or the two tracks that are associated with the FACL hits. As a result
>> the tracks do not have any match points with the TOF.
>> This can't be right. Something must be going wrong in our code!
>> This is also seen by Elton who pointed out that the matching efficiency
>> of a charged track that does match with an FCAL shower with the TOF
>> is very bad. This efficiency should be close to 100% but it is way lower
>> more like 50%. Again, I think this is a problem somewhere in our code
>> not the detector itself.
>>
>> cheers,
>> Beni
>>
>>
>> _______________________________________________
>> Halld-pid mailing list
>> Halld-pid at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/halld-pid
>
>
>
> _______________________________________________
> Halld-pid mailing list
> Halld-pid at jlab.org
> https://mailman.jlab.org/mailman/listinfo/halld-pid

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/halld-pid/attachments/20151109/0a243242/attachment.html>