Guys-
Here is the latest in the offset saga.
1) I used all d2eep ntuples from run 1348-1799.
2) I defined target ptl/ptr = 0 and ttl/ttr = 1000
I used 1000 instead of 2000 as the peaks we already closer to this.
Of course this is arbitrary and can easily be switched.
3) I defined offsets as follows:
BOT_OFFSET[sect][paddle] = (int)(ttl[paddle]->GetMean() - 1000 +
position[sect][paddle]->GetMean());
TOP_OFFSET[sect][paddle] = (int)(ttl[paddle]->GetMean() - 1000
- position[sect][paddle]->GetMean());
based on the fact that we subtract them in TBLDetRecon.cc and ptl is
defined as bot-top.
4) Looping over paddles I only used the PID cut to grab the proton peak
from deuteron break-up channel:
TString L_cutstring(u+"ntl=="+paddle+" && idl==14 && idr==3");
TString R_cutstring(u+"ntr=="+paddle+" && idr==14 && idl==3");
5) To test this I did NOT recrunch all of these lr ntuples as that would
take forever I just subtracted the offsets in the test macro which plots
ttl/ttr/ptl/ptr.
Please take a look at the attached before and after plots.
***Note: Since the d2eep ntuple does not include filter.h to subtract the
existing offsets in the lr ntuple this was not done from real data. That
is the next step ...
Pete
----------------------------------------------
Pete Karpius
Graduate Research Assistant
Nuclear Physics Group
University of New Hampshire
phone: (603)862-1220
FAX: (603)862-2998
email: karpiusp@einstein.unh.edu
http://pubpages.unh.edu/~pkarpius/homepage.htm
----------------------------------------------
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST