-
Notifications
You must be signed in to change notification settings - Fork 8
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
Write an ophyd-async device against the fastcs eiger #700
Comments
|
Gary successfully tested with
|
From discussion with Gary:
|
This was referenced Aug 19, 2024
Initial MVP completed in bluesky/ophyd-async#528. A number of spin off issues were made https://github.com/bluesky/ophyd-async/issues?q=is%3Aissue+is%3Aopen+eiger. I'm going to leave this issue here to track it from the downstream perspective but waiting on others to do bluesky/ophyd-async#405 and bluesky/ophyd-async#551 before continuing the work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We would like to move the
eiger
on to the newfastcs
version as well as move our device support toophd_async
. We should do both of these at the same time. You can run a simulatedfastcs
eiger and odin by running (in separate terminals):Local Eiger dev deployment:
Make sure you've done https://dev-portal.diamond.ac.uk/guide/containers/tutorials/podman/#enable-use-of-vscode-features
Odin deployment + tickit sim
Eiger IOC
Odin IOC
UI
Additionally, there is already an eigerIOC running on i04 at
BL04I-EA-EIGER-02:
, see https://diamondlightsource.slack.com/archives/C0176UKVBCK/p1721376023655459i03 does not yet have the new eiger so we will need the old one around for a while still
Acceptance Criteria
ophyd
deviceWe changeThis might be hard as it doesn't have the odin IOC there yeti04.py
to use this anddodal connect i04
still passesThe text was updated successfully, but these errors were encountered: