-
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
LfNetwork serialization #982
Comments
This issue is low priority, but as some preliminary work has been done by @CBiasuzzi the issue has been created to keep track of that work and the corresponding brainstorming. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the current behavior
Launching several loadflows on separaed environments needs the LfNetwork to be rebuild.
Describe the expected behavior
The LfNetwork can be serialized/deserialized so that it can be saved (and exchanged) and later reloaded.
Describe the motivation
This feature is motivated by massive launches of loadflows. This feature really makes sense only if the LfNetwork deserialization is significantly quicker than building it from the iidm network.
Extra Information
Note that deserializing the LfNetwork will need the iidm network aside, as some LfNetwork elements contain iidm objects. Therefore the iidm file loading cannot be avoided.
The text was updated successfully, but these errors were encountered: