Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic simulation final state value #3142

Merged
merged 10 commits into from
Sep 26, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/grid_exchange_formats/cgmes/export.md
Original file line number Diff line number Diff line change
Expand Up @@ -355,7 +355,7 @@ Optional property that defines which naming strategy is used to transform IIDM i
It can be:
- `identity`: CGMES IDs are the same as IIDM IDs.
- `cgmes`: new CGMES IDs (new master resource identifiers, cim:mRID) are created for IIDM `Identifiables` if the IIDM IDs are not compliant with CGMES requirements.
- `cgmes-fix-all-invalid-ids`: ensures that all CGMES IDs in the export will comply with CGMES requirements, for IIDM `Identifiables`and also for its related objects (tap changers, operational limits, regulating controls, reactive capability curves, ...).
- `cgmes-fix-all-invalid-ids`: ensures that all CGMES IDs in the export will comply with CGMES requirements, for IIDM `Identifiables`and also for its related objects (tap changers, operational limits, regulating controls, reactive capability outputVariables, ...).
Its default value is `identity`.

**iidm.export.cgmes.uuid-namespace**
Expand Down
12 changes: 6 additions & 6 deletions docs/simulation/dynamic/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The inputs of a dynamic simulation are the following:
- a mapping between static components of the network and dynamic models
- optionally, a description of events occurring in the dynamic simulation (disconnection of a line, change of tap for a transformer, etc.)
- a set of parameters for the simulator itself (simulation start and stop time, solver parameters, etc.)
- a configuration file to configure the curves to export at the end of the simulation
- a configuration file to configure the output variables to export at the end of the simulation

(dynamic-models-mapping)=
### Dynamic models mapping
Expand All @@ -32,17 +32,17 @@ For the moment, the only way to associate dynamic models to static components is
For the moment, the only way to add events to the simulation is through a groovy script. Note that the syntax of this script is specific to each simulator:
- [Dynawo event model DSL](inv:powsybldynawo:*:*#dynamic_simulation/event-models-dsl)

(curves-configuration)=
### Curves configuration
For the moment, the only way to monitor dynamic variables of the simulation in order to export curves at the end of the simulation is to provide a groovy script to the simulation. Note that the syntax of this script is specific to each simulator:
- [Dynawo curves DSL](inv:powsybldynawo:*:*#dynamic_simulation/curves-dsl)
(output-variables-configuration)=
### Output variables configuration
For the moment, the only way to add output variables configuration is to provide a groovy script to the simulation. Note that the syntax of this script is specific to each simulator:
- [Dynawo output variables DSL](inv:powsybldynawo:*:*#dynamic_simulation/output-variables-dsl)

## Outputs

The outputs of a dynamic simulation are:
- the updated static network (which may have been topologically modified depending on the events or automatons defined as inputs)
- the different results of the dynamic simulation:
- some curves asked for by the user to track the evolution of specific variables throughout the simulation
- some curves or final state values asked for by the user to track the evolution of specific variables throughout the simulation
- some aggregated data regarding constraints, like a security analysis output
- timelines that contain the list of events that occurred during the dynamic simulation, be them planned beforehand through events, or not
- logs about the execution of the dynamic simulator
Expand Down
13 changes: 8 additions & 5 deletions docs/user/itools/dynamic-simulation.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ In the end, the results and the modified network can be exported to files.

## Usage
```
usage: itools [OPTIONS] dynamic-simulation --case-file <FILE> [--curves-file
usage: itools [OPTIONS] dynamic-simulation --case-file <FILE> [--output-variables-file
<FILE>] --dynamic-models-file <FILE> [--event-models-file <FILE>]
[--help] [-I <property=value>] [--import-parameters <IMPORT_PARAMETERS>]
[--output-file <FILE>] [--parameters-file <FILE>]
Expand All @@ -15,7 +15,10 @@ Available options are:

Available arguments are:
--case-file <FILE> the case path
--curves-file <FILE> curves description as Groovy file
--output-variables-file <FILE> output variables description as
Groovy file: defines a list of
variables to plot or get the final
value
--dynamic-models-file <FILE> dynamic models description as a
Groovy file: defines the dynamic
models to be associated to chosen
Expand Down Expand Up @@ -45,8 +48,8 @@ This option defines the path of the mapping file used to associate dynamic model

### Optional options

`--curves-file`
This option defines the path of the configuration for the curves to export at the end of the simulation. This configuration file is a groovy script that respects the [curves DSL](../../simulation/dynamic/index.md#curves-configuration) syntax.
`--output-variables-file`
This option defines the path of the configuration for the output variables to export at the end of the simulation. This configuration file is a groovy script that respects the [outputVariables DSL](../../simulation/dynamic/index.md#output-variables-configuration) syntax.

`--event-models-file`
This option defines the path of the configuration for the events to simulate during the simulation. At the moment, only groovy scripts are supported. The [event models DSL](../../simulation/dynamic/index.md#event-models-mapping) depends on the simulator used.
Expand All @@ -73,7 +76,7 @@ The expected results are described in the [time domain documentation](../../simu
## Examples
The following example shows how to run a power flow simulation, using the default configuration:
```
$> itools dynamic-simulation --case-file IEEE14.iidm --dynamic-models-file dynamicModels.groovy --curves-file curves.groovy
$> itools dynamic-simulation --case-file IEEE14.iidm --dynamic-models-file dynamicModels.groovy --output-variables-file outputVariables.groovy
Loading network '/tmp/mathbagu/IEEE14.iidm'
dynamic simulation results:
+--------+
Expand Down
Loading