DAQInterface should treat process Error states the same as process crashes
Right now, in direct process management mode, if a process crashes (goes away) then DAQInterface will simply print a warning and continue running. However, if a process returns "Error" when queried (as happens when a fragment generator throws an exception), DAQInterface will initiate the recovery sequence, stopping the run. An "Error" state should be treated the same as a crash - i.e., it should only print a warning by default.
#1 Updated by John Freeman almost 2 years ago
- % Done changed from 0 to 100
- Status changed from New to Resolved
This is handled by commit d64f2b9df69524dd72b5047e8dfa59d008770bf1 on the develop branch. In the event that a process, when queried, returns "Error", then rather than shutting down the run and returning itself to the "Stopped" state, DAQInterface will instead print a warning and remove the process from its list of processes to query. Also, if we have $DAQINTERFACE_PROCESS_MANAGEMENT_METHOD == "direct" rather than "pmt", DAQInterface will kill off the process; it doesn't do this in the pmt case because that would bring down the entire run.