[d2n-analysis-talk] Database Trigger 3 Issue

[Brad Sawatzky]

On Thu, 29 Apr 2010, David Flay wrote:

> On Wed, Apr 28, 2010 at 10:24 AM, Brad Sawatzky <brads at jlab.org> wrote:
> 
> > 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...
[ . . . ]
> Also just found the trigger latch pattern explicitly:
> http://www.jlab.org/~adaq/halog/html/0902_archive/090212164702.html
> 
> Apparently things were 'wrong' then changed to be 'correct' in the time
> frame that I'm looking at...  I'm on the look out for what the trigger
> patterns were before the change (I don't necessarily trust the DB on these
> runs now) -- unless these patterns weren't set correctly in the first place
> and the histograms wouldn't have been filled anyway?

So this sounds like it was just a cratemap error (ie. software problem).
The db_DL.dat file(s) associated with the 'bad' runs needs to be updated
using the info in this halog, then the run needs to be replayed.

-- 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