v1.16.0
Labels correspond the associated described change.
indicates that some methods were deprecated;
indicates a breaking change which could impact all users;
indicates a change in the simulation results that may affect existing tests in your application;
indicates a new parameter, a new parameter default or a new parameter usage;
📜 Release notes
Dependencies
- Bump powsybl-core to v6.8.0
This release introduces breaking changes in IIDM 1.14. See the migration guide
Reports
- Reports i18n (#1216) and {#1225}. Implements the powsybl-core report node V3 for i18n API.
. When creating a root report node, you need to include the OpenLoadFlow message bundle as explained in https://github.com/powsybl/powsybl-core/wiki/Migration-guide-v6.7.0#report-node-v3-for-i18n .
- Active Power Distribution: better reports severities when residual mismatch remains #1215 . Before this change, the active power distribution could emit a report with error severity when it failed to distribute the slack, even if the load flow parameters (such as slackBusPMaxMismatch or slackDistributionFailureBehavior) would not consider this as a failure.
IIDM changes
#1246 the field tapPosition of tap changers, and the field sectionCount of shunt compensators are no longer updated after a loadFlow. Instead, the fields solvedTapPosition and solvedSection are updated. For more information, see the migration guide
Robustness and accuracy
- Fix double slack distribution in DC Security Analysis (#1209)
- Ensure all parameters are read from the platform configuration file (#1214)
- In Connectivity Report do not count twice lost loads and generators that are on a contingency bus (#1204)
- Filter disabled generators when computing bus Q limits (#1220). Before the targetQ of disconnected groups of a PV bus was counted and shifted the PQ diagram .
may change results of tests that were affected by the issue.
- Change load flow result when there is no voltage control in a component (leads to NO_CALCULATION instead of FAILED) (#1226)
may change results of tests that check load flow result status.
- Force area boundary branches to min impedance (PR #1218). For more details see the Area Interchange Control algorithm description.
Extrapolate reactive capability curve limits when outside active power limits (PR #1224) adds the new parameter extrapolateReactiveLimits to allow a different computation of reactive limits for generators that control voltage during startup (targetP < pMin) instead of using the bounds of minP.
Add parameter to define min nominal voltage for unrealistic state check (PR #1217) adds the new parameter minNominalVoltageRealisticVoltageCheck to allow setting strict realistic voltage boundaries that would apply only to high voltage substations.
- Fix slack mismatch remaining after AIC (#1223 )
Security Analysis
- Add switch actions in Fast DC Security Analysis (PR #1153). For a list of remaining limitations of Fast DC security Analysis vs default DC security Analysis, see parameter dcFastMode documentation at https://powsybl.readthedocs.io/projects/powsybl-open-loadflow/en/latest/security/parameters.html
Sensitivity Analysis
- Sensitivity Analysis : Select tie line factor with its dangling line id (PR #1228). This change enables to use the same API to get a dangling line sensitivity whether it is paired or not. When a dangling line id is specified, if the dangling line is paired (and its studied side is the side 1 corresponding to the network side), the corresponding LfTieLineBranch is selected.
- Added support of BRANCH_REACTIVE_POWER and BRANCH_CURRENT per INJECTION REACTIVE POWER (PR #1237)
Performance
- Refactor access to branch limits when detecting limit violations (#1197)
- Save and restore only active power changes in Fast DC Security Analysis (#1205)
- Change log levels of messages in fast DC Security Analysis (#1222) Detailed logs for post-contingency and post-operator strategy simulations are now in DEBUG level. Setting the
com.powsybl.openloadflow.sa.AbstractSecurityAnalysislogger to DEBUG in your logging configuration file enables the display of detailed logs (but it is recommended to avoid it for better performance, use it only for debugging and detailed analysis purpose) - Cache loadTargetQ in buses (PR #1232)