-
Notifications
You must be signed in to change notification settings - Fork 1
Long scans definition #57
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
Comments
this might be useful |
running into double nested flat-array-non-unique-keys issue - unsure how to approach |
yeah need to just fix it debugging closely the variable state |
from discussion with @iain-hall - replicating the GDA- conforming is not the expedient thing to do, yet the idea of a modifiable parameter is good. this could be made to do this for blueapi scan parameters |
we could hard-code spectroscopy scan parameters schemas and then create the scans. What is the scan type that is usually done with gda-long-scan spreadsheet view? if we make the equivalent for blueapi then we can make it looooooooong next @iain-hall please help with this, we could write a plan into https://github.com/DiamondLightSource/spectroscopy-bluesky to do this |
from discussion: many different scans can be inside the spreadsheet view: xanes, qexads, xafs. Different kinds of scans can be written inside one bluesky plan for the future really. |
the answer for now seems to not do those long scans on the UI level, as that logic can be on the plan level, and the syntax and support is better there. We don't want to put much custom logic into the queue system. |
GH copy for the issue
https://jira.diamond.ac.uk/browse/K14-24
The text was updated successfully, but these errors were encountered: