Documentation

Model Configuration Parameters: Diagnostics

The Diagnostics category includes parameters for detecting issues related to solvers and solver settings, for example, algebraic loops.

ParameterDescription

Algebraic loop

Select the diagnostic action to take if Simulink® software detects an algebraic loop while compiling the model.

Minimize algebraic loop

Select the diagnostic action to take if artificial algebraic loop minimization cannot be performed for an atomic subsystem or Model block because an input port has direct feedthrough.

Block priority violation

Select the diagnostic action to take if Simulink software detects a block priority specification error.

Min step size violation

Select the diagnostic action to take if Simulink software detects that the next simulation step is smaller than the minimum step size specified for the model.

Consecutive zero-crossings violation

Select the diagnostic action to take when Simulink software detects that the number of consecutive zero crossings exceeds the specified maximum.

Automatic solver parameter selection

Select the diagnostic action to take if Simulink software changes a solver parameter setting.

Extraneous discrete derivative signals

Select the diagnostic action to take when a discrete signal appears to pass through a Model block to the input of a block with continuous states.

State name clash

Select the diagnostic action to take when a name is used for more than one state in the model.

SimState interface checksum mismatch

Use this check to ensure that the interface checksum is identical to the model checksum before loading the SimState.

These configuration parameters are in the Advanced parameters section.

ParameterDescription

Allow symbolic dimension specification

Specify whether Simulink propagates dimension symbols throughout the model and preserves these symbols in the propagated signal dimensions.

Allowed unit systems

Specify unit systems allowed in the model.

Units inconsistency messages

Specify if unit inconsistencies should be reported as warnings. Select the diagnostic action to take when the Simulink software detects unit inconsistencies.

Allow automatic unit conversions

Allow automatic unit conversions in the model.

Check runtime output of execution context

Specify whether to display a warning if Simulink software detects potential output differences from previous releases.

Check undefined subsystem initial output

Specify whether to display a warning if the model contains a conditionally executed subsystem in which a block with a specified initial condition drives an Outport block with an undefined initial condition.

Solver data inconsistency

Select the diagnostic action to take if Simulink software detects S-functions that have continuous sample times, but do not produce consistent results when executed multiple times.

Block diagram contains disabled library links

Select the diagnostic action to take when saving a model containing disabled library links.

Block diagram contains parameterized library links

Select the diagnostic action to take when saving a model containing parameterized library links.

InitInArrayFormatMsg

Message behavior when the initial state is an array

Combine output and update methods for code generation and simulation

When output and update code is in one function, force simulation execution order to be the same as code generation order. For certain modeling patterns, setting this parameter prevents a potential simulation and code generation mismatch. Setting this parameter might cause artificial algebraic loops.

Related Topics

Was this topic helpful?