Documentation Home Page ◇ HYPERSIM Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.
Data Logger Configuration
Recording mode | The default data logger state when the simulation starts. | |
Automatic | Acquisition starts when simulation starts. | |
Manual | Acquisition starts when the user starts the signal group in the Signal Groups view. | |
Show data logger console | Unchecked by default. Allows our support team to collect more information in case debugging is required. | |
Configuration Mode | Basic | Default mode |
Advanced | Enables activating the data logger console | |
No data loss | Enables the data logger to be master to the simulation if an offline simulation mode of execution is selected. It can’t be used in real-time mode. The simulation will run as fast as the data logger can save data. |
By default, one signal group is created for the data logger. A signal group is defined as a set of signals to be acquired when the specific trigger condition of this signal group is encountered. Therefore, users can define multiple trigger conditions that trigger various acquisitions that may or may not share the same triggering signals. Each signal group stores signals in its own data file.
To create more signal groups, click the initial Signal Groups folder in the left panel. This panel provides a summary of each signal group configuration.
To add a signal group, click any of the Add 1 item buttons (1), depending on if you want to add it Above or Below the selected Signal Group. The arrow next to each button provides more options (duplicate signal groups and/or add multiple groups at once).
You can remove one or several groups (2), or reorder them by using the arrow buttons (3).
Each signal group can be configured from the previous window or from each individual signal group window. (Click on each signal group in the left panel to access their window.)
Name | Name of the signal group. | |
Recording mode | Default state when simulation is starting for the signal group. | |
Inherit | The same state as the one described in the general Data Logger view. | |
Automatic/Manual | The state which will override the one described in the general Data Logger view. | |
Export format | File extension created by the data logger. For the moment, only .oprec is available. | |
Output file auto naming | Defines the output data file name automatically and prevents file name collisions. The name format is SignalGroupName_ecfName_TimeStamp. Example: SIGNAL_GROUP_1_HVAC_500kV_6Bus_20190423_105021. | |
If you deactivate the auto-naming, you can configure: | ||
---|---|---|
Output filename | Name of the file that contains the signals' data. Make sure all signal groups have unique file names. Otherwise, files overwrite one another. If a complete or relative path and file name are provided, all intermediate folders are created when required. | |
Decimation factor | Number of steps recorded = total number of steps divided by the decimation ratio. When set to 1, the samples from each calculation step are stored. When set to 2, the samples from each 2 calculations are stored, etc. | |
Frame length | Duration for which samples are stored once a trigger occurs. | |
Frame length unit | May be either a number of steps, a duration in various time units ranging from nanoseconds to hours, or a file size in megabytes | |
Number of frames to record | Specifies how many frames to record. Note that there is no data loss within a frame but it may happen between frames. | |
Show trigger configuration | Provides access to trigger configuration parameters: | |
Trigger level | Level value that will activate the trigger. | |
Trigger function | The trigger is active on an edge or level event. | |
Trigger polarity | Negative or positive. When triggering an on-edge event, it specifies whether the trigger is to occur on a rising (positive) or falling (negative) edge around the specified trigger value. | |
Pre-trigger percentage | Percentage of the record length to be logged before the occurrence of the trigger condition. Example: For 25%, write 25.0. | |
Trigger holdoff | After the occurrence of a trigger condition, specifies the duration for which all subsequent trigger events will be ignored. Uses the unit specified in Frame length units. |
OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter