This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Do not put position
into ispyb for gridscans
#1302
Comments
rtuck99
added a commit
that referenced
this issue
May 21, 2024
rtuck99
added a commit
that referenced
this issue
May 21, 2024
rtuck99
added a commit
that referenced
this issue
May 21, 2024
rtuck99
added a commit
that referenced
this issue
May 21, 2024
rtuck99
added a commit
that referenced
this issue
May 21, 2024
olliesilvester
pushed a commit
to olliesilvester/mx-bluesky
that referenced
this issue
Aug 23, 2024
…/hyperion#1401) * (DiamondLightSource/hyperion#1302) Remove position populate from ispyb callback code * (DiamondLightSource/hyperion#1302) Remove position from external ispyb gridscan parameters * (DiamondLightSource/hyperion#1302) fixes for system tests (WIP) * (DiamondLightSource/hyperion#1302) Remove surplus JSON test file, add position test to rotation ispyb system test * (DiamondLightSource/hyperion#1302) Make pyright happy
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As discussed at https://diamondlightsource.slack.com/archives/C048RD0KFFF/p1712656243118199 we should not put
position
in the database for gridscans as it is in not well defined what that means.Acceptance Criteria
position
into ispybThe text was updated successfully, but these errors were encountered: