Improve support for obs4MIPs CMORization #3960
Draft
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
Improve support for CMORizing data for obs4MIPs
Using a more recent version of the obs4MIPs CMOR tables than what is shipped with ESMValCore is recommended. If information is missing, the tables will need to be updated before running the CMORizer.
To make this work I had to fix some formatting issues in the file Tables/obs4MIPs_coordinate-ERA5levs.json.
Note: I tried to use the required global attributes from https://github.com/PCMDI/obs4MIPs-cmor-tables/blob/94d38431fbf3f9ad9e722cdaf8aab6050a440aa0/obs4MIPs_required_global_attributes.json, but they are not up to date with the specification.
Example configuration file modelled after the obs4MIPs ESA CCI SST dataset (using our script for reformatting a newer version of the same dataset):
which works with our ESA CCI SST CMORizer after minor modifications (click details to see the changes).
Example output
TODO:
Add tests
Update documentation/add instructions on how to CMORize obs4MIPs dataset
Closes #issue_number
Link to documentation:
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
To help with the number of pull requests: