Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENH: Support grouping devices #174

Open
tangkong opened this issue Jan 11, 2023 · 0 comments
Open

ENH: Support grouping devices #174

tangkong opened this issue Jan 11, 2023 · 0 comments

Comments

@tangkong
Copy link
Contributor

Expected Behavior

Support devices that are tightly coupled together, and may possibly affect multiple beam paths.

Current Behavior

Currently each device is expected to reside on a single branch, unless it is itself a branching device.

To address this problem, we simply made copies of the offending device and dropped it into each beam path. This made the device visible in all the paths, but the duplicate devices could cause confusion down the line

Possible Solution

Group devices together, and implement veto logic?

Context

Inspired by this ticket, and the case where mec_yag0 was close enough to mr1l4 to block beam for all FEH hutches.

Your Environment

pcds-5.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant