Johannes Kochems

Thanks for opening this discussion. In general, I like the idea of having one single Flow class. I don't like putting arguments into a flat argument structure. I think, it...

Now referring to the above questions: > ```python > solph.flows.Flow( > nominal_value=, > variable_costs=..., > min=[0 max=[min # Should it stay like that? (Q2) > fix=[min # If yes: Should...

I'm not going to go into details with a code review and at the moment, unfortunately, my time for oemof development is very limited, but I had a quick look...

> > > I am still struggling with the naming of the „other needs“. There are a couple of options: > > * Demands (should probably be reserved for energy...

Hi @lensum, I'm sorry, I'm not a maintainer myself. But what you can / should do beforehand is merge the current version of the oemof/dev branch into your project and...

Sorry for the late response to this one: I'm not so very familiar with stochastical programming either, but I think, it could be quite similar to the multi-period modeling I...

After discussing it at the dev meeting https://github.com/oemof/oemof/issues/96, this should be easier to add than I originally assumed. Here is a try to summarize. @simnh and @gnn: Please correct me...

Without having a deeper look into it, this should be possible by passing down values to the _initialize_ attribute of pyomo variables, see the [pyomo docs on Variables](https://pyomo.readthedocs.io/en/stable/pyomo_modeling_components/Variables.html). This should...

I totally agree with you, @simnh. That is exactly what I had in mind in terms of difficulties. You need a remapping back from your model results to the pyomo...

I'll close this for now. We can reopen if needed.