-
Notifications
You must be signed in to change notification settings - Fork 6
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
Running Count plan against i22 F-Switch gives KeyError #536
Comments
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
joeshannon
added a commit
that referenced
this issue
May 21, 2024
This must be implemented to allow the device to be used in plans. Add a simple test to ensure the count plan runs successfully. Fixes #536.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In testing on i22 on 14/05/24, when the Count plan was run via BlueAPI against the F-Switch device the the following error was reported:
KeyError: number_of_lenses
presumably indicating that there was no corrensponding entry in the device attributes for number_of_lenses
The test was run via BlueAPI but ought to be reproducable using just a command line Bluesky/Ophyd-Async environment
Acceptance Criteria
The text was updated successfully, but these errors were encountered: