You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some beamlines with multiple endstations share hardware in the experiment hutch, with the device moving between them. This is easily handled with the @skip_device decorator to temporarily disable the device while it is not present.
However, other components (such as some optical components) are present for both endstations, will need to be read by both beamlines, and may need to be partially/wholly controlled by one/both during the course of a visit.
Options:
ReadOnly version of device for non-controlling branch?
ReadOnly signal when device instantiated on non-controlling branch?
Push handling to AuthZ service?
Good faith?
Acceptance Criteria
A pattern has been decided upon and documented for how to manage shared devices.
The text was updated successfully, but these errors were encountered:
Some beamlines with multiple endstations share hardware in the experiment hutch, with the device moving between them. This is easily handled with the @skip_device decorator to temporarily disable the device while it is not present.
However, other components (such as some optical components) are present for both endstations, will need to be read by both beamlines, and may need to be partially/wholly controlled by one/both during the course of a visit.
Options:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: