sdo.requirements.SmoothnessConstraint
Impose bounds on gradient magnitude of variable
Description
Use the sdo.requirements.SmoothnessConstraint
object to impose an upper bound on the gradient magnitude of a variable in a Simulink® model. The variable can be a vector, matrix, or multidimensional array that is a
parameter in your model, such as the data of a lookup table. For example, consider a car
engine controller whose gain changes under different operating conditions determined by the
car speed. You can use a gradient bound constraint to limit the rate at which the controller
gain changes per unit change in vehicle speed.
You can use the requirement object as an input to your cost function and then use the evalRequirement
command to evaluate whether your test data satisfies the requirement. If the test data is not
smooth, the gradient of the test data is greater than the required bound. 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.
Creation
Syntax
Description
creates an
smooth_req =
sdo.requirements.SmoothnessConstraintsdo.requirements.SmoothnessConstraint 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, smooth_req =
sdo.requirements.SmoothnessConstraint(PropertyName=Value)smooth_req =
sdo.requirements.SmoothnessConstraint(GradientBound=2.5) creates an
sdo.requirements.SmoothnessConstraint object and specifies the gradient
magnitude bound as 2.5.
Output Arguments
Properties
Object Functions
copy | Copy design requirement |
get | Get design requirement property values |
set | Set design requirement property values |
evalRequirement | Evaluate design requirement |
Examples
Version History
Introduced in R2016b