NEXT
Make New Entry,
Make Followup Entry
User name dalton
Log entry time 10:46:55 on September 10, 2009
Entry number 288913
This entry is a followup to: 288689
keyword=Further monitor saturation complications
It was curious that when BPM 12x was moved over to the 18 bit adc
the
slug summary suddenly stopped including the data as good. It
turns
out that a monitor saturation cut is hardwired into the pair
selector code. If I understand correctly, the monitor saturation
cut is already in the ok_cut, so it is unnecessary at this point.
Anyway, I'll increase this number to 150000 for BPM 12x (and worry
about having a smaller number for earlier periods only if someone
tells me it's necessary.)
Bool_t TaPairSelector::ProcessCut()
{
// Process the cuts for this event.
// PAN Cuts
if(isPanTree) {
if(!ok_cut) return kFALSE;
// BPM saturation cuts
if(doBPMSat_cuts) {
if(evt_bpm12mx[0]>=60000 || evt_bpm12mx[1]>=60000) return kFALSE;
if(evt_bpm4amx[0]>=60000 || evt_bpm4amx[1]>=60000) return kFALSE;
if(evt_bpm4bmx[0]>=60000 || evt_bpm4bmx[1]>=60000) return kFALSE;
}
// if(evt_bmwcyc[0]!=0 || evt_bmwcyc[1]!=0) return kFALSE;
}
return kTRUE;
}
<\pre>
A copy of this log entry has been emailed to: rsholmes@jlab.org, paschke@jlab.org