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

Document proposed optics hutch blueAPI architecture #30

Open
DominicOram opened this issue Feb 28, 2025 · 2 comments
Open

Document proposed optics hutch blueAPI architecture #30

DominicOram opened this issue Feb 28, 2025 · 2 comments
Labels
optics This goes into the optics

Comments

@DominicOram
Copy link

The two i19 EHs both use a shared optics hutch. There is a PV that says which hutch is currently controlling the optics. When one hutch is in control the other one should still be able to run plans to test equipment in their experiment hutch but they should not be able to move anything in the optics hutch.

Acceptance Criteria

  • There is an architecture documented that will address this
@DominicOram
Copy link
Author

Initial idea:

Image

@CoePaul
Copy link
Collaborator

CoePaul commented Feb 28, 2025

Yes this diagram matches the initial discussion.
I later asked ( Noemi ) if plans can call / delegate to / subcontrast to other auxiliary plans and I was given a clear answer in the affirmative.
I think going from the initial sketch to the fully fledged result will be easily possible using plans calling other plans as a way to protect symmetry considerations.

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

No branches or pull requests

2 participants