<br><br><div class="gmail_quote">On Wed, May 26, 2010 at 1:40 PM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br><blockquote class="gmail_quote">
<div class="im">On Wed, 26 May 2010, MATTHEW R POSIK wrote:<br>
<br>
> On Wed, May 26, 2010 at 11:05 AM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br>
><br>
> > On Wed, 26 May 2010, MATTHEW R POSIK wrote:<br>
> ><br>
> > > On Wed, May 26, 2010 at 10:15 AM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br>
> > ><br>
> > > > On Sat, 22 May 2010, <a href="mailto:posik@jlab.org">posik@jlab.org</a> wrote:<br>
> > > ><br>
> > > > > So I think I finally got the BB cer multihit TDCs working right. I<br>
> > > > > just use TString cuts for all hits in the TDC. For example the<br>
> > > > > beam line side has 6 hits, so I do something like<br>
> > > > ><br>
> > > > > TString tdc1_1 =<br>
> > > > > "DL.BBcerT01[Ndata.DL.BBcerT01-1]>xx&&DL.BBcerT01[Ndata.DL.BBcerT01-1]<xx"<br>
> > > ><br>
> > > > What happens when Ndata.DL.BBcerTxx==0? Will it attempt to index with<br>
> > > > '-1' or do you watch for that condition prior to invoking this cut?<br>
> > ><br>
> > > Yes, I took this condition in to account by appending the condition<br>
> > > Ndata.DLBBcerTxx!=0 to all 20 TDCs.<br>
> ><br>
> > You should not just add Ndata.DLBBcerTxx!=0 to the end of the Cut<br>
> > string. The software must still evaluate all of the bogus [-1] indexes.<br>
> > If those memory locations are out of scope, then you can segfault or<br>
> > throw some other error. Same problem if you try to invoke a cut for<br>
> > "hit 6" when there are less than 6 hits -- in either case you're<br>
> > indexing beyond the scope of the array. That kind of code is just<br>
> > begging for trouble :-)<br>
[ . . . ]<br>
</div><div class="im">> > It looks like the default limit is 1000. Are you really intending to<br>
> > generating a cut with more than 1000 comparisons? How big do you have<br>
> > to set it?<br>
<br>
> Right now I have it set to 10000. I have five comparisons for 1 hit on TDC1:<br>
><br>
> 1) for Ndata !=0<br>
> 2) && with the TDC hit cut windows<br>
> 3) Hit one less than a TDC channel<br>
> 4) Hit one greater than a TDC channel<br>
> 5) another && between the two high and low TDC channels<br>
<br>
</div>FWIW, I would recommend using a cut like this:<br>
"((abs( DL.BBcerT01[Ndata.DL.BBcerT01-1]) - YYY ) < XXX)"<br>
Where YYY is the nominal peak position for that channel, and XXX is the<br>
width of your cut.<br>
<div class="im"><br>
> This is then done for 20 TDCs. This gives 5*20 = 600 comparisons. I<br>
> then make another cut called "TString tdc_1 = OR of all the one hits<br>
> in the 20 TDCs" this is another 19 comparisons, which now total<br>
> 600+19=619 comparisons This is then done for 6 hits, so the<br>
> comparisons are now 619*6 = 3714 comparisons.<br>
><br>
> Is there a more efficient way to do this? I only did it this way because it<br>
> was the most straight forward.<br>
<br>
</div>It would only be valid to apply all 3714 comparisons for an event if you<br>
actually had 6 hits in all 20 PMTs. That never happens. Your existing<br>
code (may?) attempt to index outside of array bounds thousands of times on<br>
every event. Unless you can find something in the ROOT documentation<br>
that says 'dereferencing outside array bounds will not screw you in some<br>
weird and mysterious way' then I'll have to insist that the code be made<br>
more robust. CINT already does too many stupid things with arrays when<br>
it tries to guess what the user really meant with otherwise invalid<br>
syntax. I really wish it would just crash on invalid syntax...<br>
<br>
If we must use the DL class, then please rewrite your script using the<br>
TLoop framework (ie. T->MakeClass(), etc)<br></blockquote><div><br>I just checked the TDC hits and it seems like most of the (15 of the TDCs) are arrays of 16 and of the other TDCs with array length less than 16, only one was less than the 6 hits that I was looping over (For the H2 elastic runs). So I just fixed that. On the TDCs with array length 16, there seems to be events in hits 1-6 and then a large gap until hit 16 where there is what looks to be one event. <br>
</div><blockquote class="gmail_quote">
<br>
It would be best to update the Cerenkov class so that it knew about<br>
multi-hit TDCs and treated them rationally. The modified class should<br>
expose all of the hits, and should also have a boolean flag (ie. named<br>
BB.Cer.hitQ[PMT]) that would indicate whether any one of the hits land<br>
within a min,max pair added to the DB file. Better yet, set<br>
BB.Cer.hitQ[PMT] to the number of the hit in question. If<br>
BB.Cer.hitQ[PMT] == 0 (or -1), then no hit passed the cut for that<br>
event.<br>
<br>
What is the status of multi-hit Cerenkov class project anyway? Dead in<br>
the water, never started, ???<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div>I have not started that yet, but I would not mind if I could, it would save a lot of hassle makeing TDC cuts.<br><br> -matt<br> <br></div><blockquote class="gmail_quote">
<div><div class="h5">
-- 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>
</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>