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

    User name Moffit

    Log entry time 17:41:59 on February 19, 2009

    Entry number 262133

    This entry is a followup to: 262131

    keyword=A bit more analysis on the discontinuity...

    Figure 1_pad1: If we look at the syncroc5 (103.7kHz clock) and divide by the scaler reading of the BCM (read EACH event)... there's a jump. This could be the indication of a beam trip... This gap shows us that there's about 3 seconds of downtime (0.325E6 counts / 103.7E3 counts per second).

    Figure 1_pad2: But... we should still be getting 10 counts per second from the T8 pulser (1024 Hz prescaled down to 10Hz) during this beam trip. If I cut on DBB.evtype==8 (should be fine, since it's not very likely that there are T2s or T6s in coincidence), we see the same gap. Where did the T8s go during this time.

    Looks like there are periods of time 3-5 seconds (looking at previous gaps) where the DAQ stops taking data. Maybe this is related to the network saturation that has been observed (Figure 2).

    Figure 1

    Figure 2