• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name R. Michaels

    Log entry time 11:25:15 on March 6,2006

    Entry number 165493

    keyword=T9 re-installed / ROC reboots / add helicity clock

    I made an access and re-plugged in T9. It looks like my fault (groan)
    and was unplugged since Thurs night's work when I was trying to
    understand the so-called helicity loss. Sorry !!!!!

    I rebooted ROC3 & ROC4 per S. Wood's request.

    I also put in some optional debug flags to the SIS3801 server to
    diagnose its state when it is failing to update the online packaged
    data. The printouts happen once per 2 sec and won't cause harm,
    plus easy to turn off at vxWorks command line.

    Finally, I added a 2nd clock to the TS crate where helicity info
    is read. It goes into the 18th channel (hence a different chip
    set, to hopefully avoid bit errors) and appears in the datastream
    now as 8th word after the header 0xfabc0007. To reduce confusion
    I decided not to change this header. Note, there are also clocks
    in each crate, hence we can probably reduce to zero the bad helicity
    errors in GenHelicity by using a majority opinion of time to clean
    up the scaler bit errors (sympton is QRT "appears" to jump in time).