NDAttributes for Xspress detectors #340
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ead of individual mongo/tiled callbacks.
canismarko
added
device support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Area detectors can add attributes to the HDF5 file. This PR lets bluesky/ophyd-async read the attributes from the IOC and makes them available through Tiled.
During testing, there was a considerable delay when measuring each data point. This was due to the large number of documents generated for the NDAttributes. To work around this, the run engine now uses a kafka publisher by default instead of individual mongo and tiled callbacks.
This PR also changes the Kafka topics available at the beamline, consolidating the individual branch topics (e.g. "s25idc_queueserver") into "haven" and "haven-dev". This means that all mongodb documents are going to end up in the s25idc-microprobe mongo database. This isn't a problem since both branches' databases will be streamed into the new relational database, and if we revert from the relational database back to mongo we'll combine both branches into one database anyway.
Things to do before merging: