DyCoV is an engineering-oriented framework designed to support grid connection
studies through automated dynamic simulations and compliance checks.
It automates the verification of dynamic grid compliance requirements for solar
and wind farms (Power Park Modules — PPM), battery energy storage systems (BESS),
and synchronous machines (SM), covering workflows from model validation to
grid-code compliance assessment. As an end-to-end framework, DyCoV supports
both model validation and compliance assessment workflows used during grid
connection studies.
DyCoV is not a simulation tool itself — it leverages Dynawo to perform simulations and focuses on automated validation and compliance assessment workflows.
DyCoV follows a structured validation pipeline where dynamic behaviour is evaluated against defined compliance criteria:
Inputs (Model / Curves)
↓
Simulation (Dynawo)
↓
Signal Processing
↓
Validation (PCS)
↓
Reports
Depending on the workflow, DyCoV either:
- compares simulated results against reference curves (model validation), or
- evaluates system behaviour under predefined disturbances (performance verification)
This pipeline is fully automated and produces structured reports and plots.
This section provides a high-level overview of the core studies supported by DyCoV and how they contribute to grid connection validation workflows.
DyCoV automates two independent and mandatory studies required for grid connection validation:
-
RMS model validation — verifies that a dynamic model reproduces a reference behaviour within defined tolerances (PCS‑I16, Zones 1 and 3)
-
Electrical performance verification — evaluates the installation response under grid disturbances and checks compliance with grid‑code requirements (PCS‑I2, I3, I4, I5, I6, I7, I8, I10)
Both studies must be successfully completed to formally validate an installation for grid connection. These studies are independent but complementary, and together form the basis for validating a generation unit prior to grid connection.
Additionally:
- Grid‑Forming (GFM) envelope calculation — computes analytical bounds for GFM unit responses (optional workflow)
The following terms are used throughout the documentation:
- PCS: Performance Checking Sheet — set of validation tests defined in the RTE grid code (DTR)
- PPM: Power Park Module — wind, solar or aggregated generation installation
- RMS model validation — model validation workflow (PCS I16)
- Electrical performance verification — compliance assessment workflow (PCS I2–I10)
- GFM: Grid‑Forming — control mode for inverter-based resources (optional workflow)
- EMT: Electromagnetic Transients
- OC: Operating Condition
- OP: Operating Point
- PDR: Point of Delivery (Point de raccordement)
- SCR: Short Circuit Ratio
- CCT: Critical Clearing Time
- TSO: Transmission System Operator
This section serves both as an entry point and as a guide to the documentation structure:
- Quick start → minimal working examples
- Tutorials → step-by-step workflows (recommended entry point)
- Installation → environment setup
- Reference manuals → detailed technical documentation
- Developer docs → extension and internal architecture
Depending on your objective:
- To run DyCoV quickly and see results → go to Quick start
- To validate a real installation → run both validation and performance workflows in sequence
- To build your own study → see input preparation tutorials
Example cases are available in the examples/ directory and can be copied
and adapted to your own projects.
For a hands-on introduction, proceed to the Quick start section.
For detailed workflow explanations, refer to the Documentation section.
This section describes the data exchanged with DyCoV and how it is used across different workflows. DyCoV works with time-domain dynamic responses obtained from simulations or field measurements.
Typical inputs:
- Dynawo models — RMS simulation models of the installation
- Reference curves — expected behaviour (used for validation)
- Producer curves — simulated responses (used when simulations are provided externally instead of being run through Dynawo)
These are typically used when simulations are generated outside DyCoV and need to be assessed without rerunning Dynawo.
Typical outputs:
- PDF compliance reports
- Interactive HTML plots
- A structured
Results/directory (organized per study and scenario)
For full details, see: Preparing inputs
This section describes the supported installation options and points to detailed setup guides.
Choose the one that best fits your environment and usage (native, WSL, or development setup).
Once installed, DyCoV is accessed through the dycov command-line interface.
For developers building from source, see: Setup
The following steps install DyCoV in a native Linux environment.
For detailed procedures and advanced setups, see: Linux native
DyCoV requires a Linux environment with system dependencies (e.g. Python ≥ 3.13, build tools, LaTeX).
# Download and install DyCoV
curl -L https://github.com/dynawo/dyn-grid-compliance-verification/releases/latest/download/linux_install.sh | bashAfter installation, activate the environment and verify that the CLI is available:
# Activate environment
source dycov/activate_dycov
# Check CLI
dycov --versionThe following steps install DyCoV in a Windows Subsystem for Linux environment.
DyCoV runs inside a preconfigured WSL (Windows Subsystem for Linux) environment. The following steps assume this environment is used as provided.
For detailed procedures and advanced setups, see: Using the provided image
Prerequisite: WSL must be enabled:
https://learn.microsoft.com/en-us/windows/wsl/install
Download the following files:
Run:
import_wsl.batThis will import and configure the DyCoV environment automatically.
This section provides minimal working examples to quickly execute each main workflow using bundled cases, allowing you to quickly verify the installation and explore the generated outputs.
Note: On native installations, ensure the DyCoV environment is activated (e.g.
source dycov/activate_dycov). In WSL and Docker environments, it may already be active.
For a more detailed walkthrough of these steps and expected outputs, see: Quick start
This workflow focuses on validating that a dynamic model reproduces expected reference behaviour.
For a detailed description of this workflow and its expected outputs, see: RMS validation
Run:
dycov validate examples/Model/Wind/WECC4B/ReferenceCurves/ -m examples/Model/Wind/WECC4B/Dynawo/This will:
- run RMS simulations
- compare results against reference curves
- generate validation reports
Expected result:
- A
Results/Model/directory is created - A PDF report summarizing compliance is generated
- HTML plots show simulated vs reference curves
- Some tests may be marked as:
- Compliant
- Non-compliant (depending on the example and model behaviour)
Here, the system response is evaluated under predefined grid disturbance scenarios.
For detailed explanations and result interpretation, see: Performance verification
Run:
dycov performance -m examples/Performance/Single/WECC4B/Dynawo/This will:
- execute PCS test scenarios
- evaluate compliance with grid‑code requirements
Expected result:
- PCS test cases are executed
- Compliance is evaluated for each test scenario
- Tests are marked as:
- Compliant
- Non-compliant
- A summary report highlights pass/fail status per PCS, benchmark and operating condition
This optional workflow targets GFM units and computes admissible response envelopes.
For a complete description of this analysis workflow, see: Grid‑Forming (GFM) analysis
Run:
dycov generateEnvelopes -i examples/GFM/Overdamped/Producer.iniThis will:
- compute admissible envelopes
- generate CSV data and plots
Expected result:
- CSV files with envelope data
- Static PNG plots
- Interactive HTML plots for detailed inspection
The documentation is structured to progressively guide users from high-level concepts to detailed workflow configuration.
-
Installation guides:
-
Tutorials (guided learning path):
- Reading guide
- Conceptual overview
- Preparing inputs
- Understanding reports
- Workflow-specific tutorials:
These documents are intended to be used once you are familiar with the basic execution flow provided in the Quick start section.
Developer documentation is available separately and provides guidance on building, extending, and contributing to DyCoV:
- Key developer resources:
In addition to the online documentation, DyCoV provides local reference manuals installed with the software.
| Installation | Location |
|---|---|
| Linux native | ~/dycov/manual/ |
| Docker / WSL | ~/manual/ |
This section provides recorded sessions illustrating real usage of DyCoV workflows in practical studies.
Note: These videos were recorded with version 0.8.1. They remain valid, although some interface elements may have changed in more recent versions.
Workshop held on 2025-03-11 (English subtitles available in the download):
Part 1:
CAR_atelier_dycov_vost_720p_compressed_part1_vost.mp4
Part 2:
CAR_atelier_dycov_vost_720p_compressed_part2_vost.mp4
These sessions are particularly useful after completing the Quick start section.
Contributions are welcome. Please read CONTRIBUTING.md for branching conventions, code style, CI requirements, and the PR workflow.
The following roadmap outlines the main development directions currently guiding DyCoV evolution.
- Ongoing bug fixes and robustness improvements
Complete support for WECC and IEC models (PV, wind, BESS)— available since v1.1.0- Support for multi-generator topologies
- On-site measurement support for RMS model validation
Windows and Docker installation improvements— available since v1.1.0Migration of initialization layer to pypowsybl— postponed — Dynawo release-cycle blocker (details)Dynamic generation of topology schematics in reports— postponed — depends on pypowsyblExpanded test coverage and typing enforcement— available since v1.1.0Documentation and tutorials— available since v1.1.0
- Support for multiple DTR versions
- Update of fiches according to DTR 2025 revisions (I5)
- Implementation of fiche F16
- New GFM-related fiches (I18) with PPM/BESS differentiation
For questions, support, or contributions, please refer to the project repository or contact the maintainers.
- Electrical modeling inquiries (RTE): rte-r-d-raccordement@rte-france.com
- Software issues and questions (AIA): dycov@aia.es