fix: add scda to ecmwf matches, add backfill dataset definition #355
+36
−1
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.
Description
We're fixing two issues:
matchesexpression that didn't includescda. This corresponds with the most recentscdaitem, which is2023-07-01 12:00:00+00:00ifsto its data path, to differentiate from its AI-generatedaifsproduct1.The fix is two-part:
scdaback to ourmatches, so any ingests for paths after mid-February 2024 should now pick upscdaassetsdataset-scda-backfill.yamldataset definition that has the old path structureType of change
Please delete options that are not relevant.
How Has This Been Tested?
I haven't tested the ingest workflows yet, I'll wait for an initial review before firing them off. We'll want to run the backfill one starting from 30 June 2023, and the main one from 01 February 2024.
Script to get the latest dates for each stream:
Checklist:
Please delete options that are not relevant.
Footnotes
https://confluence.ecmwf.int/display/DAC/ECMWF+open+data:+real-time+forecasts+from+IFS+and+AIFS ↩