Reuse Model Representation for Analysis

When you analyze a model for the first time, Simulink^® Design Verifier™ performs a compatibility check and creates a model representation. The model representation contains information about model behavior to use for analysis. By default, the software saves the model representation at the Simulation cache folder location.

If you modify a model and rerun the analysis, Simulink Design Verifier determines whether to rebuild the model representation or to use the existing Simulink cache depending on the Rebuild model representation parameter.

This table summarizes the behavior of the Rebuild model representation option based on its settings.

Rebuild model representation option	Behavior
If change is detected	Default setting. Triggers a rebuild when changes are detected in the model. Validates model representation against any model changes and Simulink Design Verifier analysis options. Determines whether to reuse or rebuild the model representation for analysis.
Always	The model representation is rebuilt during every model analysis, regardless of changes.

Considerations for Model Change Detection

When the Rebuild model representation option is set to If change is detected, Simulink Design Verifier monitors the model for the changes.

Design Verifier Options	Maximum analysis time Output folder Make output file names unique by adding a suffix Run additional analysis to reduce instances of rational approximation Ignore objectives based on filter Filter file(s)
Test Generation options	Test conditions Test objectives Maximum test case steps Test suite optimization Extend using existing coverage data Extend using existing coverage data Extend using existing test data Separate objectives satisfied with the existing tests/coverage data in the report
Property Proving options	Assertion blocks Proof assumptions Strategy Maximum violation steps
Results generation options	Data file name Include expected output values Randomize data that do not affect the outcome Generate separate harness model after analysis Harness model file name Reference input model in generated harness Test File Name Test Harness Name
Report generation options	Generate report of the results Generate additional report in PDF format Report file name Include screen shots of properties Display report
Structural Checksum of a Model	The Simulink Design Verifier uses both structural checksum and code checksum. A structural checksum is a computation that detects changes in the model that can affect simulation results. For more information about the kinds of changes that affect the model, see Rebuild. Note When you Generate Test Cases for Embedded Coder Generated Code, Simulink Design Verifier also considers checksum of the generated code.
Additional Dependencies	In addition to structural checksum, Simulink Design Verifier checks for changes in model dependencies that can impact the analysis results, such as: Simulation run-time parameters that are defined in the data dictionary or the MATLAB® base, mask, or model workspaces External C or C++ source code files that the model uses during simulation Minimum and maximum constraints that are specified for block parameters Block parameters that are specified for blocks in the Simulink Design Verifier Block Library, such as Values

Limitations

• The model representation is always rebuilt:

  • When Simulink Design Verifier analysis is started from other products such as Simulink Test™, Simulink Coverage™, Simulink Check, and Requirements toolbox.

  • When the model contains MATLAB System blocks.

• Simulink Design Verifier does not detect changes in the custom block replacement rules that you apply, even if the Rebuild model representation option is set to If change is detected. In such cases, the Simulink cache is reused for analysis and a warning message is displayed in the Diagnostic Viewer that suggests you to set the Rebuild model representation option to Always, if you want to rebuild the model representation.