Model Configuration Parameters: Data Validity
The Diagnostics > Data Validity pane of the Configuration Parameters dialog box includes parameters for detecting issues related to model data, such as signals, parameters, and states in a model. These issues include:
Loss of information due to data type quantization and overflow
Loss of parameter tunability in the generated code
Loss of data due to the order in which Data Store Write and Data Store Read blocks execute
To open the Diagnostics > Data Validity pane of the Configuration Parameters dialog box:
To open the Configuration Parameters dialog box, in the Simulink® Toolstrip, on the Modeling tab, under Setup, click Model Settings.
In the Configuration Parameters dialog box, click the arrow next to Diagnostics to expand the list. Then, select Data Validity.
The tables summarize the parameters available on the Diagnostics > Data Validity pane of the Configuration Parameters dialog box.
Signals
Parameter | Description |
---|---|
Option to specify how model resolves signals and states to
| |
Diagnostic action to take if the Matrix Multiply block detects singular matrix | |
Diagnostic action to take if the software is unable to infer signal data type | |
Diagnostic action to take if block produces
| |
Diagnostic action to take during code generation if parameter,
block, or signal name begins with
| |
Diagnostic action to take if signal value overflows data type value range | |
Diagnostic action to take if signal value is too large for signal data type | |
Diagnostic action to take if the software is unable to infer signal dimensions | |
Diagnostic action to take when signal value is outside its specified value range | |
Diagnostic action to take if string signal value is truncated |
Parameters
Parameter | Description |
---|---|
Diagnostic action to take if the software detects parameter overflow | |
Set a threshold of one bit, half bit, or zero bits for parameter overflow detection. | |
Diagnostic action to take if the software detects parameter precision loss | |
Suppress the double to single parameter precision loss detection | |
Report parameter precision loss when the quantization error exceeds both absolute and relative difference thresholds | |
Report parameter precision loss when the quantization error exceeds both absolute and relative difference thresholds | |
Diagnostic action to take if the software detects parameter underflow | |
Diagnostic action to take if code generation reduces expression with tunable variables to numeric equivalent | |
Diagnostic action to take when parameter downcast occurs during code generation |
Data Store Memory block
Diagnostic action to take if model reads from data store before writing to that data store in current time step | |
Diagnostic action to take if model writes to data store after reading from data store in current time step | |
Diagnostic action to take if model writes to data store twice in current time step | |
Diagnostic action to take when task reads from data store to which another task writes | |
Diagnostic action to take if model contains multiple data stores with same name |
These configuration parameters are in the Advanced parameters section.
Parameter | Description |
---|---|
Detect multiple driving blocks executing at the same time step | Diagnostic action to take when execution order is not defined for blocks that drive same Merge block in same time step |
How to determine initial conditions for subset of Simulink blocks that have underspecified initial conditions | |
Diagnostic action to take when S-function writes beyond array bounds assigned in allocated memory | |
Option to enable or disable model verification blocks | |
Diagnostic action to take when code generation cannot reuse
| |
Detect ambiguous custom storage class final values | Diagnostic action to take when |
Option to enable parameter validation globally or locally |