Write L2 to file and leave all additional variable derivation for the L2toL3 step #251
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.
The idea of this new version is that:
L2 data files are written into
level_2/raw
andlevel_2/tx
folders by get_l2 (just like it was done for the L3 data previously). One consequence is that this low-latency level 2tx
data can be posted very fast on THREDDS for showcase and fieldwork, and processed into BUFR files.L2
tx
andraw
files are merged using join_l2 (just like it was done for the L3 data previously). Resampling to hourly, daily, monthly values are done here, but could be left for a later stage.get_l3 is now a script that loads the merged L2 file, run
process.L2toL3.toL3
. This will allow more variables to be derived intoL3
and historical data to be appended once the L3 data is processed.