smn
But we might have a call to discuss the details (what is required, what is possible, etc)
I added a first idea (only for the flow-associated variables). Collecting the variables can acutally be easy once we have all our first stage cost expressions (as a pyomo-Expression instance)...
I looked through the code and found the following places where cost expressions occur (they are all build in `model.._objective_expression()` | Block | name | |-------------------------------|------------------| | FlowBlock | variable_costs...
Just a small info, I rebuild the mpisppy farmer example with oemof-solph and results are the same. You can check it out here: https://github.com/simnh/oemof-sp
Ok I added a few lines. Now the duals will be available by its constraint: ``` results = m.results() results[m.Transformer.relation, None] ``` I do not know if not an additional...
What you can do is excess certain parts of the objective in pyomo of the model, for example: ``` om.InvestmentFlow.investment_cost() om.InvestmentFlow.variable_cost() om.Flow.variable_costs() ... ``` This is currently the finest resolution...
BTW, the code would be example here, for the storage: https://github.com/oemof/oemof/blob/784eabb4beb64f523b046a77466cb857f4509c09/oemof/solph/components.py#L687-L693 Where `self` is the pyomo block with the constraints which it self is an attribute of the the solph...
Well I noticed that the `add`-method already works as expected. I think a delete method that looks at the entities -list and removes the object is just a handy and...
Nice, thx that was fast..than it seems my feeling is still quite ok at least in an 'acceptable range' Just to be sure: you checked for annualized investment costs? (Because...
Sounds great - oemof-tabular is missing ;-)