find

Get model elements for the category of model code mappings

Since R2020b

Syntax

modelElementsFound= find(myCodeMappingObj,category)

modelElementsFound= find(myCodeMappingObj,category,Name,Value)

Description

modelElementsFound= find(myCodeMappingObj,category) returns the elements in the model code mappings of the specified category as an array of objects.

modelElementsFound= find(myCodeMappingObj,category,Name,Value) returns the elements in the model code mappings of the specified category that match specified property and value criteria.

Examples

Find Model Parameters in Code Mappings

In the model code mappings for model myConfigModel, find model workspace parameters.

cm = coder.mapping.api.get('myConfigModel');
modelParams = find(cm,'ModelParameters');

Find Inport Blocks That Have Storage Class Set to Auto

For model myConfigModel, find Inport blocks that have storage class set to Auto. For each Inport block found, change the storage class setting to Model default.

cm = coder.mapping.api.get('myConfigModel');
inportBlkHandles = find(cm,'Inports','StorageClass','Auto');
setInport(cm,inportBlkHandles,'StorageClass','Model default');

Input Arguments

myCodeMappingObj — Code mapping object

CodeMapping object

Code mapping object returned by a call to function coder.mapping.api.get.

Example: myCM

category — Model element category

DataStores | DataTransfers | Inports | ModelParameters | ModelParameterArguments | Outports | Signals | States

Category of model elements that you search for in the model code mappings.

Example: 'Inports'

Name-Value Arguments

Example: 'Identifier','mp_table1'

Specify optional comma-separated pairs of Name,Value arguments. Name is the argument name and Value is the corresponding value. Name must appear inside quotes. You can specify several name and value pair arguments as Name1,Value1,…,NameN,ValueN. The order of the name and value pair arguments does not matter.

Data Interfaces

StorageClass — Name of storage class

Auto | Dictionary default | ExportedGlobal | ImportedExtern | ImportedExternPointer | Model default

Data element storage class to include in code mappings search criteria. The name of a predefined storage class or storage class that is defined in the Embedded Coder Dictionary associated with the model. Values that you can specify vary depending on the category that you specify.

Identifier — Code identifier

character vector | string scalar

Name that the code generator uses to identify a data element in generated code. Applies to storage classes other than Auto.

Data Types: char | string

Output Arguments

modelElementsFound — Model elements found

array | string vector

Model elements found, returned as an array or string vector of objects. Each object identifies a model element of the specified category. If you specify additional search criteria, the array or string vector includes objects for model elements of the specified category that meet the additional search criteria. The object returned for an element depends on the category that you specify.

Category	Type of Object Returned
Inports, Outports, and States	Block handle
Signals	Port handle
DataStores	Block handle
ModelParameters	Model parameter name
ModelParameterArguments	Model parameter argument name

Version History

Introduced in R2020b

R2022b: Model parameters and parameter arguments returned separately by find function

The find function now returns model parameter arguments separately from model parameters.

Starting in R2022b, to return all elements in the model code mappings that are model parameter arguments, enter the following.

cm = coder.mapping.api.get('myConfigModel');
modelParamArgs = find(cm,'ModelParameterArguments');

To return all elements in the model code mappings that are model parameters, enter the following.

cm = coder.mapping.api.get('myConfigModel');
modelParams = find(cm,'ModelParameters');

In previous releases, specifying ModelParameters as the category argument returned both model parameters and model parameter arguments.