Use sdba options for xclim by default #363
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.
Pull Request Checklist:
number
) and pull request (:pull:number
) has been added.What kind of change does this PR introduce?
Instead of setting the options only when calling xclim's
adjust
, we set the options globally at import time.This fixes the subtle issue noted in Ouranosinc/xclim#1674 : the context options are not seen by all code when dask-backed data is used. as the actual computation occurs outside of the context.
It also allows to change these options at run time.
xc.set_options(sdba_encode_cf=False)
will fix #362, for example. This was not possible earlier as the option context was within the function and couldn't be modified by the user.Does this PR introduce a breaking change?
Yes, issue #362 will now occur on dask arrays too, until xclim's PR is merged. But it can be circumvented as shown above.