Flow decomposition¶
The flow decomposition module allows to decompose active flows on cross-border relevant network element with contingency (XNEC) based on the ACER methodology. This python interface is based on the java implementation in the PowSyBl ENTSO-E repository.
This simple version of flow decomposition will evolve with the next versions of flow decomposition Java version. Here are the assumptions that we made:
XNEC = lines specified by the user
zone = country
country GSK
no HVDC management
Run a flow decomposition¶
The general idea of this API is to create a decomposition object. Then, you can define contingencies if necessary. Then, you can define XNE and XNEC. XNEC definition requires pre-defined contingencies. Some pre-defined XNE selection adder functions are available. All the adder functions will be united when running a flow decomposition. Finally, you can run the flow decomposition with some flow decomposition and/or load flow parameters.
To do so, you can use the following methods:
Creates a flow decomposition objet, which can be used to run a flow decomposition on a network |
|
Add a contingency for each element (n N-1 states). |
|
Add a contingency with multiple elements (1 N-k state). |
|
Add branches to be monitored by the flow decomposition. |
|
Add branches to be monitored by the flow decomposition on precontingency state (XNE(s)). |
|
Add branches to be monitored by the flow decomposition on postcontingency state (XNEC(s)). |
|
Add branches that have a zone to zone PTDF greater than 5% or that are interconnections to be monitored on a precontingency state (XNE). |
|
|
Add branches that are interconnections to be monitored on a precontingency state (XNE). |
Add all branches of the network to be monitored on a precontingency state (XNE). |
|
Runs a flow decomposition. |
Some enum classes are used in the computer:
Parameters¶
The execution of the flowdecomposition can be customized using flowdecomposition parameters.
Parameters for a flowdecomposition execution. |