[d2n-analysis-talk] Database Trigger 3 Issue

[Brad Sawatzky]

On Tue, 27 Apr 2010, David Flay wrote:

> So, according to my search, I believe this issue covers runs 20060 -
> 20129, with 20135 being the first working run (DL.bit3 has a histo). 
> There are a lot of junk runs, and hence no info for 20130-20134...
> 
> That would then cover DB directories 20090205 - 20090210, with the trigger
> bit3 working for 20090211...

What does the underlying TDC histogram look like?  Is it just that
channel, or all channels on that TDC?

It seems unlikely that no one noticed this problem during the online
replay.  It really shouldn't "come and go" without there being some
halog entry.  The apparent lack of such documentation suggests to me
that this is a software problem.  Have you definitively confirm that the
analyzer is picking up the db file you think it's getting?  (Ex.  Make
some huge change or corrupt the relevant DB files one by one and make
sure that the analyze sees the change.)

If those data really are missing, I believe we had the same information
fanned out into one of the F1 TDCs.  You could look into that too.

-- Brad

-- 
Brad Sawatzky, PhD <brads at jlab.org>  -<>-  Jefferson Lab / Hall C / C111
Ph: 757-269-5947  -<>-  Fax: 757-269-5235  -<>- Pager: brads-page at jlab.org
The most exciting phrase to hear in science, the one that heralds new
  discoveries, is not "Eureka!" but "That's funny..."   -- Isaac Asimov