Operating point object from a different release

Diagnostic action to take if initial operating point was generated in different release

Model Configuration Pane: Diagnostics / Compatibility

Description

The Operating point object from a different release parameter specifies the diagnostic action to take when the initial operating point for a simulation was generated using a different version of Simulink^® software. To simulate from an initial operating point, specify the value of the Initial state parameter as a Simulink.op.ModelOperatingPoint object.

If you use a model operating point from a different release as the initial state for a simulation, the software:

• Sets block states using the loggedStates property of the ModelOperatingPoint object

• Sets the simulation time as close to the snapshot time of the operating point as possible

• Does not initialize any other aspects of the model and simulation, such as the solver state and hidden block states

Settings

error (default) | warning

error

The software terminates simulation and issues an error if the initial operating point was generated using a different version of Simulink software.

Use this setting when you need simulations run from an initial operating point to produce identical results to an equivalent simulation run from the start, without an initial operating point.

Because the Initial state parameter is run-to-run tunable, you can resolve this error by specifying a different initial state or disabling initial state loading without disabling fast restart or recompiling the model.

warning

The software issues a warning if the initial operating point was generated using a different version of Simulink software. The software initializes the simulation by using only the states data in the loggedStates property of the ModelOperatingPoint object and setting the simulation time as close to the operating point snapshot time as possible.

Tips

Differences between the model you simulate from an initial operating point and the model that produced the operating point can also affect simulation results. The software uses checksums to detect when the model that uses an operating point is different from the model that produced the operating point.

• The interface checksum tracks a collection of model settings that might affect simulation results but do not affect the model structure or the algorithmic content of the model. 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 interface checksum mismatch parameter.

• The contents checksum tracks information about the model structure and algorithmic behavior. Changes that affect the contents checksum can affect simulation results, sometimes significantly. To specify the diagnostic action to take when the model contents checksum does not match the contents checksum of the initial operating point, use the Operating point contents checksum mismatch parameter.

Programmatic Use

Parameter: NonCurrentReleaseOperatingPointMsg

Type: string | character vector

Value: "error" | "warning"

Default: "error"

Version History

Introduced in R2019a

R2019a: Simstate object from earlier release parameter renamed to Operating point object from a different release

The Operating point object from a different release parameter replaces the Simstate object from earlier release parameter, which was introduced in R2011a. To programmatically configure the parameter in previous releases, you used the SimStateOlderReleaseMsg parameter. Starting in R2019a, use the NonCurrentReleaseOperatingPointMsg parameter.

The SimStateOlderReleaseMsg parameter continues to work and results in the same behavior as the NonCurrentReleaseOperatingPointMsg parameter.