AntaresSimulatorTeam · JMJ-rte · Jul 29, 2026 · Jun 15, 2026 · Jun 15, 2026 · Jun 16, 2026
diff --git a/docs/programmatic/antares-craft-overview.md b/docs/programmatic/antares-craft-overview.md
@@ -26,6 +26,6 @@ in the [Antares Craft by Example](https://antares-craft.readthedocs.io/en/latest
 page. 
 
 Moreover, you can see all the reference for the classes and methods in the reference section of 
-[Antares website](https://antares-craft.readthedocs.io/en/latest/api-reference/).
+[Antares website](https://antares-craft.readthedocs.io/en/latest/api-reference/api_conf/).
 
 
diff --git a/docs/programmatic/antares-solver-cli.md b/docs/programmatic/antares-solver-cli.md
@@ -10,7 +10,7 @@
 | --expansion                         | Force the simulation in [expansion](../reference/xpansion-settings.md) mode                                                                                                                                     |
 | --economy                           | Force the simulation in [economy](../reference/config-general.md#building-mode) mode                                                                                                                                       |
 | --adequacy                          | Force the simulation in [adequacy](../reference/config-general.md#building-mode) mode                                                                                                                                      |
-| --parallel                          | Enable [parallel](../reference/config-advanced-parameters.md/#simulation-cores) computation of MC years                                                                                                                     |
+| --parallel                          | Enable [parallel](../reference/config-advanced-parameters.md#simulation-cores) computation of MC years                                                                                                                     |
 | --force-parallel=VALUE              | Override the max number of years computed simultaneously                                                                                                    |
 | --linear-solver=VALUE               | The optimization solver to use for linear problems. Possible values are: `sirius` (default, LP only), `coin`, `xpress`, `scip` (MIP only), `glpk` (Linux only), `highs`, `pdlp` (LP only), `gurobi` |
 | --linear-solver-param=VALUE         | Linear solver-specific parameters. Syntax is solver-dependent, and only supported for `scip` and `xpress`                                                                                           |

diff --git a/docs/programmatic/antares-xpansion-cli.md b/docs/programmatic/antares-xpansion-cli.md
@@ -62,7 +62,7 @@ Set the optimization method used by Antares Xpansion.
 |----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `benders`            | Launch the classical Benders decomposition or the Benders by batch algorithm depending on `batch_size`.
 | `mergeMPS`           | Launch a frontal resolution of the investment problem (i.e. without decomposition). This is much more time-consuming than using Benders decomposition. |
-| `adequacy_criterion` | Launch Antares Xpansion with reliability constraints, see [adequacy criterion](#).                                                 |
+| `adequacy_criterion` | Launch Antares Xpansion with reliability constraints, see adequacy criterion.                                                 |
 
 ### `--problem-format {MPS, OPTIMIZED}`
 

diff --git a/docs/reference/area.md b/docs/reference/area.md
@@ -10,11 +10,12 @@ at the node level. That's why you can attach to a map:
 - Consumption which is called [load](load.md)
 - Generation
     - [Thermal plants](thermals.md)
-    - Short-term [storage](storages.md)
     - [Renewable](renewables.md) sources
     - [Hydro](hydro.md) objects
     - [Reserves](reserves.md)
     - Other [miscellenous generation](misc-gen.md)
+- Storage
+    - Short-term [storage](storages.md)
 
 ## Properties
 
@@ -24,8 +25,8 @@ at the node level. That's why you can attach to a map:
 Average cost of failure for each area of the study (or value of lost of load VOLL).
 
 !!! tip
-    It is better if the unsupplied energy cost is much larger than
-    the cost of the most expersive generating plant of the area.
+    It is recommended that the unsupplied energy cost is much larger than
+    the cost of the most expensive generating plant of the area, otherwise such plant will never be activated.
 
 #### Spilled (€/MWh)
 
@@ -68,3 +69,24 @@ Allow to set the integration or not of the zone in the [adequacy patch](adequacy
 - `outside`
 - `inside`
 - `virtual`
+
+## Equations
+
+!!! info
+    You can check the section 
+    [Balance between load and generation](./optimization-problem.md#balance-between-load-and-generation)
+    from the [Optimization problem](./optimization-problem.md) page for details
+    about the **equations for a give node.**
+
+2 hourly variables are created per node:
+
+- The hourly spillage power 
+- The hourly unsupplied power
+
+4 parameters are created per node :
+
+- Average unsupplied energy cost 
+- Average spilled energy cost 
+- Spread unsupplied energy cost 
+- Spread spilled energy cost 
+
diff --git a/docs/reference/flow-models.md b/docs/reference/flow-models.md
@@ -126,4 +126,4 @@ $$
     FB stands for "flow-based", denomination used in the framework given to 
     the internal electricity market of western Europe.
 
-[^KL]: Such a model was used in the European [E-Highway project](http://www;e-highwy2050.eu).
+[^KL]: Such a model was used in the European [E-Highway project](https://zenodo.org/records/8232662).
diff --git a/docs/reference/hydro.md b/docs/reference/hydro.md
@@ -221,10 +221,10 @@ disabled; when enabled, this series is generated by Antares instead, based on th
 run-of-river share defined in [`Overall monthly hydro`](#overall-monthly-hydro). Used in the [optimization](optimization-problem.md), and in the [heuristic](hydro-heuristic.md) to
 compute the residual demand. Run-of-river (RoR) hydroelectric
 generation is a type of electricity production that relies on the natural flow
-of a river without significant water storage. Unlike traditional hydroelectric
-dams, RoR plants generate power continuously based on the river's current water
-level and flow rate. This makes them highly dependent on seasonal variations
-and weather conditions, leading to fluctuations in electricity production.
+of a river without significant water storage, not considered in the modelling. 
+Unlike traditional hydroelectric dams, RoR plants generate power continuously based 
+on the river's current water level and flow rate, considered as stochastic input data, like other RES generation. 
+This makes them highly dependent on seasonal variations and weather conditions, leading to fluctuations in electricity production.
 
 !!! info
     Run-of-river generation is non-dispatchable. There is no storage of energy.

diff --git a/docs/reference/outputs.md b/docs/reference/outputs.md
@@ -3,12 +3,19 @@
 When the simulation is done, you can view the different outputs generated by
 Antares Simulator. 
 
-These results follow a precise structure. They are presented by year 
-or presented aggregated accross all the simulated scenarios. 
+These results follow a precise structure. They are presented year by year or in aggregated form for all the simulated scenarios.
+In the aggregated format, each result is broken down into four values:
+
+- Expected value : the mean of the results for all the simulated Monte-Carlo years.
+- Standard deviation of the results for all the simulated Monte-Carlo years.
+- Minimum value of the results for all the simulated Monte-Carlo years.
+- Maximum value of the results for all the simulated Monte-Carlo years.
+
 
 !!! note
     The mean and standard deviation are computed taking into account
     the weights indicated in the [scenario playlist](../tutorials/select-scenario.md).
+    A dedicated "id" file indicates, for each result, which Monte-Carlo years correspond to these minimum and maximum values
 
 Then, they are grouped by:
 
@@ -108,8 +115,11 @@ and hydro cost.**
 
 #### OV. COST CSR (Euro)
 
+This variable, along with all subsequent variables bearing the "CSR" suffix, is similar to the corresponding variables lacking this suffix.
+They differ only through the application of a post-processing correction intended to net DTG MRG and UNSP ENRG; this netting results in the addition of a corrective term to the variable with the "CSR" suffix.
+
 Same as the [overall cost](#ov-cost-euro), but with CSR (curtailment sharing rule)
-unsupplied cost version[^adqp].
+unsupplied correction cost [^adqp].
 
 #### OP. COST (Euro)
 
@@ -121,7 +131,8 @@ Locational marginal price corresponding to the overall economic effect of a loca
 
 #### MRG. PRICE CSR (Euro)
 
-<!-- TODO -->
+Same as the [marginal price](#mrg-price-euro), but with CSR (curtailment sharing rule)
+unsupplied correction cost [^adqp].
 
 #### BALANCE (MWh)
 
@@ -138,7 +149,7 @@ Unsupplied energy: adequacy indicator (Expected Energy Not Served–EENS).
 
 #### UNSP. ENRG. CSR (MWh)
 
-Unsupplied energy after CSR (demand that cannot be satisfied)[^adqp].
+Unsupplied energy after CSR correction (demand that cannot be satisfied)[^adqp].
 
 #### DENS (MWh)
 
@@ -154,7 +165,6 @@ as defined by the adequacy patch[^adqp].
 
 #### SPIL. ENRG
 
-**Introduced in v8.5**
 Spilled energy (energy produced that cannot be used and has to be wasted).
 
 #### LOLD (h)
@@ -189,7 +199,7 @@ Disp. Ther. Gen. (AVL DTG – sum of all dispatched thermal generation)
 
 #### DTG MRG CSR (MWh)
 
-DTG MRG after CSR[^adqp].
+DTG MRG after CSR correction[^adqp].
 
 #### MAX. MRG (MWh)
 
@@ -198,7 +208,7 @@ of the week were used to maximise margins instead of minimizing costs.
 
 #### MAX. MRG CSR (MWh)
 
-<!-- TODO -->
+MAX. MRG after CSR correction[^adqp].
 
 ### Thermal objects
 
@@ -282,6 +292,8 @@ Same as above, but by dispatchable plant.
 #### NPCAP HOURS (h)
 
 Near price cap hours.
+Indicator of the number of hours during which the marginal price exceeds a given threshold.
+This threshold generally corresponds to the Value of Loss Load (VoLL) minus 5 €/MWh.
 <!-- Depends on unsupplied energy cost parameter and margin threshold (5.0) ? -->
 
 ### Renewable sources
@@ -678,4 +690,4 @@ more detailed values can be found in output folder: optimization/ week-by-week/y
 [^15]: 
     dispatchable production 
     = power generation above min gen 
-    = (power generation) - (min gen modulation) * num units * capacity
+    = (power generation) - (min gen modulation) * num units * capacity
diff --git a/docs/reference/renewables.md b/docs/reference/renewables.md
@@ -1,4 +1,33 @@
 # Renewables
+## Main characteristics of the object
+
+Antares offers heterogeneous possibilities to refine the modelling of a production park according to its nature. Thus, for Renewable Energy Sources (RES), it is possible, via the cluster concept, to create several subsets of production means with specific characteristics, for the same area (or node). Another historical modeling exists for such RES objects, it is an aggregate view of wind and solar generation per node (see [Wind & solar page](wind-and-solar.md)).
+
+There is a restriction for the cluster modelling : only "Ready made" type "Times-Series" are authorized to parameterize the production chronicles of these clusters. Indeed, the "Times-Series Analyser" and "Times-Series Generator" modules only produce aggregated TS of wind or solar generation for each of the nodes in the study area.
+
+Thanks to renewable clusters, it is possible to dissociate a set of given production assets, attached to the same modelling area, according to criteria such as :
+
+- Technology (depending on technological progress, some renewable assets can have very different load factors for the same weather forcing)
+- Location (for example, the on-shore/off-shore distinction for wind power or the grouping of structures by geographical sub-sectors can make it possible to calibrate specific weather forcings).
+
+With such RES object, there is no impact on the optimization problem solved at the simulation stage, since this renewable production will be considered as non-dispatchable and is fully deducted from the demand, to constitute a single residual demand chronicle to be satisfied by node.
+
+Cluster modelling brings a significant evolution in the Antares data model that has an impact on the Input/Output data formats and in the User Interface (see [next chapter](wind-and-solar.md)) and this can lead to a significant increase in the memory space occupied by a study.
+
+In addition, similar to what exists for thermal clusters, cluster modelling allows to carry out an intermediate grouping of the different clusters via the definition of categories (or "groups"). From then on, certain information available at the output of Antares will be developed at the level of the new categories proposed.
+
+## Switching between "Renewable clusters" and "Wind & solar aggregated" modeling
+There is a cohabitation of the 2 models. The choice of renewable generation modeling is made through an advanced parameter, "Renewable Generation modeling" which can take one of the following 2 values:
+
+- Aggregated (default value)
+- Clusters
+
+
+Please note that the renewable generation data loaded or developed in Antares for a modeling will not be switched to the other modeling when this parameter is modified, they will simply be ignored. However, they will not be lost and will be visible again and taken into account during the reverse switch (they are stored in different directories in the "input" folder of an Antares study).
+
+Selecting the "Aggregated" value will lead to keeping the representation of historical renewable production in Antares.
+
+Selecting the "Clusters" value will allow access to the new representation.
 
 ## Parameters
 
@@ -41,6 +70,12 @@ The type of data recorded in the time series chronicles.
 <span class="param-badge badge-int">int</span>
 Number of units inside the cluster.
 
+Note that this setting allows you to explicitly divide your cluster into a set of identical units and specify the nominal capacity of each.
+However, this feature does not affect the resolution behavior. Therefore, these 2 sets are equivalent :
+
+- `unit = n / nominal capacity = x`
+- `unit = 1 / nominal capacity = n*x`
+
 #### Nominal capacity (MW)
 
 <span class="param-badge badge-float">float</span>