Fix decadal calendar #263
Merged
Fix decadal calendar #263
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
cehbrecht
force-pushed
the
fix-decadal-calendar
branch
from
5c949a8 to
53a82b5
Compare
Merged
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.
Overview
This PR fixes an issue with cmip6-decadal data when both the Gregorian and Proleptic Gregorian calendar are used. The solution is to set Proleptic Gregorian calendar to Gregorian (Standard) which is the same after the year 1582.
Changes:
decadal_fix_calendarfixing function.Related Issue / Discussion
Additional Information
See notebook in rooki:
https://github.com/roocs/rooki/blob/master/notebooks/errors/cds-error-2024-08-28-cmip6-decadal.ipynb