Hi Brad,<br><br>plots that I refer to can be found here:<br><br><a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/</a><br><br><br> So I took a look at the T2 hits for run 2060 (<a href="http://t2_hits_2060.ps">t2_hits_2060.ps</a>) this shows the hits that the DBB.t2 trigger received. I then plotted DBB.t2 making cuts on the hits (<a href="http://t2_2060.ps">t2_2060.ps</a>). In <a href="http://t2_2060.ps">t2_2060.ps</a> the upper left is a plot of DBB.t2 with no cuts, the upper right is DBB.t2 with Ndata.DBB.t2==1 and the bottom plot is Ndata.DBB.t2==2. It seems that the stuff <500 shows up in the 1st hit data and there is none present in the second hit data.<br>
<br>Also listed here is <a href="http://cor_tdc_2060.ps">cor_tdc_2060.ps</a>, which is a plot of the retimed T2 TDCs. Originally I thought that the plateau to the right of the main peak was due to the TDCs being timed off the T6 trigger, but even with retiming the TDCs off the T2 trigger, some still have this plateau to the right of the main peak.<br>
<br>I also plotted the T2 trigger and made cuts on it to various BigBite Cerenkov pmts by cutting on ADCs. For example T2_adc_cut.png, I plotted the T2 trigger with no cuts (black) I then cut on four cerenkov ADCs being greater than 60 channels ~2photo electrons. The cut I used was the following :<br>
<br> BB.cer.a_c[xx]>60.0, where xx is the PMT in this case 5(red), 6 (violet) , 13 (blue) and 16 (green) <br><br>I was hoping to see the peaks at chan >500 change with each ADC cut, but looking at it, they look pretty similar regardless of the PMT that is selected.<br>
<br><div class="gmail_quote">On Wed, Mar 24, 2010 at 4:33 PM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br><blockquote class="gmail_quote">
<div>On Wed, 24 Mar 2010, <a href="mailto:posik@jlab.org">posik@jlab.org</a> wrote:<br>
<br>
> So I have been looking at this T2 timing corrections. All plots are from<br>
> run 2060 and can be found here:<br>
><br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/t6_timing/trig_evo/">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/t6_timing/trig_evo/</a><br>
><br>
> The first plot 2060_t2.png shows the T2 structure on linear scale. Since<br>
> there are more than one peak in this structure I decided to use different<br>
> peaks as the T2 self timing peak and see how that affects the retiming.<br>
</div>[ . . . ]<br>
<div>> It seems that the T2 retiming improves the Cerenkov TDCs no matter what<br>
> self timing peak I select. This can be seen in the 2nd and 3rd plots. I am<br>
<br>
</div>This should be no surprise, since the choice of retiming peak is simply<br>
a constant offset applied to the x-axis -- it just slides all the data<br>
left or right.<br>
<div><br>
> not sure how to go about and begin to determine which of the peaks I<br>
> should use. Any suggestions on where I may start to look?<br>
<br>
</div>>From the perspective of the Cherenkov TDC data, it doesn't really<br>
matter. In the end you'll be cutting around the peak. It doesn't<br>
matter where the peak is. (I would be inclined to center it about zero<br>
for all PMTs.)<br>
<br>
>From the perspective of the experiment, the _real_ question is "what<br>
does the structure in DBB.t2" mean? The two narrow peaks out around 550<br>
are probably due to slight timing differences in the cabling of the<br>
different Cerenkov electronics (so you get a slightly different peak<br>
depending on which PMT fired). That would be easy to establish by<br>
putting a cut on a single PMT (via track position or cherenkov ADC).<br>
<br>
The stuff <550 is a bit of a mystery to me. I know we talked about it<br>
during the run -- there might be some explanation in the Halog. It<br>
could be multiple hits in the DBB.t2 TDC channel -- try cutting on<br>
Ndata.DBB.t2==1 and see if you enhance the self-timing peaks.<br>
<div><br>
> In the evtypebit cuts on the last plot, when I cut on<br>
> (DBB.evtypebits&1<<7)==(1<<7) I end up with no events. I am guessing that<br>
> this is do to the large prescale, which was at 65535?<br>
<br>
</div>I think that prescale (2^16-1) results in the associated trigger being<br>
disabled at the trigger supervisor.<br>
<font color="#888888"><br>
-- Brad<br>
</font><div><br>
--<br>
Brad Sawatzky, PhD <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> -<>- Jefferson Lab / Hall C / C111<br>
Ph: 757-269-5947 -<>- Fax: 757-269-5235<br>
The most exciting phrase to hear in science, the one that heralds new<br>
discoveries, is not "Eureka!" but "That's funny..." -- Isaac Asimov<br>
<br>
_______________________________________________<br>
</div><div><div></div><div>d2n-analysis-talk mailing list<br>
<a href="mailto:d2n-analysis-talk@jlab.org">d2n-analysis-talk@jlab.org</a><br>
<a href="https://mailman.jlab.org/mailman/listinfo/d2n-analysis-talk">https://mailman.jlab.org/mailman/listinfo/d2n-analysis-talk</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Matthew Posik<br>Email: <a href="mailto:posik@temple.edu">posik@temple.edu</a><br>Temple University Physics Dept.<br>Office: BA-319<br>Office #: 215-204-1331 <br>
WebSites:<br>Temple:<br><a href="http://quarks.temple.edu/">http://quarks.temple.edu/</a><br>d2n:<br><a href="http://hallaweb.jlab.org/experiment/E06-014/">http://hallaweb.jlab.org/experiment/E06-014/</a><br>
<br>