Hi Brad,<br><br>Here is the link to the plots that I refer to for the t2 timing:<br><br> <a href="http://jlab.org/~posik/d2n/BB/trigger/t2_walk/t6_timing/">http://jlab.org/~posik/d2n/BB/trigger/t2_walk/t6_timing/</a><br>
<br> I took a look at the timing on the TDCs. Your explanation makes a lot of sense. I plotted a corrected TDC 03 to carry the T2 timing and also show the TDC with no T2 timing correction (corrected_TDC03.png and uncorrected_TDC03.png). As you can see the peak is much narrower and has more events under it. But there seems like there may still be a little bit of a shoulder to the right of the dominate peak. This may be related to the self-timing peak that I chose. There seems to be more than one peak in the DBB.t2 trigger (t2.png), I selected 560 as my self-timing peak, but I am not sure that this selection is correct.<br>
<br>As for the tracking variable, I thought I had fixed this too. I realized this problem when looking at some physics replays for the H2 elastic events. To correct it I ended up removing some cuts from the .cdef file. But the cdef file that I am using now is empty. And when looking at the H2 elastic events that I replayed yesterday on my current d2 set up I get more one-track than 0-track events. Where as when I replay a 4-pass 3He and a 5-pass N2 run I get more 0-track events. These can be seen here:<br>
<br><a href="http://jlab.org/~posik/d2n/BB/tracks/">http://jlab.org/~posik/d2n/BB/tracks/</a><br><br>I checked my analyzer setup. I am currently using Brad's version of the analyzer ( the one with the THaDecData fix) so when I do "which analyzer" I get:<br>
<br>/home/brads/d2n_analysis_copy/analyzer/analyzer<br><br>I am symbolicly linked to the bigbite library:<br><br> /usr/local/d2n_analysis/d2n/bigbitelib/libBigBite.so<br><br>The only other difference that I can think of is that I am using my DB with the cer ped corrections. But this DB was "diffed" with the current DB and all files are the same with the exception of the altered BB.cer file.<br>
<br>Any suggestions on what may be causing this? Could the mwdc be too tailored to the transversity settings?<br><br><div class="gmail_quote">On Tue, Mar 23, 2010 at 10:46 AM, Brad Sawatzky <<a href="mailto:brads@jlab.org">brads@jlab.org</a>> wrote:<br>
<blockquote class="gmail_quote"><div class="im">On Mon, 22 Mar 2010, <a href="mailto:posik@jlab.org">posik@jlab.org</a> wrote:<br>
<br>
> I also wanted to see what the un-prescaled t2 and t6 look like<br>
> (t2vst6.png) where T2 is the y-axis and T6 is the x-axis. I also tried<br>
> to plot the variable DBB.l1a , but I just get a white canvas and zero<br>
> entries. I was wondering is this because DBB.l1a is an un-prescaled<br>
> variable and the l1a triggeres only for prescaled triggers? Or is this<br>
> a crate map type error? There is also a variable called DBB.f1l1a<br>
> which I assume is the l1a going to f1 TDC?<br>
<br>
</div>The L1A *is* the trigger -- if you read out an event, then there was an<br>
L1A. (The L1A is always after prescaling, but that doesn't matter<br>
here).<br>
<div class="im"><br>
> I am a little confused on how to actually go about correcting for<br>
> this time walk effect. Do I apply corrections to the t2 vs TDC or do<br>
> I really want to correct the t2 vs t6 since t2 is our primary<br>
> trigger?<br>
<br>
</div>A hit in a TDC is the time difference between the trigger and the<br>
individual hit coming into the TDC. For example:<br>
dT = T_hit - Trigger<br>
For our "standard" events, the trigger is T2, so<br>
dT = T_hit - T2<br>
However, we also have a class of events where we get a T2 and a T6, but<br>
the T6 carries the timing (due prescaling and the way the Cerenkov is<br>
ANDed with the T6 to form T2). For this case you have<br>
dT = T_hit - T6<br>
You want your histogram to always reflect the dT between the hit and T2<br>
so you can do this<br>
dT = T_hit - T6 + (T2 - T6) + const<br>
where (T2 - T6) is just DBB.t2. The 'const' is the value of the self<br>
timing peak in DBB.t2<br>
<div class="im"><br>
> Also I am a bit concerned with ~95% of my statistics being lost with<br>
> a one track cut(BB.tr.n==1). Could this be a problem with the optics<br>
> or mwdc data files? Diana are you also seeing a large decrease in<br>
> statistics with this cut?<br>
<br>
</div>You had this problem before -- are you certain you're using the standard<br>
analyzer build? (ie. Environment variables are all correct?)<br>
<br>
-- Brad<br>
<font color="#888888"><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>
</font><div><div></div><div class="h5">_______________________________________________<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>