Update name of ARCO ERA5 dataset#93
Merged
tennlee merged 2 commits intoACCESS-Community-Hub:developfrom Apr 8, 2025
Merged
Conversation
Pull Request Test Coverage Report for Build 14325052955Details
💛 - Coveralls |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, the name ERA5 was used to refer to the data accessor for the ARCO-based ERA5 dataset. The name ERA5 is ambiguous and could have referred to any of the ERA5-derived datasets, such as:
ERA5 Low Resolution (from WeatherBench).
ERA5 Full Resolution (from a local on-disk replication).
ERA5 Full Resolution (from the ARCO cloud-based source).
This made it unclear which specific dataset or source was being accessed when using ERA5. Now ERA5_ARCO is used explicitly to indicate that this data accessor refers to the ARCO ERA5 dataset.
Closes #28