-
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
Option to output datasets #1625
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
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.
Cool!
Is there a particular reason why we wouldn't want to offer this as a method/call signature of Indicator objects? e.g. some_indicator(..., as_dataset=True)
?
It's simply that I didn't want to add another argument to the indicators, as to now overcrowd the signature with parameters that do not impact the computation itself. But, it could be done easily. |
That's a good point. The workflow example is clear enough, so I don't see any harm from keeping this as an option set via context. The only other way I could see this being implemented (for conventional |
LGTM ... I think the context / set_options mode is a decent compromise |
New black came out. I'll see what can be done. |
Oh! I thought this was a python 3.8 issue... |
FYI: https://github.com/psf/black/releases/tag/24.1.0 Looks like a bunch of breaking changes. I think I'm going to pin |
Pull Request Checklist:
number
) and pull request (:pull:number
) has been addedWhat kind of change does this PR introduce?
as_dataset
. When True, indicators return Datasets instead of DataArrays or tuples thereof.Does this PR introduce a breaking change?
No.
Other information: