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

    User name hyde

    Log entry time 11:05:57 on November30,2010

    Entry number 342056

    keyword=Beginning of run9105 TS livetime

    Livetime at beginning of run 9105
    T->Scan("D.TSscalLive1:D.TSscalLive2:D.HRSsinglesROC17:D.DVCSledClkROC17:D.TSscalEvent:D.Clock104KHzROC17",
    ***********************************************************************************************
    * Row * Instance * D.TSscalL * D.TSscalL * D.HRSsing * D.DVCSled * D.TSscalE * D.Clock10 *
    ***********************************************************************************************
    * 0 * 0 * 1026 * 1156 * 479 * 68 * 1 * 624404 *
    *
    * 1 * 0 * 2960 * 3275 * 479 * 69 * 2 * 625508 *
    * 2 * 0 * 4485 * 4893 * 480 * 69 * 3 * 626416 *
    * 3 * 0 * 4813 * 5261 * 481 * 69 * 4 * 626639 *
    *
    The first event comes a value 624404 of the 103.7 kHz scaler.
    This is 6 seconds into the run
    The second event is a DVCSledClk event (incremented to 69, while HRSsingles stays at 479).
    The elapsed time between first and second event is only 1104 clock counts, or 0.01 sec.
    In the first 6 seconds of the run, before the first event
    the TS scalers increase by 1026 (gated) and 1156 (ungated)
    The TS clock is roughly 200KHz. So TS was enabled 5 msec
    before the first event. This is consistent with a >20 Hz event rate.

    Why do the TS gated and ungated scalers differ?
    Is this just a different read/init time (0.5msec)?
    Or is something inhibiting TS at beginning of run