Dear analyzers,
indeed the above may happen (you should hear "oh no !") but it does not
mean that the run is "bad": we just have to be carefull to "cut" up to
the last relevant charge event not to have a pollution of the charge
measurament. This is not too hard to do.
I suggest to put such runs in limbo but if this was mostly a good run
with a problem at the end you should of course to update the (relevant
section of the) RUNLIST anyways. If possible one should try to exit the
run normally. To do this succesfully you have to go through the End section
of the coda run and click away the "end" part of the elog window.
Depending on the crash, you may not do this (end-of-run-fail) but
you can still update the elog for the present run with
ssh -X blast@dblast07 wish ~elog/bin/check_end.tcl
before you start a new one.
-- tancredi
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST