Approximately 1000 commits since v0.2 have evolved oemof, so that now is the time for a new major “development” release . In the meantime, the number of contributors has almost doubled (to 26). The mix of experienced and new developers helped to further improve structure and documentation.
Highlights
- Improved reliability: Test coverage has significantly increased, especially for the core modules that have been around since the start.
- Improved storage: The
GenericStoragehas gone through major revisions. The API has been refined to make it more intuitive. Further, it can be used unbalanced now which means that the level at the end could be different to the level at the beginning of the modeled time period. See the storage documentation for more details. - Improved
OffsetTransformer: It is now well tested and documented, so it is now as a regular oemof.solph component. - Improved looping: It is now possible to model just one time step. This is important for time step based models and all other models with an outer loop (Issue #519).
- Improved
NonConvexFlow: It can now haveactivity_costs,maximum_startups, andmaximum_shutdowns. This helps, to model e.g. terms of maintannace contracts for small CHP plants. - Improved documentation: The template for docstrings with equations (docstring of block classes) has been reworked. This also lead to significant advances of the documentation.
(See the Whats new section of the documentation for the complete changelog.)
Update
You need to adapt your application if you update from a previous version. To update oemof you can use pypi:
pip install oemof --upgrade
The new examples will help you to understand the changes. Use the user forum if you have problems with the adaption of your applications.