Manage Design Data

Choose how to store, partition, and share model design data for small projects and complex model hierarchies

Design data is the set of variables and data objects that you use to specify block parameters and signal characteristics, such as data type and dimension, in a Simulink^® model. Storage options for design data include the MATLAB^® base workspace, model workspaces, MATLAB files, and data dictionaries. Choosing a storage option for your design data can depend on:

Modeling goals
Model architecture
Types of data

To learn about types of model data and how to manage data storage for your project, see Determine Where to Store Variables and Objects for Simulink Models.

To learn how to manage data programmatically, see Manage Design Data for Simulink Models Programmatically.

Functions

expand all

Manage Data Sources

`Simulink.data.connect`	Create `Simulink.data.DataConnection` object for data source (Since R2024a)
`Simulink.data.dataSource.addSource`	Add external data source to model (Since R2024b)
`Simulink.data.dataSource.removeSource`	Remove external data source from model (Since R2024b)
`Simulink.data.dataSource.hasSource`	Determine if specified external data source is associated with model (Since R2024b)
`Simulink.data.dataSource.getSourceNames`	Get list of all external data sources associated with model (Since R2024b)

Manage Data Dictionary

`Simulink.data.dictionary.closeAll`	Close all connections to all open data dictionaries
`Simulink.data.dictionary.create`	Create new data dictionary and create `Simulink.data.Dictionary` object
`Simulink.data.dictionary.open`	Open data dictionary for editing
`Simulink.data.dictionary.getOpenDictionaryPaths`	Return file names and paths of open data dictionaries
`Simulink.dictionary.archdata.create`	Create Simulink data dictionary and Architectural Data object (Since R2023b)
`Simulink.dictionary.archdata.open`	Create Architectural Data object representing architectural data of existing Simulink data dictionary (Since R2023b)
`Simulink.LibraryDictionary.clear`	Clear library dictionary dependency analysis (Since R2021a)
`Simulink.LibraryDictionary.refresh`	Update library dictionary dependencies (Since R2021a)
`Simulink.LibraryDictionary.resetLibraryLinks`	Clear cached information on library dictionary links (Since R2022a)

Manage External File Adapters

`Simulink.data.adapters.catalog`	List registered file adapters (Since R2022b)
`Simulink.data.adapters.registerAdapter`	Register custom file adapter (Since R2022b)
`Simulink.data.adapters.unregisterAdapter`	Unregister custom file adapter (Since R2022b)

Manage Variables

`Simulink.findVars`	Analyze relationship between variables and blocks in models
`matlab.io.saveVariablesToScript`	Save workspace variables to MATLAB script
`Simulink.data.assigninGlobal`	Modify variable values in context of Simulink model
`Simulink.data.evalinGlobal`	Evaluate MATLAB expression in context of Simulink model
`Simulink.data.existsInGlobal`	Determine if variable exists in context of Simulink model
`Simulink.data.getVariableFromGlobal`	Get variable defined in context of Simulink model (Since R2024b)
`Simulink.data.resolveInGlobal`	Resolve MATLAB expression in context of Simulink model (Since R2024b)

Objects

expand all

Data Sources

Simulink.data.DataConnection Data source connection (Since R2024a)

Model Workspace

Simulink.ModelWorkspace Interact with the model workspace of a model programmatically

Data Dictionary

`Simulink.data.Dictionary`	Configure data dictionary
`Simulink.data.dictionary.Section`	Configure data dictionary section
`Simulink.data.dictionary.Entry`	Configure data dictionary entry
`Simulink.data.dictionary.EnumTypeDefinition`	Store enumerated type definition in data dictionary
`Simulink.dictionary.ArchitecturalData`	Edit architectural data in a Simulink data dictionary programmatically (Since R2023b)
`Simulink.dictionary.archdata.AliasType`	Edit Simulink alias types in Simulink data dictionary (Since R2023b)
`Simulink.dictionary.archdata.Constant`	Store constant values in Architectural Data section of data dictionaries (Since R2023b)
`Simulink.dictionary.archdata.DataInterface`	Edit data interface in Simulink data dictionary programmatically (Since R2023b)
`Simulink.dictionary.archdata.DataElement`	Data element of data interface (Since R2023b)
`Simulink.dictionary.archdata.PhysicalInterface`	Physical interface (Since R2023b)
`Simulink.dictionary.archdata.PhysicalElement`	Physical element of a physical interface (Since R2023b)
`Simulink.dictionary.archdata.FunctionElement`	Function in client-server interface (Since R2023b)
`Simulink.dictionary.archdata.FunctionArgument`	Function argument in function element of client-server interface (Since R2023b)
`Simulink.dictionary.archdata.ServiceInterface`	Service interface (Since R2023b)
`Simulink.dictionary.archdata.StructType`	Structure data type (Since R2023b)
`Simulink.dictionary.archdata.StructElement`	Struct element of a struct type (Since R2023b)
`Simulink.dictionary.archdata.NumericType`	Edit Simulink numeric types in Simulink data dictionary (Since R2023b)
`Simulink.dictionary.archdata.ValueType`	Specify common set of signal properties for reuse in Architectural Data section (Since R2023b)

External File Adapters

`Simulink.data.adapters.BaseMatlabFileAdapter`	Base class used to define file adapter for reading custom file formats (Since R2022b)
`Simulink.data.DataSourceWorkspace`	Contains data for external data source (Since R2022b)
`Simulink.data.adapters.AdapterDataTester`	Test custom external file adapter (Since R2022b)

Objects and Variables

`Simulink.WorkspaceVar`	Store information about workspace variables and blocks that use them
`Simulink.VariableUsage`	Store information about the relationship between variables and blocks in models
`Simulink.CoderInfo`	Specify information needed to generate code for signal, state, or parameter data

Tools

Architectural Data Editor

Manage architectural data (Since R2023b)

Topics

Data Storage for Simulink Models

Determine Where to Store Variables and Objects for Simulink Models
Simulink data are objects and variables that you create in workspaces such as the base workspace or a data dictionary. Choose a technique to permanently store that data.
Link MAT File to Model as External Data Source
Use MAT file as an external data source to link it to model for permanent data storage.
Manage Design Data for Simulink Models Programmatically
Connect to a data source, such as a model workspace, base workspace, MAT file, or data dictionary, then use a common set of functions to manage the data.
Create, Edit, and Manage Workspace Variables
Workspace variables enable you to share information, such as parameter values and data types, between blocks and models. Use different tools and techniques to create and manipulate workspace variables.
Edit and Manage Workspace Variables by Using Model Explorer
Find out which workspace variables are used by a model or block, find blocks that use a variable, find unused variables, and rename a variable everywhere it is used by blocks. Save and load variables from a separate file.

Data Storage in Model Workspace

Model Workspaces
Place variables and objects that a model uses in a workspace that only the model can access.
Change Model Workspace Data
When you store data in a model workspace, you choose a data source, such as the model file or an external MAT-file. To modify the variables at the source, you use a different procedure depending on the type of source that you selected.
Specify Source for Data in Model Workspace
Store variables and objects that a model uses in the model file or in a separate file. Optionally, store the variables and objects as code that you can modify.

Data Storage in Dictionary

What Is a Data Dictionary?
Use a data dictionary to store external data for a model.
Import and Export Dictionary Data
Migrate data between a data dictionary and a MAT file or MATLAB script file.
View and Revert Changes to Dictionary Data
Use a data dictionary to inspect and manage changes to model data.
Store Shared Data in Architectural Data Section
To share interfaces, data types, and constants across components and compositions modeled in Simulink, use the Architectural Data section of a data dictionary.
Migrate Models to Use Simulink Data Dictionary
Store variables and objects in data dictionaries.
Partition Dictionary Data Using Referenced Dictionaries
Create referenced dictionaries to store subsets of the data that a model or model hierarchy uses.
Partition Data for Model Reference Hierarchy Using Data Dictionaries
Compose a dictionary hierarchy based on a model reference hierarchy.
Link Data Dictionary to Custom Libraries
Share data objects with Simulink block library users using linked data dictionary.
Enumerations in Data Dictionary
Store enumerated type definitions and enumerated data in a data dictionary.
Store Data in Dictionary Programmatically
Use scripts and the command prompt to create and interact with data dictionaries.

Data Storage in External Files

Create External File Adapter for Loading Variables into Simulink.SimulationInput Object
Define a custom file adapter that can be used by Simulink to load variables from an external file source into a Simulink.SimulationInput object.

Data Storage in Objects and Variables

Data Objects
Specify properties for parameters, signals, and states, including parameter values, outside of a block diagram by using external data objects.
Symbol Resolution
You can control how blocks in a model resolve symbols to variables and objects that you create in workspaces.
Define Data Classes
Customize the way your model interacts with data (signals, parameters, and states) by creating your own class of data object.
Upgrade Level-1 Data Classes
Simulink no longer supports level-1 data classes. You must upgrade data classes that you created using the level-1 data class infrastructure, which was removed in a previous release.

Related Information

Data Import and Export

How useful was this information?

Unrated 1 star 2 stars 3 stars 4 stars 5 stars