This chapter will focus on the HYPERSIM ribbon that we overviewed in section 2.2.6. The ribbon is segmented into seven sub-categories (Tools, Target, Import, Sensors, Network, Simulation and Help) and each one can contain several actions.
Left-Clicking on the button “Target” will open the Target options window. This window consists of three tabs “Version”, “Licensing” and “Shared Folders”.
- The “Host” drop-down box lists all the targets that you previously setup and used. By selecting one, you can edit its configuration.
- You can also add a new target to the list by typing the IP address or the hostname of a Target on your network (we recommend using the IP address). HYPERSIM® will then check the availability of the target. The Host area displays the confirmed IP address and version numbers for Hycore:
In the case of a properly configured target:
In the case of an un-configured or unreachable target:
|Version||This tab allows you to install the current version to the simulation, uninstall a version or switch to another version. Please note that you can only use a version on the target that matches the version currently used on the host.|
|Licensing||This tab allows you to see the Machine ID for the selected target, save it to a file and install a license on the simulator.|
|Shared Folders||This tab allows youto configure the path of the folders shared between the host and all the previously configured targets.|
Before starting the simulation, it is useful to check some parameters in the Simulation Options window. It allows users to specify the following parameters:
|Architecture||Real-Time Accelerated simulation, or RTA, will run as-fast-as-possible: the actual Time Step will typically be smaller than the specified one. This simulation mode is useful for debugging your network. Some drivers will be disabled in RTA, thus all I/O will not be available. Real-Time will run a standard real-time simulation, all I/O will be available.|
|Target||Target IP or hostname that will be executing the simulation. This is typically an OPAL-RT simulator embedding a Linux operating system. The drop-down box lists every target previously setup in HYPERSIM>Target.|
|Time Step||The Time Step can be set in seconds, milliseconds, microseconds or nanoseconds (respectively “s”, “ms”, “μs”, and “ns” in the small drop-down box). HYPERSIM® uses this parameter to set the simulation equations. However, in real-time mode, waveform execution is altered by Performance. The execution is in real-time if performance factor = 1, faster than real-time if performance factor < 1, slower if performance factor > 1.|
|Performance Factor||This parameter serves to slow down in real-time by a specified factor. For example, if the user observes a sine wave on a real oscilloscope, its period will be equal to the product of the performance factor and the real period. This is like playing a video in slow motion. With a performance factor > 1, the time allocated for each time-step will be (performance factor * time step), therefore the CPUs have more time, and more tasks can be allocated on each CPU.|
In offline simulation (non-real-time mode) with a single CPU, HYPERSIM® still emulates the real-time mode, a large number for Performance could be required to enable the simulation.
|CPU load level||Task mapping will distribute the tasks in order to match the specified CPU usage. Use a value between 0 and 1.|
|Enable simulation logging||For debugging purposes, add more information to the simulation log file (*.simout). WARNING: this decreases real-time performance.|
|Enable automatic transceiver||If checked, automatic transceiver block will be added where needed.|
If unchecked and a transceiver is needed, an error message specifying the location were its needed will be displayed.
|Code Directory||Before simulation, HYPERSIM® generates a code C 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 target you chose.|
|Activate iterative method|
Enable the iterative solver for nonlinearities 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 tradeoff between precision and computation time.|
|Apply to all nonlinear elements||Override individual components' iteration parameter and activate iteration for all components.|
The Sensors sub-category in the HYPERIM ribbon will help you manage the sensor configuration of the active model.
|Clear||If the active model has selected sensors (you can check in “Selected Summary”), left-clicking on this button will deselect them.|
|Save||This button allows you to save the sensor configuration of the active model in a “.sig” file that you have to specify if this is the first time you save or if you did not open an existing configuration.|
|Save As||This button allows you to save the sensor configuration of the active model in a specific “.sig” file (a similar window will ask you for a path and filename).|
|Open Config||It will ask you to specify a sensor configuration file (“.sig”) that will be loaded on the active model. Be advised that any existing configuration will be discarded by this action.|
|Add to Config||Clicking on this button will also ask you to specify a “.sig” file but, as opposed to the “Open Config” action, the previous configuration is kept (merged) with the new one.|
|Selected Summary||Left-clicking on this button will open the sensor configuration summary for the active model. This window consists of a list of every sensor that is selected in your design. You can review or edit them. The two buttons allows you respectively to select and deselect every sensors in the summary.|