Skip to Main Content Skip to Search
Product Documentation

The Model Explorer: Working with Workspace Variables

Finding Variables That Are Used by a Model or Block

In the Model Explorer, you can get a list of variables that a model or block uses. The following approach is one way to get that list of variables:

  1. In the Contents pane, right-click the block for which you want to find the variables that it uses.

  2. Select the Find Referenced Variables menu item.

Model Explorer returns results similar to this:

For performance, Model Explorer uses cached information from the last compiled version of the model. If you want to recompile the model, either do so manually or, in the Model Explorer, set the Update diagram field to yes and repeat the search.

You can also use the following approaches to find variables that a model or block uses:

The Simulink.findVars function provides additional options for returning information about workspace variables that is not available from the Model Explorer or Model Editor.

For information about limitations when finding referenced variables, see the Simulink.findVars documentation.

Using the Set of Returned Variables

For a variable in the set of returned variables, you can find the blocks that use that variable (for details, see Finding Blocks That Use a Specific Variable). Also, you can export variables from the returned set of variables. For details, see Exporting Workspace Variables.

Finding Blocks That Use a Specific Variable

You can use the Model Explorer to get a list of blocks that use a specific workspace variable. One way to get that list of blocks is to right-click a variable in the Contents pane and select the Find Where Used menu item. For example:

  1. Open the f14 model.

  2. Open the Model Explorer.

  3. In the Model Hierarchy pane, select the Base Workspace node.

  4. In the Contents pane, right-click the Mq variable and select the Find Where Used menu item.

  5. In the Hierarchy dialog box that appears, select f14. The Model Explorer displays output similar to this:

    The property columns whose values include Mq represent the block parameters that use the Mq variable. If those property columns are not already in the view, then the Model Explorer adds them to the end of the search results display.

You can also find blocks that use a specific variable, by using one of these approaches:

Finding Unused Workspace Variables

You can use the Model Explorer to get a list of variables that are defined in a workspace but not used by a model or block. One way to get that list of variables is to right-click a workspace name in the Model Hierarchy pane and select the Find Unused Variables menu item. For example:

  1. Open the f14 model.

  2. Open the Model Explorer.

  3. In the Model Hierarchy pane, right-click the Base Workspace node and select the Find Unused Variables menu item.

  4. The Model Explorer displays output similar to this:

    The Simulink.findVars function provides additional options for returning information about unused workspace variables that is not available from the Model Explorer or Model Editor.

Exporting Workspace Variables

You can export (save) a set of variables listed in the Model Explorer, exporting either individual variables or all the variables in the base or model workspace.

One possible workflow is to export the set of variables returned with the Find Referenced Variables option or the Simulink.findVars function. For details, see Finding Variables That Are Used by a Model or Block.

To export all the variables in a workspace in the Model Explorer to a MATLAB code file or MAT-file:

  1. Select the variables that you want to export.

    1. To select all the variables in a workspace, right-click the workspace node (for example, Base Workspace) and select the Export menu item. For example:

    2. To select individual variables, in the Contents pane, select the variables that you want to export. Right-click one of the highlighted variables and select the Export Selected menu item.

    If the Contents pane has data grouped by a property, selecting the top line in a group does not select all the variables in that group. For details about grouped data, seeGrouping by a Property.

  2. Specify whether to save the variables in a MATLAB code file or a MAT-file.

    The MATLAB code file format is easier to read, is editable, and supports version control. The MAT-file format is binary, which has performance advantages.

    If you specify a MATLAB code file format, the Model Explorer may create an associated MAT-file, reflecting the name of the MATLAB code file, but with an extension of .mat instead of .m.

  3. Specify a name and location for the file.

  4. If the file already exists, Model Explorer displays a dialog box asking you to choose one of these options:

    • Overwrite entire file

      • Replaces all variables in the target file with the selected variables, which are stored in alphabetical order.

    • Update variables that exist in file and append new variables to file

      • Updates existing variables in place and appends new variables.

    • Only update variables that exist in file

      • Updates existing variables, but does not add any new variables, which eliminates potentially extraneous variables.

Importing Workspace Variables

You can import (load) a set of variables from a file into the base workspace or into a model workspace using the Model Explorer. When you import variables into a workspace, the Model Explorer overwrites existing variables and adds any new variables.

To import variables into a workspace:

  1. In the Model Hierarchy pane, right-click the workspace into which you want to import variables.

  2. Select the Import menu item.

  3. In the Import from File dialog box, select a MATLAB code file or MAT-file for the variables that you want to import.

      Note   If you import a MATLAB code file, then Simulink also imports the associated MAT-file.

  


Related Products & Applications

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

 © 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS