This page describes issues surrounding machine control effects on the 24-7 running feedbacks. The following section lists use cases where action taken by an operator or application effects the performance of the feedbacks. These use cases highlight where some kind of authority must be assigned when the machine state is changed by an operator or application that in turn effects the feedback.
Use cases
- Operator starts a scan application
- the scan application disables conflicting feedbacks before starting scan
- Operator starts a bunch length measurement
- the bunch length measurement application disables conflicting feedbacks before it begins
- Operator puts in a screen
- operator turns off feedback first? or,
- Feedback monitors state of screens and disables itself until it is out again?
- Operator inserts TD11 Stopper
- operator turns off feedback first?, or
- Feedbacks monitor state of TD11 Stopper?
- Operator tries to move an actuator used by feedback
- the IOC controlling the actuator has record processing that does not allow an operator to control a feedback actuator
- Operator moves the chicane, changes a quad setting, does something to the machine to change its 'configuration' enough to effect feedback...? What to do?
Related Issues that may pertain to other applications
- feedbacks want to average measurement data, where data values fall within a feedback specified range (to remove 'flyers' from the data set). edefs do not support user-defined data ranges