Log entry time 21:51:14 on July 08, 2010

Entry number 330891

This entry is a followup to: 330872

FYI, inspection of the source code of the THaDecData ("D") module shows
that a cut like D.evtype==1 is identical to fEvtHdr.fEvtType==1. (Both
variables are filled with the CODA event type straight from the CODA
event header.) As Bob explained in halog# 330820, use of this variable is
discouraged, and one should use D.evtypebits instead.

Then again, if I read Bob correctly, D.evtype==1 should be identical to
D.evtypebits==0x01. If there is only a T1 at the TS, then the eventtype
is 1, and if there is a T1 coincident with any other trigger, then
eventtype is 5 (which unfortunately is not a coincidence trigger in this
experiment). Thus, D.evtype==1 demands T1 with no other trigger present.

So perhaps the word should be, "do not check fEvtHdr.fEvtType==5"?