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

    User name R. Michaels

    Log entry time 17:48:05 on April23,2009

    Entry number 267600

    keyword=TS scaler crate data format

    Someone asked where the TIR data was on R-HRS.

    Short answer: It's the 2nd word in the crate.
    Still, the data needs to be checked.
    All I can say now is some bits are flipping.

    Long answer:
    Below is a typical event from ROC10. (ROC11 format is identical.)
    Recall, ROC10 = R-HRS TS crate. ROC11 = L-HRS TS crate

    0x00000002   0x00000fc0   0x00003b38   0x00122864   0x000014fe
    0x00000032   0xcafe0000   0x0001090f   0x00021ee8   0x0001090f
    0x00021f14   0x0001090f   0x00021f7a   0x0002121c   0x00032ddb
    0x00007003   0x0000aba6   0xfb0b0000

    The 1st word = event type (here it's 2)

    2nd word = TIR data = 0xfc0 here
    The target, helicity, etc should go into this module.
    I suggest it's best (less confusing) if it were done
    the same as on L-HRS (halog 246618 on Nov 4, 2008).

    3rd word = a counter (ramps to 20,000 then resets to 0)
    4th = vxWorks time (1 bit = 16.67 msec)
    5th = Time, I think it's 103.7 kHz (need to check)
    6th = CODA event number
    7th = 0xcafe0000 = Header to mark start of scalers

    The next 10 words are scalers.
    5 scalers are read, 2 channels each
    These are the norm scalers and 2 BCMs, u3 and d3.
    These should be checked.

    Then, following this is usually 0xfb0b0000 -- a flag
    marking the end.

    However, every synch event -- or every 100 events if
    unbuffered -- you get a full readout of all channels
    of all 5 normalization scalers, which is decoded
    in Podd by the THaScaler class. I'll check these
    during the run. They were ok for Bigbite and L-HRS
    during Transversity, and R-HRS was done the same way.