Dummy Test System description - ID123

This test system page can be used as template for your own test system. If you want to download this page in qmd format, click here:

Download test system template

Important

_Do not provide the title here (to avoid duplicate display) as it should be included in the Metadata block. We recommend including the issue ID generated by Colib GitHub along with the title. A test case includes a network test system with static and dynamic models for each element, some input data, and some scenarios. Each test case must be specific enough to be added in a new page. In other words, it means that the test case should be significatively different from existing standard test cases (either by its network topology, generation mix, static data values), either by its operating point, either by the phenomena/event it tackles. The differences with existing well-known test cases should be clearly explained.

Use case purpose​ and context (mandatory)

This section aims at explaining the main purpose of the test case, the reason why it was built. The history behind the test case can also be given for clarity.

Example

The Kundur two area system is a test system for studies on dynamic stability, oscillations, damping, power exchange and other use cases. It is a widely used standard test case defined in [1] (Figure 1).

Network ​description (mandatory)

This section gives the overview of the network test system. A grid map, an electrical circuit diagram, can be provided as well as some extra explanations of the network (chart labels, symbols, generation mix, consumption level, etc.).

Note

For electrical circuit diagram, we can use draw.io plugin for github allowing you to make your own diagram easily. The diagram is fully editable with github commit using a graphical interface, and allowing multiple format outputs (for more details, see: draw.io github) If you want to use a picture, please use Scalable Vector Graphics (SVG) file format.

Example

The test system is shown Figure 1. As [1] describes it, it consists of two similar areas connected by a weak tie.

The parameters are listed in Section 4. The system consists of 11 buses connected by lines or transformers. There are 4 generators G1…G4, two loads L7 and L9 as well as two shunt capacitors C7 and C9.

Figure 1: Kundur two area test system

Static and Dynamic models​ description (mandatory)

This section lists the different elements of the network test system.

Note

To avoid moo much information on the same page, some links to the elements model’s pages can be provided.

Example

This test case includes the following components: […]

AVRs

The following AVRs are used in this test system, depending on the used scenario:

• no AVR: Manual excitation, i.e. constant field voltage
• AVR DC1A (similar to DC1C, see colib page here)
  • \(K_\mathrm{a}=\) 20 pu
  • \(K_\mathrm{a}=\) 200 pu
• AVR ST1A (similar to ST1C, see colib page here)
  • (with/without transient gain reduction (TGR) and/or power system stabilizer (PSS))

For details on the scenarios, see Section 6.

Input Data (mandatory)

This section includes all the needed input data the test case needs to be run. It includes: static data for the network, dynamic data for each dynamic element component, load flow values, initial states of dynamic variables.

If the network is too big, input data can be provided by uploading data files directly in the page. The data files should be understandable and contains unit information. Example: Data

Example

Table 1: Synchronous machine parameters

parameter	value	pu base
\(A_\mathrm{Sat}\)	0.015	-
\(B_\mathrm{Sat}\)	9.6	-
\(H\)	6.5 s (for G1 and G2) and 6.175 pu (for G3 and G4)	-
\(K_\mathrm{D}\)	0	-
\(\Psi_\mathrm{T1}\)	0.9	-
\(R_\mathrm{a}\)	0.0025 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(S_\mathrm{r\,SM}\)	900 MVA	-
\(T_\mathrm{d0}'\)	8.0 s	-
\(T_\mathrm{d0}''\)	0.03 s	-
\(T_\mathrm{q0}'\)	0.4 s	-
\(T_\mathrm{q0}''\)	0.05 s	-
\(U_\mathrm{n\,SM}\)	20 kV	-
\(X_\mathrm{d}\)	1.8 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{d}'\)	0.3 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{d}''\)	0.25 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{l}\)	0.2 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{q}\)	1.7 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{q}'\)	0.55 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)
\(X_\mathrm{q}''\)	0.25 pu	\(U_\mathrm{n\,SM}^2 / S_\mathrm{r\,SM}\)

Scenarios (at least one mandatory)

This section explains the scenario that is played on the previous described system.

Scenario No. XX / Name

gives a number or/and a name to the scenario.

In this paragraph, all the information that is required to run the test and that the previous section hasn’t covered should be included in the scenario description. If no additional information is required, this section can be left empty.

Below the type of information that can be useful for the reader:

• Event gives a description of the event and the time of the event.

• Operating point No. X If the operating point differs from the load flow values provided before, the change in the operating point should be precised here.

• Control modes if specific control modes are used for the scenario, it should be detailed here.

• Network variant if slight changes are made in the network configuration, topology, mix, dynamic data, etc. those changes can be described here.

Simulation parameters (optional)

The section gathers the main simulation parameters used to run the case.

Example

Parameter	value
Type of problem	DAE
Solver name	IDA
Computing method	variable-order, variable-coefficient Backward differentiation formula in fixed-leading-coefficient form
Time step	5 ms
Simulation duration	5 s

Outputs (mandatory)

The section presents the key outputs of the simulation by providing figures, curves, and text.

The results should be interpreted to the extent possible. The plots can be provided in various forms.

Open source implementations (if any)

This section give a list of the different open source implementations of this model. It provides the reader with links and languages/software used for each implementations. A markdown table can be used to display such list.

Example:

This model has been successfully implemented in :

Software	URL	Language	Open-Source License	Last consulted date	Comments
Software name	Link	modelica	MPL v2.0	XX/0X/20XX	Comments can contain implementations details such as validation means, implementations key choices, etc.

Table of references & license

This section lists all the references. It must comply with current citation standards. Quarto uses BibTeX for managing reference.

1.

(2007) Power system stability and control. McGraw- Hill