Model Configuration Parameters: Diagnostics
The Diagnostics category includes parameters for configuring the diagnostic behavior when the software detects issues related to solvers and solver settings, such as algebraic loops.
Select the diagnostic action to take if Simulink® software detects an algebraic loop while compiling the model.
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.
Select the diagnostic action to take if Simulink software detects a block priority specification error.
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.
Select the diagnostic action to take when Simulink software detects that the number of consecutive zero crossings exceeds the specified maximum.
Select the diagnostic action to take if Simulink software changes a solver parameter setting.
(To be removed) 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.
Select the diagnostic action to take when a name is used for more than one state in the model.
Use this check to ensure that the interface checksum is identical to the model checksum before loading the OperatingPoint.
These configuration parameters are in the Advanced parameters section.
Specify whether Simulink propagates dimension symbols throughout the model and preserves these symbols in the propagated signal dimensions.
Specify unit systems allowed in the model.
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 in the model.
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.
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.
|Select the diagnostic action to take if Simulink detects zero-crossings that are being ignored.
Select the diagnostic action to take if Simulink detects zero-crossings that are being masked.
Select the diagnostic action to take when saving a model containing disabled library links.
Select the diagnostic action to take when saving a model containing parameterized library links.
Message behavior when the initial state is an array.
For referenced models, specify the diagnostic action to take when the character length specified in the configuration parameter Maximum identifier length is not sufficient to make global identifiers unique across models.
When output and update code is in one function, force the simulation execution order to be the same as the 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.
|Behavior when pregenerated library subsystem code is missing
|When generating code for a model that contains an instance of a reusable library subsystem with a function interface, specify whether to display a warning or an error when the model cannot use pregenerated library code or pregenerated library code is missing.
|Behavior when a matching unit test for subsystem reference is missing
|When using strong unit testing features to verify use of subsystem reference block in model, specify whether to display a warning or error when matching unit test signatures are not found.
|When the debug execution mode is enabled, FMU binaries are executed in a separate process.
Specify the diagnostic action to take when arithmetic operations are found in variant conditions.
|Variant condition mismatch at signal source and destination
|Specify the diagnostic action to take when there are variant-related modeling issues that may result in unused Simulink variables in the generated code.
|Variant activation time inherited from Simulink.VariantControl
|Specify the diagnostic action to take when a variant block with
its activation time set to
Simulink.VariantControl has no variant control
variable of type
|Variant configuration not used by top model
Specify the diagnostic action to take when Simulink detects during simulation or Variant Manager activation that a top-level model does not use a referenced model for any of the published variant configurations of the referenced model.