• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name R. Michaels

    Log entry time 14:34:25 on January20,2003

    Entry number 92683

    This entry is a followup to: 92400

    keyword=parity run -- checks

    I did a few brief parity runs (1409, 1410, 1411) to test some things about
    Qasy feedback. Now we are on run 1412 which I intend to let run for many hours.
    I believe Qasy remained small during all that.

    What I found out:
    1. If the feedback software crashes (or ctrl-C) then subsequent connections
    to the ET server fail. The code et_station_create() hangs. No return. Only
    way out is to kcoda and restart runcontrol, as per halog 92400.
    2. Some obscure errors of closing connection to ET are fixed. But these didn't
    matter, as far as I can tell.

    Practical advice
    ============
    ---> Leave a parity run for about 1 shift. It should never fail during a run, but
    do watch the "bird" GUI to verify enabled, etc. (see Kent's note about that).
    ---> Take a look at the log file of parity feedback, like this:
    "tail ~apar/feedback/runlog/ffb_1412.log". If it is growing, all is well.
    ---> We will leave a stable version of the code (the pre-jan-16 version seems ok,
    we're not sure why yet).