standard channel configuration
All relevant channels (which depend on the selected test) need to be defined in a tabular way. The default definition at the program startup can be configured in the global configuration manager.
Each channel requires the data in a specified format (unit, class, size). More information about each channel can be found in the tooltip or it the context menu.
You can either specify a path within the file, or use MATLAB Code to input the data directly.
MXeval will always try to interpret the "Path/Value/Code" as a path to a variable. If this fails, MXeval will try to interpret "Path/Value/Code" as MATLAB code (see Custom Code Limitations)!
The general translation of the channel data is the following:
Channel [Unit] = Path * Multiplier
This only works for .mat, .erg and .mdf files. When using other files for the evaluation, please use a custom channel configuration script.
Option 1: Specify path
You have two options to specify the channel path
double-click the channel name or click "read channel from file" to open the channel selector and simply select the corresponding data channel to assign it. This channel selector analyses the first file from the data input and reads out all contained variables. This channel selector cannot read fields from non scalar struct variables. Those have to be defined manually!
The Column "Path/Value/Code" is editable and can be configured manually. It will also be interpreted as MATLAB code. (see Custom Code Limitations) Examples:
|
Option 2: Use MATLAB code
Use MATLAB code directly to create the channel data. this can help when a channel is missing or if you want to change the channel data without changing the original file. (see Custom Code Limitations)
Examples:
1.8 |
[0:0.001:20] |
zeros(1,20) |
linspace(1,20,1000) |
Category
The first column indicates the category of the channel:
internal required channel |
This channel always need to be supplied, otherwise MXeval cannot perform the evaluation. |
internal optional channel |
This channel can be unspecified. It is not mandatory for the evaluation to run. The KPI values that refer to this channel won't be calculated. |
custom channel |
Custom channel. This channel will be handled as optional. |
Multiplier
Apply a specific multiplier, e.g to correct signs or convert units.
The content of the multiplier field will be interpreted as MATLAB code (see Custom Code Limitations).
Examples:
1 |
180/pi |
-0.0175 |
1e-3 |
MXeval also has a list of predefined multipliers integrated, which can be accessed via the "Apply multiplier" button or the context menu.
Filter
MXeval has predefined filters which can be parameterized and assigned to each channel independently.
The following filters are integrated in MXeval's filter designer:
|
Filtering only works for 1D numeric nonscalar data.
Filtering requires the "Path/Value/Code" field to already be configured.