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
{{ message }}
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
It is important to be able to distinguish different node instances even if they have the same parameter set. E.g. when using a power grid with 30 nodes and modeling the fall out of a single node, let's choose node 10 here, by reducing this node away, it is currently not possible in general to associate the 29 nodes after the fall out with the correct ones among the 30 nodes before. I.e. In general, it is impossible to identify node 15 in the first case with the node 14 in the second. This can be particularly problematic when plotting the combined solutions.
Currently, two nodes with the same parameter set are literally the same:
In order to distinguish dynamic nodes, I suggest to use IDs. That way one doesn't have to do the difficult counting from before but can simply use the comparison operator ==.
I would implement that simply by adding a field id to all subtypes of AbstractNodeParameters.
Opinions?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is important to be able to distinguish different node instances even if they have the same parameter set. E.g. when using a power grid with 30 nodes and modeling the fall out of a single node, let's choose node 10 here, by reducing this node away, it is currently not possible in general to associate the 29 nodes after the fall out with the correct ones among the 30 nodes before. I.e. In general, it is impossible to identify node 15 in the first case with the node 14 in the second. This can be particularly problematic when plotting the combined solutions.
Currently, two nodes with the same parameter set are literally the same:
In order to distinguish dynamic nodes, I suggest to use IDs. That way one doesn't have to do the difficult counting from before but can simply use the comparison operator
==
.I would implement that simply by adding a field
id
to all subtypes ofAbstractNodeParameters
.Opinions?
The text was updated successfully, but these errors were encountered: