Operating point interface checksum mismatch

Diagnostic action to take if model interface checksum does not match interface checksum of initial operating point

Model Configuration Pane: Diagnostics

Description

The Operating point interface checksum mismatch parameter specifies the diagnostic action to take if the interface checksum of the model does not match the interface checksum of the initial operating point. To simulate from an initial operating point, specify the value of the Initial state parameter as a Simulink.op.ModelOperatingPoint object.

The interface checksum tracks a collection of model settings, including inherited and derived settings, that do not affect the model structure or algorithm but can affect simulation results. An interface checksum mismatch indicates a difference in the value of one or more of these settings between the current model and the model that produced the initial operating point. If the interface checksum of the model does not match the interface checksum of the operating point, the software might not be able to completely initialize the simulation to the initial operating point. When you set this parameter to warning or none, the software initializes the simulation using as much operating point data as possible.

The software can detect an interface checksum mismatch but cannot determine the effect of the mismatch on the simulation results. Differences that can cause an interface checksum mismatch include:

• Choice of variable-step solver or choice of fixed-step solver

• Model-level logging settings, specified using parameters on the Data Import/Export pane of the Configuration Parameters dialog box

• Signal logging selection

• Introducing a new sample time or eliminating a sample time

To decide how to respond to an interface checksum mismatch, consider how these differences could affect simulation results and the relevance of the possible effects to your simulation goals. For more information, see Speed Up Simulation Workflows by Using Model Operating Points.

Settings

warning (default) | error | none

warning

The software issues a warning and initializes the simulation using as much operating point data as possible if the model interface checksum does not match the interface checksum of the initial operating point.

error

The software issues an error and terminates the simulation if the model interface checksum does not match the interface checksum of the initial operating point.

none

The software does not issue a diagnostic and initializes the simulation using as much operating point data as possible if the model interface checksum does not match the interface checksum of the initial operating point.

Use this setting only if you do not require that the results of simulations run from an initial operating point exactly match the results of an equivalent simulation run from the start, without an initial operating point.

Tips

• The contents checksum tracks information about the model structure and algorithmic behavior. A contents checksum mismatch indicates that the current model is structurally or algorithmically different from the model that produced the initial operating point. To specify the diagnostic action to take when the model interface checksum does not match the interface checksum of the initial operating point, use the Operating point contents checksum mismatch parameter.

• If you use a model operating point from a different release as the initial state for a simulation, the software cannot completely initialize the model and simulation to the operating point. Incomplete initialization could affect simulation results. To specify the diagnostic action to take when the initial operating point was generated in a different release, use the Operating point object from a different release parameter.

Programmatic Use

Parameter: OperatingPointInterfaceChecksumMismatchMsg

Type: string | character vector

Value: "warning" | "error" | "none"

Default: "warning"

Version History

Introduced in R2019a

R2019a: SimState interface checksum mismatch parameter renamed to Operating point restore interface checksum mismatch

The Operating point restore interface checksum mismatch parameter replaces the SimState interface checksum mismatch parameter, which was introduced in R2009b. To programmatically configure the parameter in previous releases, you used the SimStateInterfaceChecksumMismatchMsg parameter. Starting in R2019a, use the OperatingPointInterfaceChecksumMismatchMsg parameter.

The SimStateInterfaceChecksumMismatchMsg parameter continues to work and results in the same behavior as the OperatingPointInterfaceChecksumMismatchMsg parameter.