Skip to content

Add sipe instrument diagram#175

Merged
patricklatimer merged 3 commits into
mainfrom
add-sipe-instrument-diagram
Jun 16, 2026
Merged

Add sipe instrument diagram#175
patricklatimer merged 3 commits into
mainfrom
add-sipe-instrument-diagram

Conversation

@patricklatimer

@patricklatimer patricklatimer commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

@arielleleon

Copy link
Copy Markdown
Collaborator

@patricklatimer - are data gathered from LIMS meant to be specific to specimen (specimen information plus task information) and the config from config storage is meant to be for hardware? If that's the case, what do you think about calling that out?

Should the Analysis Workflow instead be called "Staging and Pre-processing"? The actual analysis happens further downstream but directly after acquisition, the data should be staged to move plus with the option to run any preprocessing through aind-data-transfer-service

@patricklatimer

Copy link
Copy Markdown
Contributor Author

@patricklatimer - are data gathered from LIMS meant to be specific to specimen (specimen information plus task information) and the config from config storage is meant to be for hardware? If that's the case, what do you think about calling that out?

Good call, that would be a good thing to clarify.

Should the Analysis Workflow instead be called "Staging and Pre-processing"? The actual analysis happens further downstream but directly after acquisition, the data should be staged to move plus with the option to run any preprocessing through aind-data-transfer-service

What if I renamed it to "Processing and Analysis" and "Long-Term Storage"? I was intending to encompass all the downstream stuff in the "Analysis Infrastructure" box, as it isn't this diagram's job to opine about what happens to the data off-rig.

@arielleleon

Copy link
Copy Markdown
Collaborator

@patricklatimer - are data gathered from LIMS meant to be specific to specimen (specimen information plus task information) and the config from config storage is meant to be for hardware? If that's the case, what do you think about calling that out?

Good call, that would be a good thing to clarify.

Should the Analysis Workflow instead be called "Staging and Pre-processing"? The actual analysis happens further downstream but directly after acquisition, the data should be staged to move plus with the option to run any preprocessing through aind-data-transfer-service

What if I renamed it to "Processing and Analysis" and "Long-Term Storage"? I was intending to encompass all the downstream stuff in the "Analysis Infrastructure" box, as it isn't this diagram's job to opine about what happens to the data off-rig.

On the second comment, that sounds good to me. I will go ahead and approve now

@patricklatimer patricklatimer merged commit 342c974 into main Jun 16, 2026
1 check passed
@patricklatimer patricklatimer deleted the add-sipe-instrument-diagram branch June 16, 2026 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants