Log entry time 03:02:45 on November 12, 2008

Entry number 248289

Fig. 2 BigBite t3 Trig 5 and Trig 3

Fig. 3 BigBite t3 Trig 3 only

Fig. 4 BigBite t4 all Trig 5

From these plots, we can see clearly that the problem is still there. The T3 is moved earlier by 20ns, this means that we are back to the HRS retiming window. (solved half) see http://www.jlab.org/~adaq/halog/html/0811_archive/081111032423.html

But T1 are only moved earlier by 60 ns. This means that the T3 is moved from 390 ns to 370 ns and T1 is moved from 430 ns to 370 ns. Now T3 still cut into our coincidence peak. This is a big issue for the BigBite Timing. We need to get this fixed.

As we can see clearly, that T3 will cut into the whole coincidence window. 140ns coincidence window, T3 cut about half. This problem can not be solved, if we do not touch HRS. This is why it is still here.

The problem is that we did not move the T1 earlier enough. But from the plot, we can see that T1 is just in the middle of the coincidence window (This is good). So I think that we should do the retiming on the BigBite. This will solve all our problems.

A copy of this log entry has been emailed to: kalyan@jlab.org,vasulk@jlab.org,camsonne@jlab.org,moffit@jlab.org,jiang@jlab.org,jpchen@jlab.org,rom@jlab.org

Figure 1

Figure 2

Figure 3

Figure 4