Testing: reading raw instrument data #216
Draft
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
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is a first-pass implementation of injecting raw instrument data into the pipeline per #213 .
The
Rawfolder is now split intoRaw-dataloggerandRaw-instrument. The sample AquaTROLL600 file sent by @Fausto2504 is from CRC-W in April 2023. These data do not exist as datalogger data:...but the new
L0-instrument.qmdfile picks up the sample file, restructures it into a datalogger-like L0 file, and passes it on to the next stages.We end up with L1 data that comes from the raw instrument.
I learned a bunch of things doing this that we'll want to think about.