[WIP] DC hot start

[gautierbureau]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

[gautierbureau]

Related to this subject I have two interrogations:

• How could admittance values could be accessible from outside to use them in an optimization problem
• If the loss are designed that way they also need to be accessible from outside to add them to the optimization problem

[SylvestreSakti]

Hello @gautierbureau , thank you, I'll have some time to review it after the march release. I may have some ideas in order not to modify too much the current architecture of LfBus (maybe by creating a new class extending AbstactLfInjection to model these loss injections), and also maybe a new kind of DcEquationTerm can be created for that.

For the wanted outputs (admittance and losses), can't it be easyly computed from the result of such a load flow ? Or are there performance constraints that make you need that directly ? (Maybe I am wrong since I did not take time to read it accurately)