This panel describes the simulation options.
Before starting the simulation, it is useful to check some parameters in the Simulation Options window.
It allows users to specify the following parameters:
|Target||Target IP or hostname on which to load and execute the simulation the simulation. This is typically an OPAL-RT simulator embedding a Linux operating system. The drop-down box lists every target previously setup in the Target Manager. The button on the right is a shortcut to open the Target Manager and focus on the selected target.|
Real-Time Accelerated (RTA) is a type of offline (or non real-time) simulation that runs as fast as possible, which means that the actual execution time is usually much faster than real-time depending on the PC specifications. All I/O are not initialized in this mode.
Real-Time runs a standard real-time simulation where all I/O are available.
|Architecture||Non-editable field. It informs on the package version of the operating system used on the target simulator.|
|Time-step||Size of the discretization used by all equations. The execution is in real-time if the performance factor = 1, faster than real-time if the performance factor < 1, and slower if the performance factor > 1.|
This parameter can be used for optimizing and debugging purposes in real-time mode. It helps altering the actual execution time by a specified factor and is usually used to slow down the simulation when more time is needed to compute all equations than what the time step allows.
Step duration = performance factor * simulation time step
For example, a time step of 50 μs with a performance factor of 2 will give the simulation 100 μs to complete calculations (while the size of the discretization remains 50 μs) and exchange I/Os. Since I/Os are only exchanged between two calculations, it would also mean that their output frequency is slowed down as well to every 100 μs. In other words, with a performance factor > 1, the processors have more time, and heavy tasks can be completed before I/Os have to be exchanged again, and thus overruns can be avoided.
To illustrate the behaviour, say a sine wave is observed on a real oscilloscope, its period is equal to the product of the performance factor and the real period. This is like playing a video in slow motion.
|Code directory||Before the simulation, HYPERSIM® generates C code specific to each network. This parameter is used to define the directory where the code is saved. This parameter will be set automatically depending on the chosen target.|
|Enable simulation logging|
For debugging purposes, add more information to the simulation log file (*.simout).
WARNING: this decreases real-time performance.
If checked, a transceiver component will automatically be added in all locations where it is needed to succeed in mapping tasks.
|Perform load flow||If checked, the load flow algorithm will be executed and initial conditions set every time the simulation is started. Otherwise, the load flow must be executed manually via the HYPERSIM® ribbon.|
|Activate iterative method|
Enable the iterative solver for non-linearities and zero-crossing. It is enabled on a task-by-task basis depending on the following:
To activate iteration for all components, check Apply to all nonlinear elements.
WARNING: if the precision valve parameter is enabled in a switch, it disables the iteration for all components within the same task.
|Maximum iterations||Limit the maximum number of iterations at each step. There is a trade-off between precision and computation time.|
|Apply to all nonlinear elements||Override individual components' iteration parameter and activate iteration for all components.|
Advanced Target Settings
This tab allows to override the target's general advanced settings, which are described here.