You can try to set <MidasOnlineCommunicationThread>to be true in your config XML file.
By doing it, the communication with the midas system will be done in a dedicated thread so it runs independently
of analysis tasks.
> I'm running ROME+Argus as an online analyzer and display for a MIDAS DAQ system.
> In our set up there is generally a few seconds between MIDAS runs. ROME
> handles the first run just fine, but always crashes when runs are taken in quick
> succession like this. When running in a slower mode, letting ROME finish
> whatever run of end task exist, the online analyzer does not have this problem.
> I've suppressed writing all output files while in the online mode and I don't
> have any end of run operations in any of the tasks. What is happening at the
> end of running that is causing ROME to crash?
> Thanks for any help.