Operating point object from a different release
Diagnostic behavior when loading initial operating point generated in different release
Model Configuration Pane: Diagnostics / Compatibility
The Operating point object from a different release parameter controls the diagnostic behavior when the specified Initial state value is a
Simulink.op.ModelOperatingObject that was generated using a different version of Simulink® software.
When you use a model operating point from a different release as the initial state for a simulation, the software might not be able to restore the complete operating point.
The software terminates simulation and issues an error when the version of Simulink software does not match the version that generated the model operating point specified as the initial state.
Use this option to ensure the complete operating point is restored.
The software issues a warning when the version of Simulink software does not match the version that generated the model operating point specified as the initial state. The simulation proceeds, and the software restores as much of the operating point as possible.
After you simulate a model with fast restart enabled for the first time, this diagnostic does not interrupt execution of subsequent simulations or require recompilation.
|Safety precaution||No impact|
Version HistoryIntroduced 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
In most cases, you do not need to update models or scripts in response to this
SimStateOlderReleaseMsg parameter continues to work
and results in the same behavior as the