[WIP] Avoid angle divergence with HVDC AC emulation and PMax #1010
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Users report convergence problems with HVDC and AC emulation and PMax
What kind of change does this PR introduce?
When angle difference at HVDC bounds is larger than the operational range of the HVDC (ie range in which P grows with angle difference), the derivative for the AC emulation term does not return 0 for dp/dphi but the slope between bounded teta and angle value for which P = 0/
What is the current behavior?
Possible divergence if NR initialized with angle values out of the HVDC operational range.
What is the new behavior (if this is a feature change)?
Better convergence.
However, if a network convergence state is far outside of the operational range of an HVDC in AC eumlation mode, sensitivity analysis may return incorrect value (because dp/dphi does not return null)
Does this PR introduce a breaking change or deprecate an API?