You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/castor.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,7 @@ As mentioned above, for NTC Capacity calculation/ CEP Validation, this stop crit
130
130
These stop criteria only make sense for a minimum margin objective function (may it be absolute or relative).
131
131
132
132
On both stop criteria, [additional constraints](parameters.md#network-actions-optimisation-parameters) can be added, for example:
133
-
- the maximal number of consecutive chosen network actions, also called search tree depth (for [preventive](parameters.md#max-preventive-search-tree-depth), [auto](parameters.md#max-auto-search-tree-depth) and [curative](parameters.md#max-curative-search-tree-depth) search trees),
133
+
- the maximal number of consecutive chosen network actions, also called search tree depth (for [preventive](parameters.md#max-preventive-search-tree-depth) and [curative](parameters.md#max-curative-search-tree-depth) search trees),
134
134
- the [minimal relative gain](parameters.md#relative-minimum-impact-threshold) of objective function between two consecutive network actions (i.e. between two search tree depths).
First, all automatic network actions with a FORCED usage method are applied on the network. FORCED means that no optimization is carried out and that as long as the triggering conditions are met, the remedial action is applied.
55
55
56
-
#### Automatic search tree
57
-
58
-
Then, the automatic network actions which are available (i.e. not mandatory to apply) are selected by the RAO if they
59
-
help making the network secure, using a search-tree algorithm (similar to what is done in preventive or curative).
60
-
61
56
#### Automatic range actions simulation
62
57
63
-
Finally, automatic range actions are applied one by one, as long as some of the perimeter's CNECs are overloaded. Range
58
+
Then, automatic range actions are applied one by one, as long as some of the perimeter's CNECs are overloaded. Range
64
59
actions include PSTs and HVDCs. The remedial actions' speed determines the order in which they are applied: the fastest
65
60
range actions are simulated first. Aligned range actions are simulated simultaneously.
66
61
67
-
> Note that auto range actions must have a FORCED usage method.
62
+
> Note that auto range actions must have a FORCED usage method too.
68
63
69
-
Automatic range actions' setpoint is computed using the results of a sensitivity analysis computation, during which the
64
+
Automatic range actions' set-point is computed using the results of a sensitivity analysis computation, during which the
70
65
sensitivity $\sigma$ of a range action on a CNEC is computed. By focusing on the worse overloaded CNEC, we can compute
71
-
the automatic range action's optimal setpoint to relieve that CNEC with the following formula:
66
+
the automatic range action's optimal set-point to relieve that CNEC with the following formula:
Copy file name to clipboardExpand all lines: ra-optimisation/rao-api/src/main/java/com/powsybl/openrao/raoapi/json/extensions/JsonTopoOptimizationParameters.java
Copy file name to clipboardExpand all lines: ra-optimisation/rao-api/src/main/java/com/powsybl/openrao/raoapi/parameters/extensions/SearchTreeRaoTopoOptimizationParameters.java
-17
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,6 @@ public class SearchTreeRaoTopoOptimizationParameters {
Copy file name to clipboardExpand all lines: ra-optimisation/rao-api/src/test/java/com/powsybl/openrao/raoapi/parameters/RaoParametersYamlConfigTest.java
0 commit comments