Tancredi-
I have been putting some time into trying to figure out why the timing
offsets have seemingly shifted. OK well I have given up trying to figure
that out and am now only trying to rectify the problem. I have been
crunching all the H2 data through run 801 using three different calib
files. (Again these ntuples are being sent to "anothercrunchdir" so
as not to corrupt the real analysis directory - as you know there is also
a seperate directory set up for separate Blast_Params) The three calib
files are based on:
1) zero offsets
2) offsets from run 1326 flasher (i.e. post-CFD delays = 2ns)
3) offsets from the actual H2 data
Anyway, it seems that the best position results come from using the real
data (please see that the attached plot) I do not necessarily think that
this means that we can not use the flasher for determining offsets I just
I am not sure about how the run conditions for flasher vs real data varied
in this dataset. I still need to verify ttl-ttr:ttr-ttl but there is a
small problem here (in test macro or elsewhere) on which I am
stil working. Yes this is WAY overdue for a solution! Dealing with these
offsets is getting, as we say, a little long in the tooth!
Working on BATS tomorrow with Ben
but I will be around to speak
about this,
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