Skip to content
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

Display the values (p, q, i) of "Xnode" after security analysis #950

Open
chri-dani opened this issue Feb 17, 2025 · 0 comments
Open

Display the values (p, q, i) of "Xnode" after security analysis #950

chri-dani opened this issue Feb 17, 2025 · 0 comments

Comments

@chri-dani
Copy link

Describe the current behavior

After running a security analysis for Contingency X and having a monitored element Y that is a TieLine, the results of security analysis when invoked for example with .get_branches(), give only information about the real nodes. For example regarding the currents:

Contingency X, TieLine -> i1=Value1 -- i2=Value2
Contingency X, DanglingLine1 -> i1=Value1 -- i2=NaN
Contingency X, DanglingLine2 -> i1=Value2 -- i2=NaN

  • where Value1 refers to the current of the real node of one side, and Value2 refers to the current of the real node of the other side.
  • NaN values refer to the current of the Xnode.

A more detailed example is attached.
Request for Xnode values.xlsx

Describe the expected behavior

My suggestion is to have also the values of the Xnode displayed after the security analysis and when .get_branches() is called, meaning p_boundary, q_boundary, i_boundary. So the currently NaN values shall be replaced with the ones of the Xnode.

Describe the motivation

A feature is needed to calculate the total capacity flows of TieLines from side1 to side2.
For example, when the Limiting CNE is a TieLine and we want to consider only the values of side1, it would be useful to have the values of the Xnode. This way, side2 can be somewhat ignored, allowing us to rely solely on side1 for the maximum loading and finally the maximum capacity flow.

Extra Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant