ZI: Adds the reacquire acquisition step in the instrument coordinator

Kelvin Lohrequested to merge
zi_reacquire_acquisition into develop

Explanation of changes

This is one of the trickier implementations for the ZI backend. As we use the LabOne server to communicate and retrieve acquisitions, there are cases when the acquisition call has timed out. When that happens, LabOne just spits out the last successful acquisition without any warning to the user. Hence, we need to restart the entire instrument coordinator to retrieve the acquisition again whilst checking if we got a duplicated result.

Merge checklist

See also merge request guidelines

  • Merge request has been reviewed and approved by a project maintainer.
  • Merge request contains a clear description of the proposed changes and the issue it addresses.
  • Merge request made onto appropriate branch (develop for most MRs).
  • New code is fully tested.
  • New code is documented and docstrings use numpydoc format.
  • CHANGELOG.rst and AUTHORS.rst have been updated (when applicable).
  • CI pipelines pass
    • black code-formatting passes (gitlab-ci),
    • test suite passes (gitlab-ci),
    • no degradation in code-coverage (codacy),
    • no (serious) new pylint code quality issues introduced (codacy),
    • documentation builds successfully (CI and readthedocs),
    • windows tests pass (manually triggered by maintainers before merging).

For reference, the issues workflow is described in the contribution guidelines.

Edited by Kelvin Loh

Merge request reports