Add more data streaming documentation - ADRs, more hardware architecture. #135
Conversation
This file contains hidden or 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
rerpha
changed the title
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.
This PR adds a few ADRs to the dev wiki under the data streaming section as we have had a very informative talk with DSG and some things have become much clearer.
I am writing this now for HRPD-X so there are some ways we can cut corners ie. not histogramming and no spectra mapping, but this will likely change in the future to support the other instruments that we'll roll data streaming out to.
Please leave any initial comments here, but we will have a proper meeting to discuss - I'll organise this soon.
Closes ISISComputingGroup/DataStreaming#15
Closes ISISComputingGroup/DataStreaming#12
Closes ISISComputingGroup/DataStreaming#7
Closes ISISComputingGroup/DataStreaming#3
ISISComputingGroup/DataStreaming#26
and ISISComputingGroup/DataStreaming#24 should be done before creating any other tickets - we have some of the answers now, but the actual operation of the topics for each of those tickets will be done by those two processes. We should create tickets at the end of prototyping to flesh them out.