Add anchors on security documentation to be binded by OLF documentati…

docs/grid_model/extensions.md

@@ -710,7 +710,7 @@ This extension is provided by the `com.powsybl:powsybl-iidm-api` module.
 
 This extension is attached to a [network](network_subnetwork.md#network) and is used to define the angle references of a Power Flow solution.
 The support of this feature by Load Flow implementations may vary. For example, the [OpenLoadFlow](inv:powsyblopenloadflow:*:*#index) implementation
-today supports writing to the Network the terminals of the reference generators chosen via the [Reference Priority extension](#reference-priority).
+today supports writing to the Network the terminals of the reference generators chosen via the [Reference Priority extension](#reference-priorities-extension).
 
 The reference bus is defined through the terminal of the equipment and an integer specifying the reference priority.
 0 means "do not use as reference", 1 is "highest priority", 2 "second priority", etc.

docs/simulation/security/index.md

@@ -31,6 +31,7 @@ violations can have different types:
 The first input of the security analysis is a network. As this simulation is based on a [load flow](../loadflow/index)
 engine for a list of contingencies, this network should converge in the pre-contingency state.
 
+(security-contingencies)=
 ### Contingencies
 
 The security analysis needs a list of contingencies as an input. When contingencies are provided, the violations are
@@ -58,6 +59,7 @@ A contingency is made of contingency elements. A contingency can trigger one ele
 at a time (N-K). Bus bar and bus contingencies are special N-K contingencies as they trigger all the equipments
 connected to a given bus bar section.
 
+(security-operator-strategies)=
 ### Operator strategies
 
 An operator strategy is applied in pre-contingency or after a contingency, depending on the contingency context
@@ -69,6 +71,7 @@ provided. A contingency context can be:
 
 An operator strategy groups a condition and a list of remedial actions.
 
+(security-remedial-actions)=
 #### Remedial actions
 
 Remedial actions are actions that are applied when limit violations occur. Supported actions are:
@@ -99,6 +102,7 @@ Remedial actions can be *preventive* or *curative*:
 
 Note: you can find the current list of remedial actions implemented in the PowSyBl Open Load Flow security analysis provider in the [PowSyBl Open Load Flow documentation](inv:powsyblopenloadflow:*:*#security/inputs).
 
+(security-conditions)=
 #### Conditions
 
 Actions are applied if a condition is met. The conditions can be diversified and extended in the future:
@@ -116,7 +120,7 @@ Actions are applied if a condition is met. The conditions can be diversified and
   transformer threshold condition, injection threshold condition and AC/DC converter threshold condition.
 
 
-
+(security-state-monitors)=
 ### State monitors
 
 A stateMonitor allows getting information about branch, bus and three-winding transformers on the network after a
@@ -131,6 +135,7 @@ state or post-contingency state with a contingency id or both. For example:
   contingencyContext will contain contingencyId `c1`, contextType `ALL` and the state monitor will contain the id of the
   branch.
 
+(security-limit-reductions)=
 ### Limit reductions
 
 Limit reductions can be specified in order to detect when a specific limit is **nearly** reached, without having to
@@ -145,7 +150,8 @@ These criteria can include:
 - the use case (for monitoring only or also for applying remedial actions);
 - the contingency context (pre-contingency, after a specific contingency or after all contingencies, etc.);
 - the network elements targeted by the reduction (by ids, countries and/or nominal voltages);
-- which operational limits are affected by the reduction (permanent or temporary + acceptable duration).
+- which operational limits are affected by the reduction (permanent or temporary + acceptable duration);
+- which specified operational limit groups are affected by the reduction.
 
 You can find more details about limit reductions [here](./limit-reductions).
 

docs/simulation/security/limit-reductions.md

@@ -87,3 +87,8 @@ When no duration criteria are present, the reduction is applied to all permanent
 
 When several duration criteria are specified, the limit reductions apply to each one.
 For instance, if both criteria `PERMANENT` and (`TEMPORARY` ; `EQUALITY`: 600) are defined, the limit reduction will apply to permanent limits and 600 s limits.
+
+### Operational limits groups selection
+
+The list of the ids of the operational limits groups on which the limit reduction will be applied. If the list is empty, then the limit reduction will be applied to all operational limits groups.
+