Skip to content

FIX: closes bdaq after exception in the scan init

Konstantin Mauer requested to merge close_bdaq_on_exception into development

When a exception happens during initialization of a scan, (e.g. no aurora sync) the bdaq object does not get closed properly. In particular, the sockets stay open and no new connection to the readout board can be established after catching the exception.

Merge request reports