Model Configuration Parameters: Diagnostics

The Diagnostics pane includes parameters that specify the diagnostic action to take when the software detects issues related to solvers and solver settings.

Parameter	Description
Algebraic loop	Diagnostic action to take when the software detects algebraic loop during compilation
Minimize algebraic loop	Diagnostic action to take when the software is unable to resolve artificial algebraic loops
Block priority violation	Diagnostic action to take when the software detects block priority specification error
Min step size violation	Diagnostic action to take when minimum step size violation occurs
Consecutive zero-crossings violation	Diagnostic action to take when zero-crossing violation occurs
Automatic solver parameter selection	Diagnostic action to take when the software changes a solver parameter value
State name clash	Diagnostic action to take when more than one state has same name

These configuration parameters are in the Advanced parameters section.

Parameter	Description
Allow symbolic dimension specification	Option to propagate symbolic dimensions throughout model
Check undefined subsystem initial output	Option to issue warning when models contain conditionally executed subsystems with undefined initial output values
Allow automatic unit conversions	Option to automatically convert units that have known mathematical relationship
Allowed unit systems	Option to specify supported unit systems for model
Units inconsistency messages	Diagnostic action to take when model contains unit inconsistencies
Solver data inconsistency	Diagnostic action to take when S-function with continuous sample time produces inconsistent results
Ignored zero crossings	Diagnostic action to take when solver ignores zero crossings in simulation
Masked zero crossings	Diagnostic action to take when the software detects masked zero crossings
Initial state is array	Diagnostic action to take when initial state for model is specified as array
Insufficient maximum identifier length	Diagnostic action to take when maximum identifier length is too short to ensure unique global identifiers
Block diagram contains disabled library links	Diagnostic action to take when saving a model that contains disabled library links
Block diagram contains parameterized library links	Diagnostic action to take when saving a model that contains parameterized library links
Operating point interface checksum mismatch	Diagnostic action to take if model interface checksum does not match interface checksum of initial operating point
Operating point contents checksum mismatch	Diagnostic action to take if model contents checksum does not match contents checksum of initial operating point
Combine output and update methods for code generation and simulation	Option to require same execution order for simulation and generated code
Behavior when pregenerated library subsystem code is missing	Diagnostic action to take when model cannot use pregenerated library code or pregenerated library code is missing
Behavior when a matching unit test for subsystem reference is missing	Diagnostic action to take when subsystem reference signature does not match any unit test signature
FMU Import blocks	Option to enable debug execution mode for FMU Import blocks
Arithmetic operations in variant conditions	Diagnostic action to take when variant condition values include arithmetic operations
Variant activation time inherited from Simulink.VariantControl	Diagnostic action to take when variant blocks that inherit activation time from Simulink.VariantControl have no value to inherit
Variant condition mismatch at signal source and destination	Diagnostic action to take when variant modeling issues might cause creation of unused variables in generated code
Variant configuration not used by top model	Diagnostic action to take when variant configuration of a top model does not use an existing variant configuration of a referenced model