[d2n-analysis-talk] Spike at E/p=0 [SOLVED, but begs a new question]

[Brad Sawatzky]

On Tue, 14 Dec 2010, David Flay wrote:

> So therefore, in the future as we look at E/p one <should> include
> such cuts.
> 
> Would it make more sense to just include these cuts on E/p in the cut
> definition file for the replay?

Please verify that the raw ADC information is zero for these bad events.
By raw, I mean the non-corrected data containing the raw bin value
returned by the 1881 hardware.

I would recommend not placing a hard cut (ie. in the cdef file) on
"high-level" derived variables like this.  There's too great a risk of
hiding some underlying bug/problem/weirdness.

For example, at first glance, that looks like quite a few hits that have
generated a trigger (ie. good hit in two scintillator planes), have a
good track (correct? if not, p should be undefined), and yet don't
deposit anything in either lead-glass layer.  That's kind of strange...

Are the usual EDTM and trigger cuts (ie. no T8 pulser, etc) in place for
these plots?

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