search

quintel / refinery

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

Multi-query edges do not always work - example in buildings & households #33

Closed Richard-Deuchler closed 10 years ago

Richard-Deuchler commented 10 years ago

When defining edges for the graph, I ran into the following problem:

There are certain edges, where I need to provide a parent and a child share. For example, in buildings (useful demand cooling) refinery knows the following initial values : screen shot 2013-08-07 at 17 07 04

and it transforms this into the following calculable:

screen shot 2013-08-07 at 17 07 20

However, in the households sector, the same trick does not do the job:

initial values': screen shot 2013-08-07 at 17 07 42

The initial set of parent and child shares does not allow for full calculation of all converters. calculable:

screen shot 2013-08-07 at 17 07 57

Admittedly, the two situations are not 100% the same, but I do not understand why refinery can calculate "upstream" in only one of the two cases.

antw commented 10 years ago

but I do not understand why refinery can calculate "upstream" in only one of the two cases.

Neither do I. I'll take a look into it.

Richard-Deuchler commented 10 years ago

Please see quintel/etsource@68b1875. Could it be the changed type of the edges?

antw commented 10 years ago

Please git up Atlas, and then bundle install to grab the latest version of Refinery. I made changes to Refinery today which happened to fix this. :smile:

households 1-finished-calculable

With that said, please change those two edges back to "flexible" (as they are in the diagram above). The "type" is used by ETEngine. While ETEngine isn't yet using the node and edge .ad files, when it does in the future, changing the "type" would probably break the model in horrible ways. :scream:

Richard-Deuchler commented 10 years ago

thanks @antw - everything solved.