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 |
---|---|
Diagnostic action to take when the software detects algebraic loop during compilation | |
Diagnostic action to take when the software is unable to resolve artificial algebraic loops | |
Diagnostic action to take when the software detects block priority specification error | |
Diagnostic action to take when minimum step size violation occurs | |
Diagnostic action to take when zero-crossing violation occurs | |
Diagnostic action to take when the software changes a solver parameter value | |
Diagnostic action to take when more than one state has same name |
These configuration parameters are in the Advanced parameters section.
Parameter | Description |
---|---|
Option to propagate symbolic dimensions throughout model | |
Option to issue warning when models contain conditionally executed subsystems with undefined initial output values | |
Option to automatically convert units that have known mathematical relationship | |
Option to specify supported unit systems for model | |
Diagnostic action to take when model contains unit inconsistencies | |
Diagnostic action to take when S-function with continuous sample time produces inconsistent results | |
Diagnostic action to take when solver ignores zero crossings in simulation | |
Diagnostic action to take when the software detects masked zero crossings | |
Diagnostic action to take when initial state for model is specified as array | |
Diagnostic action to take when maximum identifier length is too short to ensure unique global identifiers | |
Diagnostic action to take when saving a model that contains disabled library links | |
Diagnostic action to take when saving a model that contains parameterized library links | |
Diagnostic action to take if model interface checksum does not match interface checksum of initial operating point | |
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 |
Option to enable debug execution mode for FMU Import blocks | |
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 |
Diagnostic action to take when variant modeling issues might cause creation of unused variables in generated code | |
Diagnostic action to take when variant configuration of a top model does not use an existing variant configuration of a referenced model |