Pierre Francois

Discussion with @p-snft , @joroeder , @sasa821 : there should not be InvestFlow, NonConvexFlow, NonConvexInvestFlow but just one Flow class and depending on the argument the user provides, the Flow...

To define a nonconvex and investment flow ``` solph.flows.Flow( nominal_value=None, variable_costs=..., min=, max=, investment=solph.Investment( ep_costs=..., maximum=..., # need to have maximum provided here ) ) ``` Another alternative ``` solph.flows.Flow(...

The nested structure seems to be the preferred way. I would also vote in favor of it. What I like is that the user doesn't have to know in advance...

The DarkThemeProvider doesn't have an `id`, so one technically cannot write a callback with it

I agree, and maybe we should also rename it "PushButton" (with backward compatibility) before creating too many apps?

> Are there any changes so far about its implementation? @gitfeldhase - not that I know of, maybe it was discussed in the latest [oemof dev meeting](https://github.com/oemof/oemof/wiki/Meeting-2022.11)

Some people at Reiner Lemoine Institut tried using oemof with HIGHS and it was successful some of the examples. What they did was to install HIGHS with ```pip install highspy```...

I came across this repository via the pyvideo from 2016 and I used it (not fully, though for lack of time) to improve this readme https://github.com/open-plan-tool/simulation-server Thanks for going through...

@MGlauer, @johannwagner - What about the work done in #391 ?

@wingechr, @gnn wouldn't you be able to do that in no time :)