Page tree
Skip to end of metadata
Go to start of metadata


Example 1 showed how to execute a test sequence that had only hardcoded values. Example 2 will focus on the use of variables to define some parameters in the model. This example will not go into much details regarding the blocks that were used in the first example. It is recommended to do the first example before this one.

The starting point is the end of the Quick Start tutorial (Link to the Quick Start tutorial). Your TestView should now look like Figure 88.

Starting Point: Example 2

This example will modify the resistance of Ld2 in the example HVAC_500kV_6Bus model following the equation

Where ‘index’ is the loop variable and User request will be a pop-up for the user to fill. This equation does not make any physical sense, but it demonstrates quite well how to use several blocks in TestView.

Similarly to example 1, let’s start by making sure that the options Start simulation and Disable Time Events are checked and unchecked, respectively in the HYPERSIM Settings block and let’s add a sleep of 1 second.

The next step is to add an ‘Assign’ block to initialize the variables that we will need for the equation. If the initialization is not done, the test will crash when trying to evaluate the equations for the first time. Fill the Assign block as shown in Figure 89 and press Apply.

The first variable is for the fault current, the second is for the timing of the fault, the third one is for the pop-up window for the user and the fourth is for the result. They are all defined to zero to make sure TestView sees them as numbers, not as strings.

Initialization of Variables

Similarly to the example 1, add a Miscellaneous block to force the General Operation option of the Fault breaker to ‘Enable’ and add a Snapshot block to take a snapshot (you can copy the blocks from the example 1 test and paste it in the example 2 test to save some time. The shortcuts do not work, you need to right-click on the blocks). Let’s add a second parameter, which would be the resistance of Ld2, to be sure it always starts at the same default value.

First Miscellaneous Block in Example 2

The next step is to add a loop block for the test, as shown in Figure 90. In this case, we will do four iterations in total, 2 for each part of the equation.

Loop Block in Example 2

Add a Snapshot block in the test to load a snapshot and a breaker block to set the timings for 4 different tests (see example 1). At this point, the test should now look like Figure 91.

Test After Adding the Breaker Block

At this point, it is time to handle the equation itself. The first part is to check if the index is smaller or bigger than 2 to find which of the two halves of the equation to use. In this case, we can use a If/else combo.

Double-click on the if expression in the Palette tab and add the expression in Figure 92. Press Apply to close the window.

If expression Dialog Box

In Figure 92, the %{} are essential for TestView to understand that it is a variable and not a literal string. TestView would crash if it tried to compare a string to an integer.

Double-click on the else [if(expression)] in the Palette tab to add the else block. Press Apply.

Add a message block under the if expression and under the else expression (you can uncheck the ‘pause’ option in both blocks).

The test should now look like Figure 93. Notice the indentations in Figure 93. If the blocks are not at the right indentations, move them using the arrows in the bottom part of the main TestView window.

Example 2 Test After Adding the Messages

At this point, it is possible to run the test to see if we made any mistakes. Run it by going in the Runner tab, select the ‘Current test only’ and press play.

In the console, you can see the messages being displayed, as shown in Figure 94.

Snippet from the Console Showing that the If and Else is Working

To continue, in the if expression, we need to implement the first half of the equation:

Therefore, we need to ask a value to the user to enter: i.e. to add the Input Value block. To do so, double-click on the Input Value block in the Palette tab and add ‘user_value’ in the field. Press Apply.

Input Value Dialog Box for Example 2

Notice that no %{} were used to surround the name of the variable. The Input Value block requests for a symbol (i.e. a variable).

You can run again the test sequence. Notice that the pop-up window appears only twice out of four iterations because it is in the if expression (therefore true for index 0 and 1 only).

To continue, we are now at the step of calculating the value of RLd2. For the first iteration, there are no previous test, therefore the ‘maximum fault current from previous test’ will simply be the default value 0.

To calculate RLd2, we have the choice between the Eval block and the Expression block (both will work in this case). Let’s take the Eval block and add the following in the field:

Eval Expression for Index 0 and 1


In the else part of the test, let’s add another block to calculate RLd2 for index 2 and 3. Recall that the equation is:

Just for the pedagogical aspect of it, let’s use the Expression block instead of the Eval block for this one.

To add the Expression block to the Test, simply double-click on Expression in the Palette tab and fill the dialog box as presented in Figure 97. Pres Add and then Apply.

Expression Dialog Box for the Else part of the Script

The script should now look like Figure 98.

Example 2: Once the Equation is Completely Defined

To make a quick recap of the test up to now: it sets the connections to the model, enables the fault block, takes a snapshot of the steady-state conditions (prior to any fault) then iterates four times. In each iteration, it loads the snapshot, defines the timing for the fault and calculates the value of RLd2 based on the given equation.

What is left to do is to set RLd2 using the result from the equation, to run the tests and to update the variables after each test.

To set RLd2, double-click on Miscellaneous in the Palette tab, and fill the dialog box as presented below. Make sure that you select the Ld2 and R from the dropdown list (and not hardcoding them). Recall that if the lists are empty, it means that there is a connection problem between TestView and HYPERSIM.

Setting the Resistance of Ld2

The block should be inside the loop but not inside the if or the else expression. Use the arrows to move the block at the right place.

(Left) Block is Not in the Right Place! (Right) Block is in the Right Place

To continue, the next step is to add a processing block (the one in the Main folder of the Palette tab). A shortcut is to copy the one from Example1 and build from it. If you are starting with a new block, don’t forget to create a Signals Key (see Example 1).

We need the maximum current of phase A and the crossing time of the fault. To have those, go in the processing tab of the block and add the following. The functions used are from ScopeView. Please refer to the ScopeView User Manual for more details regarding those.

Selected Signals from Processing Tab of Processing Block.

Then, go to the post-processing tab and add the two results to see them. This way, we will see the evolution throughout the four iterations.

Selected Signals from Post-Processing Tab of the Processing Block

Finally, go back to the general tab and make sure the ‘Show Graphic’ option is set for both the processing and the post-processing option.

General Tab of the Processing Block

The last block to add is the Expression one to update the variables. Add the block and fill the dialog box as follow:

Second Expression Block in Example 2 to Update the Variables

The test should now look like:

Example 2 - Complete Test

To run the test, go in the View tab, check ‘Show’ in the processing and post-processing sections. Go in the runner tab and press play.

WARNING: Do you enter 0 (nor negative) as the user value, it gives a resistance of 0 (or negative), which will make the test crash!

When you run the test, you should see waveforms like in Figure 107. The waveforms depend on the entered value.

Figure 108 shows the waveforms for the post-processing part. There should be four points per graphs because there were four iterations executed. Post-Processing is a way to compare the results from different tests rapidly.

Typical Processing Waveforms for Example 2

Typical Post-Processing Waveforms for Example 2


  • No labels