powsybl-core Add contingency status for security analysis

Add contingency status for security analysis

Open obrix opened this issue 2 years ago • 3 comments

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Does this PR already have an issue describing the problem ? If so, link to this issue using '#XXX' and skip the rest

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Add contingency status for security analysis, first for post contingency results. Update version of the result format to 1.3. I can probably also add a status for the pre contingency case, but some of the enums values are less relevant there.

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:

[ ] The Breaking Change or Deprecated label has been added
[ ] The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

Oct 20 '22 11:10 obrix

I think this status should be add in OperatorStrategyResult too

Oct 24 '22 08:10 EtienneLt

@EtienneLt Thanks, yes I am still working on it and will push more commits soon (adding to OperatorStrategyResult and removing the computationOK boolean everywhere).

Oct 24 '22 08:10 obrix

Kudos, SonarCloud Quality Gate passed!