Uwe Krien
Uwe Krien
What about this? Is it solved. I will postpone it to v0.3.1
@jnnr Would be nice if there is something like this within the docstring. Any ideas? The following workaround does not show the function as headline so that the docstring (only!)...
I talk to @jokochems, @p-snft , @gnn and we think that `options` is more common than `flow_kwargs`.
Some of the comments are outdate because the structure changed due to the unbundling but we could keep it open to check if everything is done.
Thanks @simnh Could you open a PR?
In Issue #618 @simnh wrote: > Well I think putting it to solph is possible and putting it to tabular as well. The main thing about the facades is, that...
@simnh answered in Issue #618 that tabular-facades will work in solph directly, too. If the facades are not an exclusive part of tabular I would prefer to have either a...
First we have to define the difference. For me a component is defined in the typical solph way with `inputs={bus1:Flow()}`. If we use facades we do not need this anymore....
I think a more or less basic component could even be part of solph. ```python class HeatPump(Transformer): def __init__(cop, **kwargs): self.cop = cop if kwargs.get('conversion_factors') is not None: raise ValueError('')...
> In my opinion, the goal of facades is to facilitate the creation of networks, so they should be precisely defined and eliminate potential for mistakes. Maybe, they should except...