Added code to deal with extra "expver" dimension in ERA5T files #11
Conversation
This file contains 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.
For data < 3 months, some variables have en extra dimension "expver" that indicates which data are from ERA5 and from ERA5T (the latter will need to be updated with consolidated data). The code was failing due to this extra dimension, the atmospheric variable having double the size of the original one. When the dimension "expver" exists, the added code merges the ERA5 and ERA5T datasets and add a note in the attributes of the file.
This version of the code also comments out the line verbose: self.config_ecmwf.debug in the file ECMWF_tools.py to avoid the "False is not of type string" error, as suggested by @crargr in issue #10