powsybl-open-loadflow
powsybl-open-loadflow copied to clipboard
Refactor DC Sensitivity Analysis with Woodbury engine
Please check if the PR fulfills these requirements
- [ ] 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?
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
- [ ] Yes
- [ ] No
If yes, please check if the following requirements are fulfilled
- [ ] The Breaking Change or Deprecated label has been added
- [ ] The migration steps are described in the following section
What changes might users need to make in their application due to this PR? (migration steps)
Other information:
After refactoring, we propose to implement the DC sensitivity analysis as follows:
- Calculation of potential/actual connecrtivity losses of the contingencies (for now, in the WoodburyEngine).
- Calculation of rhs (for flows/injections), with modifications applied to the rhs in cases of broken connectivity, glsk with loss of elements... This is done in the DcSensitivityAnalysis class, and modified rhs are stored in the class WoodburyEngineRhsModifications.
- Calculation of pre/post contingency states using the WoodburyEngine. Note that only states are calculated here.
- Calculation of sensitivities in the DcSensitivityAnalysis class from the previously calculated states, and filling writers/results returned by the DC sensitivity analysis.
Feel free to comment @annetill @geofjamg !
Quality Gate passed
Issues
6 New issues
0 Accepted issues
Measures
0 Security Hotspots
96.5% Coverage on New Code
0.0% Duplication on New Code
Quality Gate passed
Issues
4 New issues
0 Accepted issues
Measures
0 Security Hotspots
96.5% Coverage on New Code
0.0% Duplication on New Code
Quality Gate passed
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
97.3% Coverage on New Code
0.0% Duplication on New Code