Fix convert calendar on non-temporal data in datasets #10268
Merged
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.
convert_calendar
adds atime
dimension to all variables #10266whats-new.rst
When calling
convert_calendar
on dataset with non-temporal variable (notime
dimension), thetime
dimension was added. This is because the function was usingwhere(time.notnull(), drop=True)
to drop the time elements of the source that did not map to a valid time in the target calendar.Given that
time
is always 1D and always loaded (no dask), usingsel(time=time.notnull())
fixes the bug, and, in fact, makes more sense to me. (I don't remember why I didn't use that in my first version of the method...)I added a minimal test that detects the bug raised in the issue.