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

    User name R. Michaels

    Log entry time 06:06:27 on March26,2014

    Entry number 387583

    This entry is a followup to: 387581

    keyword=scaler wierdness and DT

    First of all, it seems that the number of events reported is correct.
    I can read the CODA files rapidly with "~a-onl/rwcoda/rwcoda file"
    and the number of triggers agrees.

    Second, it seems that on the L-HRS the T1 rate is approx. 2x the T1 on R-HRS,
    which is odd because these are similarly formed triggers. I suggest looking on
    a scope for double-pulsing on this trigger.

    For example run 1243: reading the file we see

    ~a-onl/rwcoda/rwcoda /adaq1/data1/gmp_1243.dat.0

    CODA file: /adaq1/data1/gmp_1243.dat.0

    Triggered Event Types
    T1 T2 T3 T4 T5 T6 T7 T8 T9 T14
    57538 0 0 0 0 0 0 0 0 0

    Total physics triggers (evtype <= 14) 57538

    Other Event Types
    120 130 131 133 135 136 140
    0 0 1292 1 0 0 1247

    ---------------

    But halog says
    TRIGGER RATES: PRES/REAL
    T1:T1: 7.6/7.6 Hz

    TRIGGER TOTALS: PRES/REAL
    T1:T1: 81456/81456

    which looks wrong -- see my post on the T1 rates just now.

    -----------------------

    Then there is the strange run 1240 for which the reported rate in halog is equal
    to the number of counts. My investigation says that this occurs because the
    run is long (6+ hours) and the clock rate is high (103700 Hz), so the time becomes
    "negative" (signed integer). Need more bits in the number.
    In halla_scaler_process.tcl if time is negative it is reset to 1.
    This does not happen on R-HRS because the clock rate is only 1024 Hz.