Add an option that allow checking unrealistic voltage only on final state of the loadflow. #1087
Conversation
…tate of the loadflow. It allows outerloops to fix some voltage issues before failing. Signed-off-by: MURGEY Sebastien <[email protected]>
murgeyseb
force-pushed
the
feature/add-option-to-check-unrealistic-voltage-only-on-final-state
branch
from
139078d to
d874b63
Compare
|
| @@ -14,6 +14,13 @@ | |||
| */ | |||
| public class NewtonRaphsonParameters extends AbstractNewtonParameters<NewtonRaphsonParameters> { | |||
|
|
|||
| public enum UnrealisticVoltageCheckBehavior { | |||
There was a problem hiding this comment.
@murgeyseb can you add the documentation of the new parameter you have introduced. Or I can do it if you prefer. Just tell me !
There was a problem hiding this comment.
As I understand it, this PR is a workaround to the fact that remote voltage control can create very low voltages, either in intermediate state of the solution of in final states. It does not solve the problem and does not resolve all divergence issues due to low voltage with this algorithm.
Unless there are other use cases for this PR, I would prefer that we do not commit this workaround before we have a full solution to stabilize the remote voltage algorithm.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Feature
What is the current behavior?
Current implementation of unrealistic voltage check does stop computation with status Unrealistic Voltage each time any Newton Raphson iteration ends with a found voltage on any node outside the allowed range.
What is the new behavior (if this is a feature change)?
Adds an option that allow checking unrealistic voltage only on final state of the loadflow. It allows outerl oops to fix some voltage issues before failing.
Does this PR introduce a breaking change or deprecate an API?