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.

Sign up for GitHub

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

Jump to bottom

In Flow RaoResult, when calling isSecure, ensure that it is called on FLOW parameter #898

Open
pet-mit opened this issue Feb 22, 2024 · 0 comments · May be fixed by #905
Open

In Flow RaoResult, when calling isSecure, ensure that it is called on FLOW parameter #898

pet-mit opened this issue Feb 22, 2024 · 0 comments · May be fixed by #905
Labels
bug Something isn't working

Comments

@pet-mit
Copy link
Collaborator

pet-mit commented Feb 22, 2024

Describe the current behavior

When calling isSecure(PhysicalParameter.. u), the flow RaoResult implementations currently return whether flows are secure, regardless of u.
This can lead to an error for example if the flows are not secure, when the user calls isSecure(ANGLE)

Describe the expected behavior

At least check that u contains "FLOW"

Describe the steps

No response

Environment

No response

Relevant Log Output

No response

Extra Information

No response
@pet-mit pet-mit added the bug Something isn't working label Feb 22, 2024
@bqth29 bqth29 linked a pull request Feb 28, 2024 that will close this issue
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check physical parameters in RaoResult's isSecure powsybl/powsybl-open-rao
1 participant
@pet-mit