Manage Design Data
You can use MATLAB® variables to configure and manage signals and block parameters in a model. For more information about how models use variables, see Symbol Resolution. To create, edit, and manage variables, see Create, Edit, and Manage Workspace Variables.
You can store model variables in the MATLAB base workspace, a model workspace, or a data dictionary. To decide where to store variables for your model, see Determine Where to Store Variables and Objects for Simulink Models.
To use variables to control signal and parameter characteristics, such as data types and code generation settings, you can store data objects in a workspace or data dictionary. See Data Objects.
|Analyze relationship between variables and blocks in models|
|Save workspace variables to MATLAB script|
|Evaluate MATLAB expression in context of Simulink model|
|Modify variable values in context of Simulink model|
|Check existence of variable in context of Simulink model|
|Create new data dictionary and create |
|Open data dictionary for editing|
|Return file names and paths of open data dictionaries|
|Create Simulink data dictionary and Architectural Data object (Since R2023b)|
|Create Architectural Data object representing architectural data of existing Simulink data dictionary (Since R2023b)|
|Clear library dictionary dependency analysis (Since R2021a)|
|Update library dictionary dependencies (Since R2021a)|
|Clear cached information on library dictionary links (Since R2022a)|
Objects and Variables
|Configure data dictionary|
|Configure data dictionary section|
|Configure data dictionary entry|
|Store enumerated type definition in data dictionary|
|Edit architectural data in a Simulink data dictionary programmatically (Since R2023b)|
|Edit data interface in Simulink data dictionary programmatically (Since R2023b)|
|Data element of data interface (Since R2023b)|
|Physical interface (Since R2023b)|
|Physical element of a physical interface (Since R2023b)|
|Function in client-server interface (Since R2023b)|
|Function argument in function element of client-server interface (Since R2023b)|
|Service interface (Since R2023b)|
|Structure data type (Since R2023b)|
|Struct element of a struct type (Since R2023b)|
External File Adapters
|Base class used to define file adapter for reading custom file formats (Since R2022b)|
|Contains data for external data source (Since R2022b)|
|Test custom external file adapter (Since R2022b)|
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.
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.
- Graphically Manage Shared Interfaces, Data Types, and Constants
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.
- Attach Data Dictionary to Custom Libraries
Share data objects with Simulink block library users using attached data dictionary.
- Attach Data Dictionary to Subsystem Reference
Use a Simulink data dictionary with child blocks and instances of your subsystem file.
- 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 Objects and Variables
- 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 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.
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