• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT
    Make New Entry, Make Followup Entry

    User name Ole Hansen

    Log entry time 14:13:05 on July 09, 2010

    Entry number 331109

    This entry is a followup to: 331095

    keyword=Re: evtypebits

    0x40 is just the hex representation of decimal 64, so there is absolutely
    no difference between the two except for human readbility. (Some folks
    prefer to think hex.)
    BTW, it turns out that D.evtypebits==0x40 is always false for the
    conincidence runs (at least the ones I checked). The reason is simple:
    trigger 6 (-> 0x40 pattern) is the coincidence LS2+RS2+RGC. But there is
    also trigger 4, which is the coincidence LS2+RS2. Hence, if trigger 6 is
    present, trigger 4 is always also present, so the bitpattern is always at
    least 0x40+0x10 = 0x50 (=80 decimal). Therefore, to select trigger 6, use
    D.evtypebits & 0x40 != 0 or D.evtypebits==0x50. (The second form
    disallows other triggers present and hence is a bit cleaner.) 
    Since trigger 6 always means also trigger 4, (almost) all triggers 6 get
    mapped to fEvtHdr.fEvtType==5, per Bob's logic. So yes, this variable is
    ill defined at present.