Handle naming convention change for RRFS files #360
Merged
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.
Note: while modest in its scope, it's my first public contribution so may want to lend extra scrutiny (and apologies for any bad etiquette).
Around 4/19/24, RRFS URL naming convention changed on AWS (directory structure doesn't appear to have changed, just the file names):
conus_3km
toconus
m0x
was added betweendate
andproduct
Changes are confined to
rrfs.py
, where URLs are now generated for all combinations of domain and ensemble member naming conventions. TheSOURCES
dictionary should remain compatible withfind_grib
fromcore.py
, though includes up to 4aws_i
keys.