Fix time weights support for different in NCL function time_operations #1956
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.
The NCL function time_operations (statistics.ncl) optionally calculates weights based on the number of days per month for time averaging. In the current implementation, a possibly present calendar attribute is not taken into account when calculating the number of days per month potentially giving the wrong number of days in case of a leap year. This has now been fixed by preserving the calendar attribute (if present).
Closes #1946
Checklist for technical review
Automated checks pass, status can be seen below the pull request:
Detailslink to find out why.Detailslink to see it.Checklist for scientific review
New or updated recipe/diagnostic:
@esmvalbotwithout any modifications to the recipe and with all data specified in the recipe