sdo.requirements.MonotonicVariable Class
Namespace: sdo.requirements
Superclasses:
Impose monotonic constraint on variable
Description
Use the sdo.requirements.MonotonicVariable
object
to impose a monotonic constraint on a variable in your Simulink® model.
The variable can be a vector, matrix, or multidimensional array that
is a parameter in your model, such as the breakpoints of a lookup
table. You create the requirement object, and specify the type of
monotonic requirement the variable needs to satisfy. For example,
for a 2-D array variable, you can specify the elements of the first
dimension as monotonically increasing and the elements of the second
dimension as monotonically decreasing.
You can use the requirement object as an input to your cost function and
use the evalRequirement
command to evaluate whether
your test data satisfies the specified requirement. You can then use
the cost function and sdo.optimize
to
perform response optimization, subject to satisfaction of the specified
requirement. If you are performing sensitivity analysis, after you
generate parameter samples, you can use the cost function and sdo.evaluate
to evaluate the requirement
for each generated sample.
Construction
creates an
mono_req
=
sdo.requirements.MonotonicVariablesdo.requirements.MonotonicVariable
requirement object and assigns
default values to its properties. Use dot notation to customize the properties. Use the
evalRequirement
command to evaluate whether test data satisfies
the specified requirement.
specifies one or more properties using name-value
arguments. For example, mono_req
=
sdo.requirements.MonotonicVariable(Name=Value)mono_req =
sdo.requirements.MonotonicVariable(Type=">")
creates an
sdo.requirements.MonotonicVariable
object and specifies the
Type
property as monotonically decreasing.
Before R2021a, use commas to separate each name and value, and enclose
Name
in quotes. For example, mono_req =
sdo.requirements.MonotonicVariable("Type",">")
creates an
sdo.requirements.MonotonicVariable
object and specifies the
Type
property as monotonically decreasing.
Properties
Methods
copy | Copy design requirement |
get | Get design requirement property values |
set | Set design requirement property values |
evalRequirement | Evaluate design requirement |
Copy Semantics
Handle. To learn how handle classes affect copy operations, see Copying Objects.
Examples
Version History
Introduced in R2016b