Hi Brad, <br><br> So in the previous email you said<br><br>>Recall that the first hit in time is<br>
> DBB.t2[Ndata.DB.t2 - 1] for Ndata.DB.t2 >= 1<br>
<br> So then my loop should be something like<br><br>for (Int_t hit =Ndata.DBB.t2 - 1; hit>=0 ; hit--)<br>
{<br>
t2_histogram->Fill( DBB.t2[hit] );<br>
}<br><br>**Note all runs discussed here are from run 2060**<br><br>There is something that is confusing me. When I do a T->MakeSelector(), it produces a .h file that give the definitions in the TTree and for T2 for example it gives:<br>
<br> Int_t Ndata_DBB_t2;<br> Double_t DBB_t2[2]; //[Ndata.DBB.t2]<br><br>So according to this, I would expect that DBB.t2 to have two elements DBB.t2[0,1] since Ndata.DBB.t2 = 2. So I plotted Ndata.DBB.t2 see plot<br>
<br> <a href="http://jlab.org/~posik/d2n/BB/trigger/t2_data.png">http://jlab.org/~posik/d2n/BB/trigger/t2_data.png</a><br><br> in the upper left box. There are three bins for Ndata.DBB.t2. Then I plotted various hits in the T2, starting with DBB.t2[Ndata.DBB.t2] in the upper right, DBB.t2[Ndata.DBB.t2-1] in the bottom left and DBB.t2[Ndata.DBB.t2-2] in the bottom right. Since [Ndata.DBB.t2-1] is the first hit in time and [Ndata.DBB.t2-2] would be the last hit in time since Ndata.DBB.t2 = 2, then what is showing up when I plot DBB.t2[Ndata.DBB.t2] ? does it correspond to the 0th or 2nd bin in Ndata.DBB.t2 ?<br>
<br>Also I looked at the Ndata.DBB.BBcerT06 histogram <br><br><a href="http://jlab.org/~posik/d2n/BB/cer/nhit.png">http://jlab.org/~posik/d2n/BB/cer/nhit.png</a><br><br> and Makeselecter gives the foolowing definition:<br>
<br> Int_t Ndata_DBB_BBcerT06;<br> Double_t DBB_BBcerT06[16]; //[Ndata.DBB.BBcerT06] <br><br>But in the Ndata histogram there are 17 bins.<br><br>Also I took another look at the triggers on the BigBite side. Here is the plot of the DBB.t1 trigger vs the TDC 06 <br>
<br><a href="http://jlab.org/~posik/d2n/BB/trigger/2060_t1_tdc.png">http://jlab.org/~posik/d2n/BB/trigger/2060_t1_tdc.png</a><br><br>I can't see too much from here, so I also plotted the DBB.t1 and DBB.t6 vs the DBB.t2 (<a href="http://jlab.org/~posik/d2n/BB/trigger/trig_check/2060_t6_t1_t2_mod.png">http://jlab.org/~posik/d2n/BB/trigger/trig_check/2060_t6_t1_t2_mod.png</a>). To the left is T6 vs T2 and the the right is T1 vs T2. Both of these plots have a <br>
<br>"(DBB.evtypebits&1<<2)==(1<<2) "<br><br>cut applied to them. The T6 vs T2 looks pretty clean, except in the T2 range ~450-500 which is where the T6 carries the T2 timing? And in the T2 histogram this is where a good portion of the events fall <br>
<br> <a href="http://jlab.org/~posik/d2n/BB/trigger/t2_data.png">http://jlab.org/~posik/d2n/BB/trigger/t2_data.png</a><br><br>I then plotted the T1 vs the T2 and now there is a lot going on in the plot. There is a lage block structure centered near chan ~250, as well as at chan ~450-550 and at chan 550-560 there are 2 verticle bands. So does this mean that the T1 trigger is responsible for most of the structure in the T2 trigger, including the two bands at chan 550-560?<br>
<br>Thanks <br>Matt<br> <br>
<br><br><br><div class="gmail_quote">On Tue, Mar 30, 2010 at 9:58 PM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br><blockquote class="gmail_quote">
<div class="im">On Mon, 29 Mar 2010, MATTHEW R POSIK wrote:<br>
<br>
> I think my code is plotting the correct thing, I think I am just<br>
> poorly explaining what I am doing, so let me try this again. So I get<br>
> the value of Ndata.DBB.t2 from the replayed TTree, in the case of run<br>
> 2060 Ndata.DBB.t2 = 2.<br>
> Then to plot the T2 trigger, for each event I loop over the hits<br>
> this is done using the following for loop:<br>
><br>
> for (Int_t hit =0; hit<Ndata.DBB.t2 ; hit++)<br>
> {<br>
> t2_histogram->Fill( DBB.t2[hit] );<br>
> }<br>
><br>
> So is this same thing as DBB.t2[Ndata.DBB.t2-1] , since I have T2[ ]<br>
> running from 0 to Ndata.DBB.t2-1, ie( T2[0] and T2[1] ) ?<br>
<br>
</div>Not quite... reread the previous email. If you want to plot the hit<br>
farthest from the common stop in time (ie. the first hit the TDC sees<br>
after the interaction in the target) then you want to plot the *last*<br>
hit in your TDC array, not the first.<br>
<div class="im"><br>
> I also looked at the shoulder events in TDC 04 from run 2060 (<br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc04.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc04.png</a> )<br>
><br>
> I plotted the re-timed TDC 04 (Red histo) and the not retimed TDC 04 (blue<br>
> histo) on the same plot in log scale. To make these plots I used the<br>
> following cut on each TDC:<br>
><br>
> "BB.tr.n==1&&(DBB.evtypebits&1<<2)==(1<<2)"<br>
><br>
> I then redid the same plot as above, however this time I did not use the<br>
> BB.tr.n==1 cut So the cut on each TDC is now<br>
><br>
> "(DBB.evtypebits&1<<2)==(1<<2)"<br>
><br>
> You can now clearly see a well defined shoulder in both the re-timed TDC 04<br>
> (Red histo) and the not re-timed TDC 04 (blue histo). The plot is here:<br>
<br>
</div>Interesting.<br>
<div class="im"><br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc4_1.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc4_1.png</a><br>
><br>
> So it seems that the one track cut greatly reduces this shoulder, but<br>
> that may just be because that cut right now is throwing out a lot of<br>
> statistics. I also compared the TDC 04 vs the T2 trigger to the<br>
> re-timed TDC 04 vs the T2 trigger, this can be seen here:<br>
><br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc4_t2.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc4_t2.png</a><br>
<br>
</div>Also a good plot.<br>
<div class="im"><br>
> The re-timed TDC looks good against the T2 trigger (right plot),<br>
> except there seems to be a few events that fall at the two horizontal<br>
> bands at DBB.t2 = 560 and DBB.t2 = 565 that do not fall in line with<br>
> the vertical peak at TDC channel ~260. It is these events that<br>
> contribute to the shoulder events in the TDC histogram. I did verify<br>
> this by plotting the re- timed TDC 04 and making a cut on the T2<br>
> trigger, this can be seen here:<br>
><br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc04_t2_shoulder_ct.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc04_t2_shoulder_ct.png</a><br>
><br>
> With that said, I still do not know why these events do not seem to shift<br>
> with the T2 re-timing of the TDC. Could they some how be correlated with the<br>
> T1, since the T2 trigger is formed from the shower and cerenkov and the<br>
> shower had two triggeres, the T1 and T6?<br>
<br>
</div>Hmm... that's a good thought. If that's what's happening you should see<br>
it in a plot like this, but with T1.<br>
<div class="im"> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc4_t2.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc4_t2.png</a><br>
<br>
</div><div class="im">> Also I wanted to check where the structure in the T2 at chan. < 400 were<br>
> falling in the TDC.<br>
><br>
> <a href="http://jlab.org/%7Eposik/d2n/BB/trigger/t2_walk/2060_tdc4_t2selection.png">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/2060_tdc4_t2selection.png</a><br>
><br>
> So I plotted for run 2060 the re-timed TDC 04 with T2<400 (red histo,<br>
> scaled to the blue histo) and the re-timed TDC 04 with T2>400 (blue<br>
> histo). From this is seems that what ever is generating the T2<br>
> trigger as chans<400 are events that do not fall into the timing peak<br>
> of the TDC.<br>
<br>
</div>Remember that if you cutting on T2 outside of its self-timing peak means<br>
(by definition) that some other trigger is carrying the timing. A<br>
significant fraction of the T6 triggers are good electrons (and would<br>
have generated a T2 but for prescaling). Events with a T2 well off its<br>
self timing peak means that the system accepted a trigger pretty far<br>
away in time from whatever fired the Cerenkov component of the T2<br>
trigger -- ie. should be dominated by background.<br>
<br>
Just FYI, you can get some weird apparent structure when plotting the<br>
DBB.xxxTnn[0] hit for high rate data. Things might look more reasonable<br>
if you plot DBB.xxxTnn[Ndata.DBB.xxxTnn-1] instead.<br>
<div class="im"><br>
> I am going to take a look at the trigger diagram and see if I can<br>
> figure anything out.<br>
<br>
</div>Very good. All through this email I just about started typing a<br>
suggestion that you do X, Y or Z only to find in the next paragraph that<br>
you were one step ahead of me -- excellent.<br>
<div><div></div><div class="h5"><br>
-- Brad<br>
<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 -<>- Pager: <a href="mailto:brads-page@jlab.org">brads-page@jlab.org</a><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>
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>