Matpower: extend status #3028
Draft
Matpower: extend status #3028
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]> # Conflicts: # matpower/matpower-converter/src/main/java/com/powsybl/matpower/converter/MatpowerExporter.java
Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
Signed-off-by: Luma <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
…k for each synchronousComponent. Select as slack the bus with the highest generation Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]> # Conflicts: # matpower/matpower-converter/src/main/java/com/powsybl/matpower/converter/MatpowerExporter.java
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: José Antonio Marqués <[email protected]>
Signed-off-by: marquesja1 <[email protected]> # Conflicts: # matpower/matpower-converter/src/main/java/com/powsybl/matpower/converter/MatpowerExporter.java
…ectable buses Signed-off-by: marquesja1 <[email protected]>
Signed-off-by: marquesja1 <[email protected]>
Signed-off-by: marquesja1 <[email protected]>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
What kind of change does this PR introduce?
Feature
What is the current behavior?
Only equipment with status = 1 (in service) is exported.
What is the new behavior (if this is a feature change)?
Equipment with status = 0 (out of service) is also exported.
Only the equipment that can be connected to exported buses is exported.
Only the buses inside the main synchronous component and the buses of other parts of the main connected component linked with the main synchronous through DC lines with voltageSourceConverters are exported.
Almost all the
exported busesareenergized buses. Only thestar busesof three winding transformers with all three legs disconnected that can be connected toexported busesare exported asisolated buses.Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: