Skip to content

Handle exceptions during the S-bit rate scan

Laurent Petre requested to merge bugfix/sbit-rate-error-handling into develop


The exceptions were not caught and handled in the scanning thread (used at the moment only by the S-bit rate scan) leading to an abrupt termination of the whole xDAQ executive if only one of the back-end board was reporting a single error.

This MR aims at catching all exceptions in the scanning thread, avoiding the executive termination, and moving the AMCManager to the Error state with a meaningful error message.

Related Issue

Issue discovered with #166 (closed).

How Has This Been Tested?

Starting an S-bit rate scan, then powering off one chamber. The AMCManager goes to Error with a meaningful error message.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)


  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
Edited by Laurent Petre

Merge request reports