-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Behaviour of initialization on previous values #429
Comments
Similar issue than one described in #188 |
In case of any operator strategy in the security analysis, we have added this fall back (https://github.com/powsybl/powsybl-open-loadflow/blob/main/src/main/java/com/powsybl/openloadflow/network/util/PreviousValueVoltageInitializer.java). We can discuss now added this for the contingency state computation. @sylvlecl what do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ambiguous.
When using
PREVIOUS_VALUES
as initialization option, we may get an exception with following message:This can make that option hard to use, because it can happen even after a very minor topology change.
To be discussed: we might want to fill the holes when they occur ?
Or maybe we could fall back on a DC values initialization ?
Alternatively, maybe this issue must be left for the user to handle, through a try/catch for example, or ensuring that he uses that option only when he is sure to have results on all buses.
The text was updated successfully, but these errors were encountered: