You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Topology templates should be in the list on the import screen depending on the scaling factor of a certain LES. A topology usually represents a certain amount of households, a scenario usually is scaled to a certain amount of households. Now these two are not connected.
The way I see this technically is that we sum up all the units attributes from a topology_template. This will give us a maximum (? @ChaelKruip) amount of households a certain topology represents. So:
This amounts to 99 households and a minimum ofcourse of 3 households. So if you scaled your households somewhere in between 3..99 households, this topology could be suited for your LES.
This requires us to ensure that the units are given for the end-points of featured topologies.
I'm not sure if we should show all topologies with households > households_in_LES or also limit the size of the topology at some point. For example we could show topologies in the range 0.8 * households < connections in topology < 1.2 * households, or something similar.
Topology templates should be in the list on the import screen depending on the scaling factor of a certain LES. A topology usually represents a certain amount of households, a scenario usually is scaled to a certain amount of households. Now these two are not connected.
The way I see this technically is that we sum up all the units attributes from a
topology_template
. This will give us a maximum (? @ChaelKruip) amount of households a certain topology represents. So:This amounts to 99 households and a minimum ofcourse of 3 households. So if you scaled your households somewhere in between
3..99
households, this topology could be suited for your LES.Scribbles of code:
The text was updated successfully, but these errors were encountered: