• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name choi

    Log entry time 19:57:22 on January26,2003

    Entry number 93488

    This entry is a followup to: 93358

    keyword=Synchronization problem between ROC3 and ROC10?

    I spent a little more time to investigate the problem: disagreement of trigger type between ROC3 and ROC10. It seems that after several "synchronization problem", there is some delay between the trigger types from ROC3 and ROC10. Anyway, the mismatch goes to the end of run for runs 20548 and 20549 and I am not sure if we can recover them later. Alexandre reported numerous "synchronization problem" message from elastic data and large number of helicity 0 events. I have just checked two elastic runs 20194 and 1194. Run 1194 generates numerous "synchronization problem", but the trigger type from the two ROC's agree perfectly. Run 20194 has no "synchronization problem" message during espace replay and the two trigger types agree perfectly. So the conclusion is that mismatch of trigger type is related to "synchronization problem", but not always. Anyway, after switching to unbuffered mode for left DAQ, we had not seen any such problems yet. We will wait definitive answer from Bob Michaels when he comes back.