quintel / refinery

Calculates node demands and edge shares for sparse energy graphs.
2 stars 0 forks source link

Some energy flows are not calculated in Residences sector #37

Closed Richard-Deuchler closed 10 years ago

Richard-Deuchler commented 10 years ago

I am working on the Residence sub-graph. What keeps me from finishing it is the following problem:

initial values: (the green arrow indicates that the lower figures refer to the diagonal edge (not relevant in this ticket)) screen shot 2013-08-08 at 11 40 13

calculable: screen shot 2013-08-08 at 11 40 31

Why does refinery not calculate the energy flow from households_useful_demand_for_space_heating_after_insulation_and_solar_heater_and_add_on to households_useful_demand_for_space_heating_after_insulation_and_solar_heater?

(I added the red arrow for clarity, the transparent purple incalculable edge is hard to see)

Richard-Deuchler commented 10 years ago

For this particular edge, I do not want to provide a parent or child share. (They are simply not known in the Excel analysis. If refinery cannot work around it, I might have to. But that would significantly broaden the scope of the Excel analysis)

antw commented 10 years ago

I think there are two issues to note here:

I'll look into it shortly and get back to you.

antw commented 10 years ago

I noticed that there is a similar set of nodes just below those space heating ones. But in that case, one of the flexible edges has a parent share:

households 0-initial-values

The issue here is that Refinery can't figure out the demand of the households_useful_demand_for_space_heating_after_insulation_and_solar_heater node. It knows the demand of one incoming edge – but not the child share – and the demand of an outgoing edge – but not the parent share. It's the same as this issue.

Richard-Deuchler commented 10 years ago

ok - then I will produce one more parent_share in the Residence Analysis. That should fix the problem. Thanks for checking, @antw

Richard-Deuchler commented 10 years ago

The above solution is possible but ugly (we do not really want to produce these two parent shares in the Excel analysis).

The preferred solution is likely going to be to change two edge types from "flexible" to "share". See https://github.com/quintel/etsource/compare/master...set_household_edge_to_flexible (do not merge yet).

Richard-Deuchler commented 10 years ago

problem solved, closing. For further documentation, go to https://github.com/quintel/refinery/issues/41