After oemof v0.3.2, we decided to make oemof’s structure more clear: Both, the framework (including e.g. TESPy) and the Package for energy system optimisation (using solph) were called the same – oemof. With the release of v0.4.0, there are now split packages for oemof.solph, oemof.network, and oemof.tools.
Highlights
- Improved storage: The
GenericStorage
now allows forfixed_losses
, that are independent from the currentstorage_content
. - Having a non equidistant time index is now allowed.
- User warnings help to identify possible flaws in the energy system.
(See the the changelog in the documentation more information.)
API changes
- Change the import of oemof-solph due to unbundling oemof solph
The import statements have changed, for examplefrom outputlib.views import processing
–>from oemof.solph import processing
. There are further changes for the modulesviews
,helpers
,economics
,logger
,network
. - Rename the flow attribute “actual_value“ to “fix“
The attributeactual_value=time_series
was only considere, when a second attributefixed=True
was set. To make this more user-friendly, we adjusted this tofix=time_series
. This is also coherent with the attributesmin
andmax
. - Rename GenericStorage attributes
- The attribute
capacity
of the GenericStorage describing the current absolute stored energy/material/water etc. has been renamed tostorage_content
. In the GenericStorageBlock and GenericInvestmentStorageBlock, the attributeinit_cap
has been renamedinit_content
. This change is intended to avoid confusion withnominal_storage_capacity
or capacity in terms of installed capacity.
- The attribute
Update
You need to adapt your application if you update from a previous version. To update, you can use pypi:
pip uninstall oemof
pip install oemof.solph
The new examples will help you to understand the changes. Use the user forum if you have problems with the adaption of your applications.