Skip to content
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

Move functionality to oemof.tabular #75

Open
jnnr opened this issue Oct 12, 2022 · 1 comment
Open

Move functionality to oemof.tabular #75

jnnr opened this issue Oct 12, 2022 · 1 comment
Milestone

Comments

@jnnr
Copy link
Collaborator

jnnr commented Oct 12, 2022

The generic functionality here can move step-by-step to oemof.tabular. If most or all can be moved, this would make maintenance easier.

These can be addressed one after the other:

These belong together

  • DataFramepackage class
  • Define schemas for tabular data packages that describe energy systems in facade_attrs and the available components and busses in component_attrs.yml and busses.yml
  • Setup datapackages by passing the lists of regions, links, busses and components to EnergyDataPackage.setup_default. Custom-defined busses and components can be passed as dictionaries bus_attrs_update and component_attrs_update.
  • Parametrize the EnergyDataPackage with EnergyDataPackage.parametrize
  • stacking, unstacking
  • sensitivity

This could be checked, too:

  • Infer metadata (mainly done by oemof.tabular already, but maybe there are some extra features that can improve tabular).
@jnnr jnnr added this to the Someday milestone Nov 14, 2022
@jnnr
Copy link
Collaborator Author

jnnr commented Dec 13, 2022

Remember to clean up oemoflex: Remove functionality that has been moved or is not used any more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant