-
Notifications
You must be signed in to change notification settings - Fork 10
Delete old/redundant outputs #548
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
Conversation
dalonsoa
left a comment
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 changes all make sense, specially because they remove ambiguity.
Remember to mention in the release note for the next release that these outputs are no longer available.
| return _aggregate_sectors(sectors, market_out, op=sector_supply) | ||
|
|
||
|
|
||
| def sector_supply(sector: AbstractSector, market: xr.Dataset, **kwargs) -> pd.DataFrame: |
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.
The infamous sector_supply function, gone for good!
| return _aggregate_sectors(sectors, market_out, op=sectory_supply) | ||
|
|
||
|
|
||
| def sectory_supply( |
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.
What the heck is sectory_supply? I hadn't seen this before...
Deletes outputs that aren't required any more, as discussed in #413
Deleting these because they are known to be unreliable (e.g. #312), and all the relevant data can be created with other global/sector outputs
I advised in the release notes for v1.2.0 that these would eventually be deleted, so nobody should still be using these anyway.
Will save this for v1.3.0 along with #507 #510 and others