[d2n-analysis-talk] (no subject)

[posik at jlab.org]

Hi Brad,

  So I have been working on the BB cerenkov multi hit TDCs. I first tried
to do this by running a script that implements the TDC cuts though
strings ie

   T->Draw(var,"DBB.BBcerT04<400.0 && "DBB.BBcerT04>150.0")

Since each TDC can handle 16 hits I wrote some code that loops over all 16
hits for a given TDC and then histogramed it. In this case I chose to look
at TDC 14, this is called tdc.ps. To check that these are doing what I
want them to, I then plotted the full TDC 14, full_tdc.ps. However when
applying the multihit TDC 14 as a cut, I run into a problem. For each of
the 16 hits I cut on the range: 150 < TDC chan. < 400. Since I then want
to include this range for all 16 hits, I OR the 16 hits together. For
example

   TDC_cut = (range cut of hit 0)||(range cut of hit 1)||...||(range cut
of hit 16). where range cut is just the tdc chan range given above.

 What I would expect to see it peaks for each hit that fall into this
range cut. However, I see this but also some other stuff to the right of
this range. I think this may be do to me ORing each of the hits together,
but I am not sure how to remove the stuff to the right of the range that
I want. Any suggestions?

 Next, I left making the cuts using strings and instead I opened the
rootfile and put the DBB hits and TDCs into arrays using

  GetBranchAddress(  );

 I then wrote a program that loops over all the hits on all the TDCs for
each event. I was able to generate the following histograms for runs
2063-2065:

         beam_tdc_2063.ps,rhrs_tdc_2063.ps
            --these show the hit number on that pmt, as well as the
multihit TDC signal in blue and the tdc cut in red that I
apply to the ADC for the beam line side and the right hrs
side.

         adc_2063.ps
            --shows the corrected ADCs with the TDC cut applied.
-Matt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: tdc.ps
Type: application/postscript
Size: 14554 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0006.ps 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: full_tdc.ps
Type: application/postscript
Size: 9692 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0007.ps 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tdc_cut.ps
Type: application/postscript
Size: 13816 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0008.ps 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: beam_tdc_2063.ps
Type: application/postscript
Size: 125095 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0009.ps 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rhrs_tdc_2063.ps
Type: application/postscript
Size: 123954 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0010.ps 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: adc_2063.ps
Type: application/postscript
Size: 143692 bytes
Desc: not available
Url : https://mailman.jlab.org/pipermail/d2n-analysis-talk/attachments/20100311/013616e0/attachment-0011.ps