ISISComputingGroup / ISISComputingGroup/EPICS-refl
Reflectometry: do not allow compound move to start if any axis not communicating
Open
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
As a scientists i do not want a clash to happen if i start a move of several axes and one of them was not communicating. I would like teh reflectometry server to check that none of the axes in the move are currently in a INVALID alarm status (as might be caused by a communication failure) and then if any are in this state to not do the move
## Acceptance criteria
- moves involving of multiple axes are not actioned by reflectometry server if any of the axes involved are in an INVALID_ALARM state
## notes
probably need ISISComputingGroup/IBEX#8524 doing before can be tested properly
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.