Model References

Reuse models as blocks in other models

You can include one model in another by using a Model block. Each instance of a Model block is a model reference. For simulation and code generation, blocks within a referenced model execute together as a unit. The model that contains a referenced model is a parent model. A collection of parent and referenced models constitutes a model hierarchy.

Like subsystems, model references allow you to organize large models hierarchically. Like libraries, model references allow you to define a set of blocks once and use it repeatedly. Model references provide several advantages that are unavailable with subsystems and libraries. Several of these advantages result from referenced models compiling independent of the context of the Model block, including:

Modular development
Model protection
Inclusion by reference
Incremental loading
Accelerated simulation
Incremental code generation
Independent configuration sets

Blocks

Model	Reference another model to create model hierarchy
Variant Subsystem, Variant Model	Template subsystem containing Subsystem blocks or Model blocks as Variant choices

Functions

`depview`	Display graph of model referencing dependencies with or without library dependencies
`find_mdlrefs`	Find Model blocks and referenced models at all levels or at top level only
`Simulink.fileGenControl`	Specify root folders for files generated by diagram updates and model builds
`Simulink.SubSystem.convertToModelReference`	Convert subsystem to model reference
`slbuild`	Build standalone executable or model reference target for model

Classes

Simulink.BlockPath Fully specified Simulink block path

Simulink Configuration Parameters

Model Configuration Parameters: Model Referencing

Model Configuration Parameters: Model Referencing Diagnostics

Topics

Determine When to Reference Models

Model Reference Basics

Create a model hierarchy by referencing one model in another model. A referenced model contains blocks that execute together as a unit.

Component-Based Modeling Guidelines

Consider componentization for large models and multiuser development teams.

Model Reference Requirements and Limitations

Model references have requirements and limitations relating to features such as reusability, simulation modes, masking, and debugging.

Create Model References

Reference Existing Models

Include a model in another model.

Reference Protected Models from Third Parties

Use a protected model that you received from a third party.

Convert Subsystems to Referenced Models

Prepare a subsystem for conversion, convert the subsystem to a model, and compare simulation results before and after conversion.

Model Reference Interface and Boundary

Ports in the referenced model correspond with ports at the model reference. Signals that cross the model boundary must meet certain requirements.

Inspect Model Hierarchies

Examine the contents, structure, model versions, and logged signals in a model hierarchy.

Configure Model References

Set Configuration Parameters for Model Hierarchies

Configuration parameter values can be different in top models and referenced models. Some configuration parameter values have special requirements or behavior with model referencing.

Modify Referenced Models for Conditional Execution

Execute referenced models conditionally, similar to conditionally executed subsystems.

Referenced Model Sample Times

A referenced model can inherit sample times from the model that references it.

Parameterize Instances of a Reusable Referenced Model

When you model a reusable component as a referenced model, to configure each instance of the component to use different values for block parameters, create model arguments.

Parameterize a Referenced Model Programmatically

This example shows how to programmatically configure multiple instances of a referenced model to use different values for the same block parameter.

Group Multiple Model Arguments into a Single Structure

This example shows how to programmatically configure multiple instances of a referenced model to use different values for the same block parameter by using structures.

Configure Instance-Specific Data for Lookup Tables Programmatically

When you use Simulink.LookupTable objects to store and configure lookup table data for ASAP2 or AUTOSAR code generation (for example, STD_AXIS or CURVE), you can configure the objects as model arguments.

Simulate Model Hierarchies

Choose Simulation Modes for Model Hierarchies

Select the simulation mode for models in a model hierarchy.

Share Build Artifacts for Faster Simulation and Code Generation

Use Simulink cache files to share build artifacts that let you avoid the cost of a first-time build.

Model Reference Simulation Targets

A simulation target, or SIM target, is a MEX-file that implements a referenced model that executes in accelerator mode.

Simulate Conditionally Executed Referenced Models

Run a standalone simulation of a conditionally executed referenced model.

Simulate Multiple Referenced Model Instances in Normal Mode

Simulate a model that contains multiple instances of a referenced model.

Related Information

Component-Based Modeling

Large-Scale Modeling

Variant Systems

Featured Examples

Component-Based Modeling with Model Reference

Use Model Reference. It walks you through simulation and code generation of a model that references another model multiple times.

Open Model

Visualizing Model Reference Architectures

View dependencies among referenced models.

Open Model

Converting Subsystems to Model Reference

Automate conversion of a model containing buses to use model reference.

Open Model

Introduction to Managing Data with Model Reference

The basic concepts related to managing data with model reference.

Open Model

Using Data Stores Across Multiple Models

Use and log local data stores. It also shows how to define, use and log global data stores to share global data among referenced models.

Open Model

Interface Specification Using Bus Objects

Propagate bus signals into referenced models. It also shows how you can simulate the referenced models independently using logged signal data from the parent model. (For a quick introduction to Model Reference, see Component-Based Modeling with Model Reference. See Simulink® documentation for more information about configuring signals for data logging.)

Open Model