Model Configuration Parameters: Data Validity Diagnostics
TheDiagnostics>Data Validitycategory includes parameters for detecting issues related to data (signals, parameters, and states). These issues include:
Loss of information due to data type quantization and overflow.
Loss of parameter tunability in the generated code.
Loss of information due toData Store WriteandData Store Readblock ordering.
On the Configuration Parameters dialog box, the following configuration parameters are on theData Validitypane.
Parameter | Description |
---|---|
Select how Simulink®software resolves signals and states to |
|
Select the diagnostic action to take if theProductblock detects a singular matrix while inverting one of its inputs in matrix multiplication mode. |
|
Select the diagnostic action to take if Simulink software could not infer the data type of a signal during data type propagation. |
|
Select the diagnostic action to take when signals exceed specified minimum or maximum values. |
|
Select the diagnostic action to take if the string signal is truncated. |
|
Select the diagnostic action to take if the value of a signal overflows the signal data type and wraps around. |
|
Select the diagnostic action to take if the value of a signal is too large to be represented by the signal data type, resulting in a saturation. |
|
Select the diagnostic action to take if the value of a block output is |
|
Select the diagnostic action to take during code generation if a Simulink object name (the name of a parameter, block, or signal) begins with |
|
Select the diagnostic action to take when a parameter downcast occurs during simulation. |
|
Select the diagnostic action to take if a parameter overflow occurs during simulation. |
|
Select the diagnostic action to take when a parameter underflow occurs during simulation. |
|
当参数选择诊断操作r precision loss occurs during simulation. |
|
Select the diagnostic action to take when an expression with tunable variables is reduced to its numerical equivalent in the generated code. |
|
如果模型选择诊断操作attempts to read data from a data store to which it has not written data in this time step. |
|
如果模型选择诊断操作attempts to write data to a data store after previously reading data from it in the current time step. |
|
如果模型选择诊断操作attempts to write data to a data store twice in succession in the current time step. |
|
Select the diagnostic action to take when one task reads data from aData Store Memoryblock to which another task writes data. |
|
Select the diagnostic action to take when the model contains multiple data stores that have the same name. The data stores can be defined withData Store Memoryblocks or |
These configuration parameters are in theAdvanced parameterssection.
Parameter | Description |
---|---|
Enable live streaming of selected signals to Simulation Data Inspector |
|
Enable model verification blocks in the current model either globally or locally. |
|
Detect multiple driving blocks executing at the same time step |
Select the diagnostic action to take when the software detects a Merge block with more than one driving block executing at the same time step. |
Select how Simulink software handles initialization of initial conditions for conditionally executed subsystems, Merge blocks, subsystem elapsed time, and Discrete-Time Integrator blocks. |
|
Detect if a signal using a Reusable custom storage class does not have a unique endpoint. The run-time environment should not read the variable because its value is ambiguous. |
|
Detect if a signal uses a Reusable custom storage class that the code generator cannot reuse with other uses of the same Reusable custom storage class. If the code generator cannot implement reuse, the generated code will likely contain additional global variables. |