Documentation

Always rebuild targets for referenced models. This setting requires the most processing time because it can trigger unnecessary builds. To make all model reference targets up to date, use this setting before you deploy a model.

Conditionally rebuild targets for referenced models when Simulink detects a change that could affect simulation results. To perform extensive change detection on dependencies of referenced models, use this setting.

If Simulink finds no changes in known dependencies, it computes the structural checksum of the model. The structural checksum detects changes that occur in user-created dependencies that are not specified using the Model dependencies configuration parameter. If the structural checksum has changed, Simulink rebuilds the model reference target.

Conditionally rebuild targets for referenced models when Simulink detects a change that could affect simulation results. To reduce the time required for change detection, use this setting.

If Simulink finds no changes in known or potential dependencies, it does not compute the structural checksum of the model and does not rebuild the model reference target. To avoid invalid simulation results, you must list all user-created dependencies in the Model dependencies parameter.

Do not rebuild targets for referenced models. This setting requires the least processing time and, when available, uses Simulink cache files for faster simulations. To avoid rebuilds when developing a model, use this setting.

If model reference targets are out of date, the simulation may present invalid results. To have Simulink check for changes in known target dependencies and report if the model reference targets may be out of date, use the Never rebuild diagnostic parameter. To manually rebuild model reference targets, use the slbuild function.

For information on using and sharing Simulink cache files, see Share Simulink Cache Files for Faster Simulation.

Known target dependencies are files and data external to model files that Simulink examines for changes when checking if a model reference target is up to date. Simulink automatically computes a set of known target dependencies. Examples of known target dependencies are:

Potential target dependencies are files and data external to model files and model configuration settings that Simulink examines for changes when checking if a model reference target is up to date. Simulink automatically computes a set of potential target dependencies. Examples of potential target dependencies are:

Simulink examines each potential target dependency to determine whether its state triggers a structural checksum check.

User-created dependencies are files that Simulink does not automatically identify, in spite of their potential impact on simulation results. Examples of user-created dependencies are:

You can add user-created dependencies to the set of known target dependencies by using the Model dependencies parameter.

A structural checksum is a computation used to detect changes in the model that can affect simulation results. When Simulink computes the structural checksum, it loads and compiles the model. To compile the model, Simulink must execute callbacks and access all variables that the model uses. The structural checksum detects changes in user-created dependencies, regardless of whether you have specified those user-created dependencies in the Model dependencies parameter.

For more information about the kinds of changes that affect the structural checksum, see Simulink.BlockDiagram.getChecksum.