Accelerating the pace of engineering and science

# Documentation

## Diagnostics Pane: Data Validity

### Data Validity Diagnostics Overview

Specify what diagnostic action Simulink® software should take, if any, when it detects a condition that could compromise the integrity of data defined by the model, as well as the Data Validity parameters that pertain to code generation, and are used to debug a model.

#### Configuration

Set the parameters displayed.

#### Tips

• To open the Data Validity pane, in the Simulink Editor, select Simulation > Model Configuration Parameters > Diagnostics > Data Validity.

• The options are typically to do nothing or to display a warning or an error message.

• A warning does not terminate a simulation, but an error does.

### Signal resolution

#### Settings

Default: Explicit only

Explicit only

Do not perform implicit signal resolution. Only explicitly specified signal resolution occurs. This is the recommended setting.

Explicit and implicit

Perform implicit signal resolution wherever possible, without posting any warnings about the implicit resolutions.

Explicit and warn implicit

Perform implicit signal resolution wherever possible, posting a warning of each implicit resolution that occurs.

#### Tips

• Use the Signal Properties dialog box (see Signal Properties Dialog BoxSignal Properties Dialog Box) to specify explicit resolution for signals.

• Use the State Attributes pane on dialog boxes of blocks that have discrete states, e.g., the Discrete-Time IntegratorDiscrete-Time Integrator block, to specify explicit resolution for discrete states.

• Multiple signals can resolve to the same signal object and have the properties that the object specifies.

• MathWorks® discourages using implicit signal resolution except for fast prototyping, because implicit resolution slows performance, complicates model validation, and can have nondeterministic effects.

• Simulink software provides the disableimplicitsignalresolution function, which you can use to change settings throughout a model so that it does not use implicit signal resolution.

#### Command-Line Information

 Parameter: SignalResolutionControl Type: string Value: 'UseLocalSettings' | 'TryResolveAll' | 'TryResolveAllWithWarning' Default: 'UseLocalSettings'
SignalResolutionControl ValueEquivalent Signal Resolution Value
'UseLocalSettings'Explicit only
'TryResolveAll'Explicit and implicit
'TryResolveAllWithWarning'Explicit and warn implicit

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionExplicit only

### Division by singular matrix

Select the diagnostic action to take if the ProductProduct block detects a singular matrix while inverting one of its inputs in matrix multiplication mode.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Command-Line Information

 Parameter: CheckMatrixSingularityMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Underspecified data types

Select the diagnostic action to take if Simulink software could not infer the data type of a signal during data type propagation.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Command-Line Information

 Parameter: UnderSpecifiedDataTypeMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Simulation range checking

Select the diagnostic action to take when signals exceed specified minimum or maximum values.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Use a block's Output minimum or Minimum parameter to specify the minimum value that the block should output.

• Use a block's Output maximum or Maximum parameter to specify the maximum value that the block should output.

• Enable this diagnostic to check whether block outputs exceed the minimum or maximum values that you specified.

• When Simulation range checking is enabled, Simulink software performs signal range checking at every time step during a simulation. Setting this diagnostic to warning or error can cause a decrease in simulation performance.

#### Command-Line Information

 Parameter: SignalRangeChecking Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
Debuggingwarning or error
Traceabilitywarning or error
Efficiencynone
Safety precautionerror

### Wrap on overflow

Select the diagnostic action to take if the value of a signal overflows the signal data type and wraps around.

#### Settings

Default: warning

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• This diagnostic applies only to overflows which wrap for integer and fixed-point data types.

• To check for floating-point overflows (for example, Inf or NaN) for double or single data types, select the Inf or NaN block output diagnostic. (See Inf or NaN block output for more information.)

#### Command-Line Information

 Parameter: IntegerOverflowMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'warning'

#### Recommended Settings

ApplicationSetting
Debuggingwarning
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Saturate on overflow

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.

#### Settings

Default: warning

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• This diagnostic applies only to overflows which saturate for integer and fixed-point data types.

• To check for floating-point overflows (for example, Inf or NaN) for double or single data types, select the Inf or NaN block output diagnostic. (See Inf or NaN block output for more information.)

#### Command-Line Information

 Parameter: IntegerSaturationMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'warning'

#### Recommended Settings

ApplicationSetting
Debuggingwarning
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Inf or NaN block output

Select the diagnostic action to take if the value of a block output is Inf or NaN at the current time step.

 Note:   Accelerator mode does not support runtime diagnostics.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• This diagnostic applies only to floating-point overflows for double or single data types.

• To check for integer and fixed-point overflows, select the Wrap on overflow diagnostic. (See Wrap on overflow for more information.)

#### Command-Line Information

 Parameter: SignalInfNanChecking Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### "rt" prefix for identifiers

Select the diagnostic action to take during code generation if a Simulink object name (the name of a parameter, block, or signal) begins with rt.

#### Settings

Default: error

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• The default setting (error) causes code generation to terminate with an error if it encounters a Simulink object name (parameter, block, or signal), that begins with rt.

• This is intended to prevent inadvertent clashes with generated identifiers whose names begins with rt.

#### Command-Line Information

 Parameter: RTPrefix Type: string Value: 'none' | 'warning' | 'error' Default: 'error'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Detect downcast

Select the diagnostic action to take when a parameter downcast occurs during simulation.

#### Settings

Default: error

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• A parameter downcast occurs if the computation of block output required converting the parameter's specified type to a type having a smaller range of values (for example, from uint32 to uint8).

• This diagnostic applies only to named tunable parameters.

#### Command-Line Information

 Parameter: ParameterDowncastMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'error'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Detect overflow

Select the diagnostic action to take if a parameter overflow occurs during simulation.

#### Settings

Default: error

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• A parameter overflow occurs if Simulink software encounters a parameter whose data type's range is not large enough to accommodate the parameter's ideal value (the ideal value is either too large or too small to be represented by the data type). For example, suppose that the parameter's ideal value is 200 and its data type is int8. Overflow occurs in this case because the maximum value that int8 can represent is 127.

• Parameter overflow differs from parameter precision loss, which occurs when the ideal parameter value is within the range of the data type and scaling being used, but cannot be represented exactly.

• Both parameter overflow and precision loss are quantization errors, and the distinction between them can be a fine one. The Detect overflow diagnostic reports all quantization errors greater than one bit. For very small parameter quantization errors, precision loss will be reported rather than an overflow when

$\left(Max+Slope\right)\ge {V}_{ideal}>\left(Min-Slope\right)$

where

• Max is the maximum value representable by the parameter data type

• Min is the minimum value representable by the parameter data type

• Slope is the slope of the parameter data type (slope = 1 for integers)

• Videal is the ideal value of the parameter

#### Command-Line Information

 Parameter: ParameterOverflowMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'error'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Detect underflow

Select the diagnostic action to take when a parameter underflow occurs during simulation.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Parameter underflow occurs when Simulink software encounters a parameter whose data type does not have enough precision to represent the parameter's ideal value because the ideal value is too small.

• When parameter underflow occurs, casting the ideal value to the data type causes the parameter's modeled value to become zero, and therefore to differ from its ideal value.

#### Command-Line Information

 Parameter: ParameterUnderflowMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Detect precision loss

Select the diagnostic action to take when parameter precision loss occurs during simulation.

#### Settings

Default: warning

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Precision loss occurs when Simulink software encounters a parameter whose data type does not have enough precision to represent the parameter's value exactly. As a result, the modeled value differs from the ideal value.

• Parameter precision loss differs from parameter overflow, which occurs when the range of the parameter's data type, i.e., that maximum value that it can represent, is smaller than the ideal value of the parameter.

• Both parameter overflow and precision loss are quantization errors, and the distinction between them can be a fine one. The Detect Parameter overflow diagnostic reports all parameter quantization errors greater than one bit. For very small parameter quantization errors, precision loss will be reported rather than an overflow when

$\left(Max+Slope\right)\ge {V}_{ideal}>\left(Min-Slope\right)$

where

• Max is the maximum value representable by the parameter data type.

• Min is the minimum value representable by the parameter data type.

• Slope is the slope of the parameter data type (slope = 1 for integers).

• Videal is the full-precision, ideal value of the parameter.

#### Command-Line Information

 Parameter: ParameterPrecisionLossMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'warning'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Detect loss of tunability

Select the diagnostic action to take when an expression with tunable variables is reduced to its numerical equivalent.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tip

If a tunable workspace variable is modified by Mask Initialization code, or is used in an arithmetic expression with unsupported operators or functions, the expression is reduced to a numeric expression and therefore cannot be tuned.

#### Command-Line Information

 Parameter: ParameterTunabilityLossMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

Select the diagnostic action to take if the model attempts to read data from a data store to which it has not written data in this time step.

#### Settings

Default: Use local settings

Use local settings

For each local data store (defined by a Data Store Memory block or Simulink.Signal object in a model workspace) use the setting specified by the block. For each global data store (defined by a Simulink.Signal object in the base workspace) disable the diagnostic.

Disable all

Disables this diagnostic for all data stores accessed by the model.

Enable all as warnings

Displays diagnostic as a warning at the MATLAB® command line.

Enable all as errors

Halts the simulation and displays the diagnostic in an error dialog box.

#### Command-Line Information

 Parameter: ReadBeforeWriteMsg Type: string Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' Default: 'UseLocalSettings'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionEnable all as errors

Select the diagnostic action to take if the model attempts to write data to a data store after previously reading data from it in the current time step.

#### Settings

Default: Use local settings

Use local settings

For each local data store (defined by a Data Store Memory block or Simulink.Signal object in a model workspace) use the setting specified by the block. For each global data store (defined by a Simulink.Signal object in the base workspace) disable the diagnostic.

Disable all

Disables this diagnostic for all data stores accessed by the model.

Enable all as warnings

Displays diagnostic as a warning at the MATLAB command line.

Enable all as errors

Halts the simulation and displays the diagnostic in an error dialog box.

#### Command-Line Information

 Parameter: WriteAfterReadMsg Type: string Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' Default: 'UseLocalSettings'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionEnable all as errors

### Detect write after write

Select the diagnostic action to take if the model attempts to write data to a data store twice in succession in the current time step.

#### Settings

Default: Use local settings

Use local settings

For each local data store (defined by a Data Store Memory block or Simulink.Signal object in a model workspace) use the setting specified by the block. For each global data store (defined by a Simulink.Signal object in the base workspace) disable the diagnostic.

Disable all

Disables this diagnostic for all data stores accessed by the model.

Enable all as warnings

Displays diagnostic as a warning at the MATLAB command line.

Enable all as errors

Halts the simulation and displays the diagnostic in an error dialog box.

#### Command-Line Information

 Parameter: WriteAfterWriteMsg Type: string Value: 'UseLocalSettings' | 'DisableAll' | 'EnableAllAsWarning' | 'EnableAllAsError' Default: 'UseLocalSettings'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionEnable all as errors

Select the diagnostic action to take when one task reads data from a Data Store MemoryData Store Memory block to which another task writes data.

#### Settings

Default: warning

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Such a situation is safe only if one of the tasks cannot interrupt the other, such as when the data store is a scalar and the writing task uses an atomic copy operation to update the store or the target does not allow the tasks to preempt each other.

• You should disable this diagnostic (set it to none) only if the application warrants it, such as if the application uses a cyclic scheduler that prevents tasks from preempting each other.

#### Command-Line Information

 Parameter: MultiTaskDSMMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'warning'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionerror

### Duplicate data store names

Select the diagnostic action to take when the model contains multiple data stores that have the same name. The data stores can be defined with Data Store MemoryData Store Memory blocks or Simulink.Signal objects.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tip

This diagnostic is useful for detecting errors that can occur when a lower-level data store unexpectedly shadows a higher-level data store that has the same name.

#### Command-Line Information

 Parameter: UniqueDataStoreMsg Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionNo impact

### 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.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Connecting the inputs of a Merge block to multiple driving blocks that execute at the same time step can lead to inconsistent results for both simulation and generated code. Set Detect multiple driving blocks executing at the same time step to error to avoid such situations.

• If Underspecified initialization detection is set to Simplified, this parameter is disabled, and Simulink software automatically uses the strictest setting (error) for this diagnostic. Multiple driving blocks executing at the same time step always result in an error.

#### Dependency

This parameter is enabled only if Underspecified initialization detection is set to Classic.

#### Command-Line Information

 Parameter: MergeDetectMultiDrivingBlocksExec Type: string Value: 'none' | 'warning' | 'error' Default: 'error'

#### Recommended Settings

ApplicationSetting
Debuggingerror
Traceabilityerror
EfficiencyNo impact
Safety precautionerror

### Underspecified initialization detection

Select how Simulink software handles initialization of initial conditions for conditionally executed subsystems, Merge blocks, subsystem elapsed time, and Discrete-Time Integrator blocks.

#### Settings

Default: Classic

Classic

Initial conditions are initialized the same way they were prior to R2008b.

Simplified

Initial conditions are initialized using the enhanced behavior, which can improve the consistency of simulation results.

#### Tips

• Use Classic to ensure compatibility with previous releases of Simulink.

• Use Simplified to improve the consistency of simulation results, especially for models that do not specify initial conditions for conditional subsystem output ports, and for models that have conditionally executed subsystem output ports connected to S-functions.

• When using Simplified initialization mode, you must set both Mux blocks used to create bus signals, and Bus signal treated as vector to error on the Connectivity Diagnostics pane.

• For existing models, MathWorks recommends using the Model Advisor to migrate your model to the new settings. To migrate your model, run the following Model Advisor checks:

• Check bus usage

• Check consistency of initialization parameters for Outport and Merge blocks

For more information, see Check consistency of initialization parameters for Outport and Merge blocks.

#### Dependencies

Selecting Classic enables the following parameters:

• Detect multiple driving blocks executing at the same time step

• Check undefined subsystem initial output

• Check preactivation output of execution context

• Check runtime output of execution context

Selecting Simplified disables these parameters, and automatically sets Detect multiple driving blocks executing at the same time step to error.

#### Command-Line Information

 Parameter: UnderspecifiedInitializationDetection Type: string Value: 'Classic' | 'Simplified' Default: 'Classic'

#### Recommended Settings

ApplicationSetting
DebuggingSimplified
TraceabilitySimplified
EfficiencySimplified
Safety precautionSimplified

### 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

#### Settings

Default: On

On

Displays 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.

Off

Does not display a warning.

#### Tips

• This situation occurs when a block with a specified initial condition, such as a Constant, Initial Condition, or Delay block, drives an Outport block with an undefined initial condition (Initial output parameter is set to []).

• Models with such subsystems can produce initial results (i.e., before initial activation of the conditionally executed subsystem) in the current release that differ from initial results produced in Release 13 or earlier releases.

Consider for example the following model.

This model does not define the initial condition of the triggered subsystem's output port.

The following figure compares the superimposed output of this model's Step block and the triggered subsystem in Release 13 and the current release.

Notice that the initial output of the triggered subsystem differs between the two releases. This is because Release 13 and earlier releases use the initial output of the block connected to the output port (i.e., the Constant block) as the triggered subsystem's initial output. By contrast, this release outputs 0 as the initial output of the triggered subsystem because the model does not specify the port's initial output.

#### Dependency

This parameter is enabled only if Underspecified initialization detection is set to Classic.

#### Command-Line Information

 Parameter: CheckSSInitialOutputMsg Type: string Value: 'on' | 'off' Default: 'on'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionOn

### Check preactivation output of execution context

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

#### Settings

Default: Off

On

Displays a warning if Simulink software detects potential initial output differences from previous releases.

Off

Does not display a warning.

#### Tips

• This diagnostic is triggered if the model contains a block that meets the following conditions:

• The block produces nonzero output for zero input (e.g., a Cosine block).

• The block is connected to an output of a conditionally executed subsystem.

• The block inherits its execution context from that subsystem.

• The Outport to which it is connected has an undefined initial condition, i.e., the Outport block's Initial output parameter is set to [].

• Models with blocks that meet these criteria can produce initial results (i.e., before the conditionally executed subsystem is first activated in the current release that differ from initial results produced in Release 13 or earlier releases.

Consider for example the following model.

The following figure compares the superimposed output of the Pulse Generator and cos block in Release 13 and the current release.

Note that the initial output of the cos block differs between the two releases. This is because in Release 13, the cos block belongs to the execution context of the root system and hence executes at every time step whereas in the current release, the cos block belongs to the execution context of the triggered subsystem and hence executes only when the triggered subsystem executes.

#### Dependency

This parameter is enabled only if Underspecified initialization detection is set to Classic.

#### Command-Line Information

 Parameter: CheckExecutionContextPreStartOutputMsg Type: string Value: 'on' | 'off' Default: 'on'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionOn

### Check runtime output of execution context

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

#### Settings

Default: Off

On

Displays a warning if Simulink software detects potential output differences from previous releases.

Off

Does not display a warning.

#### Tips

• This diagnostic is triggered if the model contains a block that meets the following conditions:

• The block has a tunable parameter.

• The block is connected to an output of a conditionally executed subsystem.

• The block inherits its execution context from that subsystem.

• The Outport to which it is connected has an undefined initial condition, i.e., the Outport block's Initial output parameter is set to [].

• Models with blocks that meet these criteria can produce results when the parameter is tuned in the current release that differ from results produced in Release 13 or earlier releases.

Consider for example the following model.

In this model, the tunevar S-function changes the value of the Gain block's k parameter and updates the diagram at simulation time 7 (i.e., it simulates tuning the parameter).

The following figure compares the superimposed output of the model's Pulse Generator block and its Gain block in Release 13 and the current release.

Note that the output of the Gain block changes at time 7 in Release 13 but does not change in the current release. This is because in Release 13, the Gain block belongs to the execution context of the root system and hence executes at every time step whereas in the current release, the Gain block belongs to the execution context of the triggered subsystem and hence executes only when the triggered subsystem executes, i.e., at times 5, 10, 15, and 20.

#### Dependency

This parameter is enabled only if Underspecified initialization detection is set to Classic.

#### Command-Line Information

 Parameter: CheckExecutionContextRuntimeOutputMsg Type: string Value: 'on' | 'off' Default: 'on'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionOn

### Array bounds exceeded

Select the diagnostic action to take when blocks write data to locations outside the memory allocated to them.

#### Settings

Default: none

none

warning

error

Simulink software terminates the simulation and displays an error message.

#### Tips

• Use this option to check whether execution of each instance of a block during model simulation writes data to memory locations not allocated to the block. This can happen only if your model includes a user-written S-function that has a bug.

• Enabling this option slows down model execution considerably. Thus, you should enable it only if you suspect that your model contains a user-written S-function that has a bug.

• This option causes Simulink software to check whether a block writes outside the memory allocated to it during simulation. Typically this can happen only if your model includes a user-written S-function that has a bug.

• See Checking Array Bounds in Error Handling for more information on using this option.

#### Command-Line Information

 Parameter: ArrayBoundsChecking Type: string Value: 'none' | 'warning' | 'error' Default: 'none'

#### Recommended Settings

ApplicationSetting
Debuggingwarning
TraceabilityNo impact
Efficiencynone
Safety precautionNo impact

### Model Verification block enabling

Enable model verification blocks in the current model either globally or locally.

#### Settings

Default: Use local settings

Use local settings

Enables or disables blocks based on the value of the Enable assertion parameter of each block. If a block's Enable assertion parameter is on, the block is enabled; otherwise, the block is disabled.

Enable All

Enables all model verification blocks in the model regardless of the settings of their Enable assertion parameters.

Disable All

Disables all model verification blocks in the model regardless of the settings of their Enable assertion parameters.

#### Dependency

Simulation and code generation ignore the Model Verification block enabling parameter when model verification blocks are inside a S-function.

#### Command-Line Information

 Parameter: AssertControl Type: string Value: 'UseLocalSettings' | 'EnableAll' | 'DisableAll' Default: 'UseLocalSettings'

#### Recommended Settings

ApplicationSetting
DebuggingNo impact
TraceabilityNo impact
EfficiencyNo impact
Safety precautionDisable all