Jann Launer

Results 37 issues of Jann Launer

This PR fixes #816 by introducing a new constraint that allows to set flows or the sum of groups of flows equal or proportional by a constant factor. The new...

Adds a new constraint to the solph.constraints module which allows to define an "idle time" for a flow (flow2) depending on another flow (flow1), i.e. a number of timesteps that...

enhancement

There is a constraint `equate_variables` in `oemof.solph.constraints` that allows to equate two variables or set them proportional with a factor. However, this does not work for flows, which are time-indexed....

enhancement
feedback wanted
oemof-solph

The new feature (added in #668) is not tested anywhere yet. Please add one ore more tests. @c-koehl, @oemof/oemof-solph

help wanted

This issue is related to tespy's https://github.com/oemof/tespy/issues/87 1. Check for a consistent structure 2. update old information, repair broken links and fix errors, 3. fill a glossary. We aim to...

documentation

It would be useful to be able to set parameters of components of an energysystem not only upon initialisation, but also as part of an existing energysystem. Use cases are...

question
feedback wanted
API

@FranziPl and @jnnr have extended the docu on GenericCHP and ExtractionTurbineCHP. The aim was the following: * show the constraints of the components in the [oemof-solph](https://oemof.readthedocs.io/en/stable/oemof_solph.html#) part of the docu...

help wanted
feedback wanted
documentation

The docstring seems inconsistent. Shouldn't it be `om.GenericInvestmentStorageBlock.capacity` and `om.GenericInvestmentStorageBlock.invest?` > **The following variables are created:** > > capacity :attr:`om.InvestmentStorage.capacity[n, t]` > Level of the storage (indexed by STORAGES and...

documentation

I think that busses should have the attribute "carrier" describing what energy form or resource is flowing. Until now, busses only have the attribute "label", which serves both as unique...

Other than variables, which will be documented in the math yaml-files (and can then be rendered in the docs), parameters are nowhere defined or described. What can be done about...

v0.6