-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CGMES export as bus/branch: unit test to clarify behaviour with non-retained open switches #3370
CGMES export as bus/branch: unit test to clarify behaviour with non-retained open switches #3370
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tests are great. Could you please also add some comment in the documentation (grid exchange formats/cgmes/export/topology-kind) to highlight that situation to users?
documentation added |
@zamarrenolm: Can you also fix the DCO problem on your last commit? |
077e4e8
to
dac62f6
Compare
fixed the problem with DCO |
Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
Co-authored-by: Olivier Perrin <[email protected]> Signed-off-by: Luma <[email protected]>
Co-authored-by: Olivier Perrin <[email protected]> Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
8a012da
to
d1a68b6
Compare
|
…etained open switches (#3370) * unit test to clarify bus/branch export with non-retained open switches * add documentation * move paragraph Signed-off-by: Luma <[email protected]> (cherry picked from commit 455fd74)
…etained open switches (#3370) * unit test to clarify bus/branch export with non-retained open switches * add documentation * move paragraph Signed-off-by: Luma <[email protected]> (cherry picked from commit 455fd74)
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Related to #3318
What kind of change does this PR introduce?
Additional unit test.
The goal is to show that when using bus/branch exports of a node/breaker network, you should close all non-retained open switches in your case before exporting it, if you plan to use the exported files for later calculations (and want to keep the maximum amount of connectivity).
What is the current behavior?
Having non-retained open switches in a network that is exported as bus/branch may result in multiple connectivity components in the exported network.
What is the new behavior (if this is a feature change)?
No behaviour is changed. The unit tests tries to clarify potential issues with bus/branch export of node/breaker networks that contain non-retained open switches.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information:
The unit test uses a simple node/breaker network:

where the disconnectors are open and marked as non-retained, and the breakers are also open and retained.
Exporting the network as bus/branch from this situation produces the following:

In this exported network, the generator and the load can not be reconnected to the rest of the network, even after closing the retained breakers.
If the non-retained switches are closed BEFORE exporting to bus/branch, the exported network will keep the possibility of reconnecting these equipment:
