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.

Sign up for GitHub

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

Jump to bottom

FAQ: how to write new support for existing EPICS control(s) #297

Open

prjemian opened this issue Apr 19, 2024 · 1 comment

Contributor

prjemian commented Apr 19, 2024

Might be good to start this as a FAQ.

Originally posted by @prjemian in #42 (comment)

Contributor Author

prjemian commented Apr 19, 2024

The usual practice to implement new Bluesky (ophyd) support for existing EPICS controls is to start with:

discuss with beam line staff that use the control(s)
GUI screen(s)
existing programmatic support (such as SPEC)
EPICS database(s)
documentation

Bluesky support should be a thin layer on top of the EPICS support. Additional code to correct problems or add capabilities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment