sdo.requirements.MonotonicVariable class
Package: 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 requirement
=
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.
creates the requirement object with additional options specified by one or more
requirement
= sdo.requirements.MonotonicVariable(Name,Value
)Name,Value
pair arguments. Name
is a property name and
Value
is the corresponding value. Name
must
appear inside single quotes (''
). You can specify several name-value
pair arguments in any order as Name1,Value1,...,NameN,ValueN
.
Input Arguments
Name-Value ArgumentsSpecify optional pairs of arguments as
Name1=Value1,...,NameN=ValueN
, where Name
is
the argument name and Value
is the corresponding value.
Name-value arguments must appear after other arguments, but the order of the
pairs does not matter.
Before R2021a, use commas to separate each name and value, and enclose
Name
in quotes.
Use Name,Value
arguments to specify properties of the
requirement object during object creation. For example, requirement
= sdo.requirements.MonotonicVariable('Type',{'>'})
creates
an sdo.requirements.MonotonicVariable
object
and specifies the Type
property as monotonically
decreasing.
Properties
Methods
evalRequirement | Evaluate satisfaction of monotonic variable requirement |
Copy Semantics
Handle. To learn how handle classes affect copy operations, see Copying Objects.
Examples
Version History
Introduced in R2016b