-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix time indexer encoder and parser in fitting standardized index and… #1843
Conversation
Welcome, new contributor! It appears that this is your first Pull Request. To give credit where it's due, we ask that you add your information to the
Please make sure you've read our contributing guide. We look forward to reviewing your Pull Request shortly ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks excellent! Thanks a lot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I think of it, was there a need for using jsonpickle
instead of the builtin json
?
jsonpickle
is a dependency in xclim because of some stuff in sdba
where json
can't do the job. When the plan of taking sdba
out of xclim is executed, we'll want to remove unneeded dependencies.
Co-authored-by: Pascal Bourgault <[email protected]>
Thank you for pointing out. I believe |
Warning This Pull Request is coming from a fork and must be manually tagged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved again, thanks!
Pull Request Checklist:
number
) and pull request (:pull:number
) has been addedWhat kind of change does this PR introduce?
Fix the encoder and parser for the time indexer in the
xc.indices.stats.standardized_index_fit_params
andxc.indices.stats.standardized_index
to allow no indexer, non-array indexers, and multiple indexers.Does this PR introduce a breaking change?
No. But the new parser is not compatible with the previous as the format of params.attrs["time_indexer"] is different. If any saved
params
from previous version were reloaded, it may lead to errors.Other information: