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

    User name R. Michaels

    Log entry time 11:25:31 on February14,2011

    Entry number 346857

    Followups:

    keyword=script failure investigation

    At the moment, I CANNOT reproduce the script failure for
    start-run and end-run !! I did 12 runs 1320 - 1331.

    This may be related to the fact that we don't get events
    now, because of cabling issues in the hall (halog 346817).

    I'm speculating wildly here; maybe the new JAVA GUI gets too busy
    when there are events, so it fails to run "asynchronous" jobs ?
    Needless to say, I'm passing this info to the DAQ group.

    Also, each time I end a run (with zero events), the EB
    segmenation faults. So I need to start by hand for the next run.
    (This may be due to the fact that we don't get any events,
    but I suspect it's a DIFFERENT problem; of course no code should
    ever seg fault. Maybe exit with an error ?)

    FYI, to restart EB:

    coda_eb_rc3 -i -s BigBite -n EB2 -t CDEB

    ------ Appendix -----

    Info about what the scripts produce

    In ~a-onl/epics/runfiles there should be five files created by
    the scripts. Here is a normal run 1320:

    (i) At start of run
    Start_of_Run_1320.epic
    halog_1320.epics ... (10 sec delay after the above)

    (ii) At end of run
    End_of_Run_1320.epics
    halog_com_1320.epics
    halog_end_1320.epics ... (10 sec delay after previous 2)

    A failure of the scripts will result in one or more of these
    files not existing for the given run, and typically a missing
    halog entry.