Polezero plot of linear system approximated from nonlinear Simulink model
Simulink^{®} Control Design™
This block is the same as the Check PoleZero Characteristics block except for different default parameter settings in the Bounds tab.
Compute a linear system from a Simulink model and plot the poles and zeros on a polezero map.
During simulation, the software linearizes the portion of the model between specified linearization inputs and outputs, and plots the poles and zeros of the linear system.
The Simulink model can be continuous or discretetime or multirate and can have time delays. Because you can specify only one linearization input/output pair in this block, the linear system is SingleInput SingleOutput (SISO).
You can specify multiple bounds that approximate secondorder characteristics on the pole locations and view them on the plot. You can also check that the bounds are satisfied during simulation:
If all bounds are satisfied, the block does nothing.
If a bound is not satisfied, the block asserts and a warning message appears in the MATLAB^{®} Command Window. You can also specify that the block:
Evaluate a MATLAB expression.
Stop the simulation and bring that block into focus.
During simulation, the block can also output a logical assertion signal.
If all bounds are satisfied, the signal is true (1
).
If any bound is not satisfied, the signal is false (0
).
You can add multiple PoleZero Plot blocks to compute and plot the poles and zeros of various portions of the model.
You can save the linear system as a variable in the MATLAB workspace.
The block does not support code generation and can be used only
in Normal
simulation mode.
The following table summarizes the PoleZero Plot block parameters, accessible via the block parameter dialog box.
Task  Parameters  

Configure linearization.  Specify inputs and outputs (I/Os). 
In Linearizations tab: 
Specify settings. 
In Linearizations tab:  
Specify algorithm options. 
In Algorithm Options of Linearizations tab:  
Specify labels for linear system I/Os and state names. 
In Labels of Linearizations tab:  
Plot the linear system.  Show Plot  
(Optional) Specify bounds on polezero for assertion.  In Bounds tab:  
Specify assertion options (only when you specify bounds on the linear system). 
In Assertion tab:  
Save linear system to MATLAB workspace.  Save data to workspace in Logging tab.  
Display plot window instead of block parameters dialog box on doubleclicking the block.  Show plot on block open. 
Linearization inputs and outputs that define the portion of a nonlinear Simulink model to linearize.
If you have defined the linearization input and output in the Simulink model, the block automatically detects these points and displays them in the Linearization inputs/outputs area. Click at any time to update the Linearization inputs/outputs table with I/Os from the model. To add other analysis points:
Click .
The dialog box expands to display a Click a signal in the model to select it area and a new button.
Select one or more signals in the Simulink Editor.
The selected signals appear under Model signal in the Click a signal in the model to select it area.
(Optional) For buses, expand the bus signal to select individual elements.
Tip
For large buses or other large lists of signals, you can enter search text for filtering element names in the Filter by name edit box. The name match is casesensitive. Additionally, you can enter a MATLAB regular expression.
To modify the filtering options, click . To hide the filtering options, click .
Click to add the selected signals to the Linearization inputs/outputs table.
To remove a signal from the Linearization inputs/outputs table, select the signal and click .
Tip
To find the location in the Simulink model corresponding to a signal in the Linearization inputs/outputs table, select the signal in the table and click .
The table displays the following information about the selected signal:
Block : Port : Bus Element  Name of the block associated with the input/output. The number adjacent to the block name is the port number where the selected bus signal is located. The last entry is the selected bus element name. 
Configuration 
Type of linearization point:

Note
If you simulate the model without specifying an input or output, the software does not compute a linear system. Instead, you see a warning message at the MATLAB prompt.
No default
Enables signal selection in the Simulink model. Appears only when you click .
When this option appears, you also see the following changes:
A new button.
Use to add a selected signal as a linearization input or output in the Linearization inputs/outputs table. For more information, see Linearization inputs/outputs.
changes to .
Use to collapse the Click a signal in the model to select it area.
No default
Enable the use of MATLAB regular expressions for filtering
signal names. For example, entering t$
in the Filter
by name edit box displays all signals whose names end with
a lowercase t
(and their immediate parents). For
details, see Regular Expressions.
Default: On
Allow use of MATLAB regular expressions for filtering signal names.
Disable use of MATLAB regular expressions for filtering signal names. Filtering treats the text you enter in the Filter by name edit box as a literal character vector.
Selecting the Options button on the righthand side of the Filter by name edit box () enables this parameter.
Uses a flat list format to display the list of filtered signals, based on the search text in the Filter by name edit box. The flat list format uses dot notation to reflect the hierarchy of bus signals. The following is an example of a flat list format for a filtered set of nested bus signals.
Default: Off
Display the filtered list of signals using a flat list format, indicating bus hierarchies with dot notation instead of using a tree format.
Display filtered bus hierarchies using a tree format.
Selecting the Options button on the righthand side of the Filter by name edit box () enables this parameter.
When to compute the linear system during simulation.
Default: Simulation
snapshots
Simulation snapshots
Specific simulation time, specified in Snapshot times.
Use when you:
Know one or more times when the model is at a steadystate operating point
Want to compute the linear systems at specific times
External trigger
Triggerbased simulation event. Specify the trigger type in Trigger type.
Use when a signal generated during simulation indicates steadystate operating point.
Selecting this option adds a trigger port to the block. Use this port to connect the block to the trigger signal.
For example, for an aircraft model, you might want to compute the linear system whenever the fuel mass is a fraction of the maximum fuel mass. In this case, model this condition as an external trigger.
Setting this parameter to Simulation
snapshots
enables Snapshot times.
Setting this parameter to External trigger
enables Trigger
type.
Parameter: LinearizeAt 
Type: character vector 
Value: 'SnapshotTimes'  'ExternalTrigger' 
Default: 'SnapshotTimes' 
One or more simulation times. The linear system is computed at these times.
Default: 0
For a different simulation time, enter the time. Use when you:
Want to plot the linear system at a specific time
Know the approximate time when the model reaches steadystate operating point
For multiple simulation times, enter a vector. Use when you want to compute and plot linear systems at multiple times.
Snapshot times must be less than or equal to the simulation time specified in the Simulink model.
Selecting Simulation snapshots
in Linearize on enables
this parameter.
Parameter: SnapshotTimes 
Type: character vector 
Value: 0 
positive real number  vector of positive real numbers 
Default: 0 
Trigger type of an external trigger for computing linear system.
Default: Rising
edge
Rising edge
Rising edge of the external trigger signal.
Falling edge
Falling edge of the external trigger signal.
Selecting External trigger
in Linearize on enables
this parameter.
Parameter: TriggerType 
Type: character vector 
Value: 'rising'  'falling' 
Default: 'rising' 
Enable zerocrossing detection to ensure that the software computes the linear system characteristics at the following simulation times:
The exact snapshot times, specified in Snapshot times.
As shown in the following figure, when zerocrossing detection
is enabled, the variablestep Simulink solver simulates the model
at the snapshot time T_{snap}
. T_{snap}
may
lie between the simulation time steps T_{n1}
and T_{n}
which
are automatically chosen by the solver.
The exact times when an external trigger is detected, specified in Trigger type.
As shown in the following figure, when zerocrossing detection
is enabled, the variablestep Simulink solver simulates the model
at the time, T_{trig}
, when
the trigger signal is detected. T_{trig}
may
lie between the simulation time steps T_{n1}
and T_{n}
which
are automatically chosen by the solver.
For more information on zerocrossing detection, see ZeroCrossing Detection in the Simulink User Guide.
Default: On
Compute linear system characteristics at the exact snapshot time or exact time when a trigger signal is detected.
This setting is ignored if the Simulink solver is fixed step.
Compute linear system characteristics at the simulation time steps that the variablestep solver chooses. The software may not compute the linear system at the exact snapshot time or exact time when a trigger signal is detected.
Parameter: ZeroCross 
Type: character vector 
Value: 'on'  'off' 
Default: 'on' 
How to represent time delays in your linear model.
Use this option if you have blocks in your model that have time delays.
Default: Off
Return a linear model with exact delay representations.
Return a linear model with Padé approximations of delays, as specified in your Transport Delay and Variable Transport Delay blocks.
Parameter: UseExactDelayModel 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Sample time of the linear system computed during simulation.
Use this parameter to:
Compute a discretetime system with a specific sample time from a continuoustime system
Resample a discretetime system with a different sample time
Compute a continuoustime system from a discretetime system
When computing discretetime systems from continuoustime systems and viceversa, the software uses the conversion method specified in Sample time rate conversion method.
Default: auto
auto
. Computes the sample time
as:0, for continuoustime models.
For models that have blocks with different sample times (multirate models), least common multiple of the sample times. For example, if you have a mix of continuoustime and discretetime blocks with sample times of 0, 0.2 and 0.3, the sample time of the linear model is 0.6.
A discretetime linear system from a continuoustime system.
A discretetime linear system from another discretetime system with a different sample time
0
Use to compute a continuoustime linear system from a discretetime model.
Parameter: SampleTime 
Type: character vector 
Value:
'auto'  Positive finite value  '0' 
Default:
'auto' 
Method for converting the sample time of singlerate or multirate models.
This parameter is used only when the value of Linear
system sample time is not auto
.
Default: ZeroOrder
Hold
ZeroOrder Hold
Zeroorder hold, where the control inputs are assumed piecewise constant
over the sampling time Ts
. For more information, see
ZeroOrder Hold.
This method usually performs better in the time domain.
Tustin (bilinear)
Bilinear (Tustin) approximation without frequency prewarping. The software rounds off fractional time delays to the nearest multiple of the sampling time. For more information, see Tustin Approximation.
This method usually performs better in the frequency domain.
Tustin with Prewarping
Bilinear (Tustin) approximation with frequency prewarping. Also specify the prewarp frequency in Prewarp frequency (rad/s). For more information, see Tustin Approximation.
This method usually performs better in the frequency domain. Use this method to ensure matching at frequency region of interest.
Upsampling when possible, ZeroOrder
Hold otherwise
Upsample a discretetime system when possible and use ZeroOrder
Hold
otherwise.
You can upsample only when you convert a discretetime system to a new faster sample time that is an integer multiple of the sample time of the original system.
Upsampling when possible, Tustin
otherwise
Upsample a discretetime system when possible and use Tustin
(bilinear)
otherwise.
You can upsample only when you convert a discretetime system to a new faster sample time that is an integer multiple of the sample time of the original system.
Upsampling when possible, Tustin
with Prewarping otherwise
Upsample a discretetime system when possible and use Tustin
with Prewarping
otherwise. Also, specify the prewarp
frequency in Prewarp frequency (rad/s).
You can upsample only when you convert a discretetime system to a new faster sample time that is an integer multiple of the sample time of the original system.
Selecting either:
Tustin with Prewarping
Upsampling when possible, Tustin with
Prewarping otherwise
enables Prewarp frequency (rad/s).
Parameter: RateConversionMethod 
Type: character vector 
Value: 'zoh'  'tustin'  'prewarp'  'upsampling_zoh'  'upsampling_tustin'  'upsampling_prewarp' 
Default: 'zoh' 
Prewarp frequency for Tustin method, specified in radians/second.
Default: 10
Positive scalar value, smaller than the Nyquist frequency before
and after resampling. A value of 0
corresponds
to the standard Tustin method without frequency prewarping.
Selecting either
Tustin with Prewarping
Upsampling when possible, Tustin with
Prewarping otherwise
in Sample time rate conversion method enables this parameter.
Parameter: PreWarpFreq 
Type: character vector 
Value: 10 
positive scalar value 
Default: 10 
How the state, input and output names appear in the linear system computed during simulation.
The linear system is a statespace object, and system states and input/output names appear in following statespace object properties:
Input, Output or State Name  Appears in Which StateSpace Object Property 

Linearization input name  InputName 
Linearization output name  OutputName 
State names  StateName 
Default: Off
Show state and input/output names with their path through the
model hierarchy. For example, in the chemical reactor model
,
a state in the Integrator1
block of the CSTR
subsystem
appears with full path as scdcstr/CSTR/Integrator1
.
Show only state and input/output names. Use this option when
the signal name is unique and you know where the signal is location
in your Simulink model. For example, a state in the Integrator1
block
of the CSTR
subsystem appears as Integrator1
.
Parameter: UseFullBlockNameLabels 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
How to label signals associated with linearization inputs and outputs on buses, in the linear system computed during simulation (applies only when you select an entire bus as an I/O point).
Selecting an entire bus signal is not recommended. Instead, select individual bus elements.
You cannot use this parameter when your model has mux/bus mixtures.
Default: Off
Use the signal names of the individual bus elements.
Bus signal names appear when the input and output are at the output of the following blocks:
Rootlevel inport block containing a bus object
Bus creator block
Subsystem block whose source traces back to one of the following blocks:
Output of a bus creator block
Rootlevel inport block by passing through only virtual or nonvirtual subsystem boundaries
Use the bus signal channel number.
Parameter: UseBusSignalLabels 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Check that the pole locations satisfy approximate secondorder bounds on the settling time, specified in Settling time (sec) <=. The software displays a warning if the poles lie outside the region defined by the settling time bound.
This parameter is used for assertion only if Enable assertion in the Assertion tab is selected.
You can specify multiple settling time bounds on the linear system. The bounds also appear on the polezero plot. If you clear Enable assertion, the bounds are not used for assertion but continue to appear on the plot.
Default:
Off for PoleZero Plot block.
On for Check PoleZero Characteristics block.
Check that each pole lies in the region defined by the settling time bound, during simulation.
Do not check that each pole lies in the region defined by the settling time bound, during simulation.
Clearing this parameter disables the settling time bounds and the software stops checking that the bounds are satisfied during simulation. The bounds are also greyed out on the plot.
If you also specify other bounds, such as percent overshoot, damping ratio or natural frequency, but want to exclude the settling time bound from assertion, clear this parameter.
To only view the bounds on the plot, clear Enable assertion.
Parameter:
EnableSettlingTime 
Type: character vector 
Value:
'on'  'off' 
Default:
'off' for PoleZero Plot block,
'on' for Check PoleZero
Characteristics block. 
Settling time, in seconds, of the secondorder system.
Default:
[] for PoleZero Plot block 
1 for Check PoleZero Characteristics
block 
Finite positive real scalar for one bound.
Cell array of finite positive real scalars for multiple bounds.
To assert that the settling time bounds are satisfied, select both Include settling time bound in assertion and Enable assertion.
You can add or modify settling time bounds from the plot window:
To add a new settling time bound, rightclick the plot, and select Bounds > New Bound. Specify the new value in Settling time.
To modify a settling time bound, drag the corresponding bound segment. Alternatively, rightclick the bound and select Bounds > Edit. Specify the new value in Settling time (sec) <.
You must click Update Block before simulating the model.
Parameter:
SettlingTime 
Type: character vector 
Value:
[]  1  finite positive real
scalar  cell array of finite positive real
scalars . Must be specified inside single quotes
('' ). 
Default:
'[]' for PoleZero Plot block,
'1' for Check PoleZero
Characteristics block. 
Check that the pole locations satisfy approximate secondorder bounds on the percent overshoot, specified in Percent overshoot <=. The software displays a warning if the poles lie outside the region defined by the percent overshoot bound.
This parameter is used for assertion only if Enable assertion in the Assertion tab is selected.
You can specify multiple percent overshoot bounds on the linear system. The bounds also appear on the polezero plot. If you clear Enable assertion, the bounds are not used for assertion but continues to appear on the plot.
Default:
Off for PoleZero Plot block. 
On for Check PoleZero Characteristics block. 
Check that each pole lies in the region defined by the percent overshoot bound, during simulation.
Do not check that each pole lies in the region defined by the percent overshoot bound, during simulation.
Clearing this parameter disables the percent overshoot bounds and the software stops checking that the bounds are satisfied during simulation. The bounds are also greyed out on the plot.
If you specify other bounds, such as settling time, damping ratio or natural frequency, but want to exclude the percent overshoot bound from assertion, clear this parameter.
To only view the bounds on the plot, clear Enable assertion.
Parameter:
EnablePercentOvershoot 
Type: character vector 
Value:
'on'  'off' 
Default:
'off' for PoleZero Plot block,
'on' for Check PoleZero
Characteristics block. 
Percent overshoot of the secondorder system.
Default:
[] for PoleZero Plot block 
10 for Check PoleZero Characteristics
block 
Minimum: 0
Maximum: 100
Real scalar for single percent overshoot bound.
Cell array of real scalars for multiple percent overshoot bounds.
The percent overshoot p.o can be expressed in terms of the damping ratio ζ, as:
$$p.o.=100{e}^{\pi \zeta /\sqrt{1{\zeta}^{2}}}.$$
To assert that the percent overshoot bounds are satisfied, select both Include percent overshoot bound in assertion and Enable assertion.
You can add or modify percent overshoot bounds from the plot window:
To add a new percent overshoot bound, rightclick the plot,
and select Bounds > New Bound. Select Percent
overshoot
in Design requirement
type and specify the value in Percent
overshoot <.
To modify a percent overshoot bound, drag the corresponding bound segment. Alternatively, rightclick the bound, and select Bounds > Edit. Specify the new damping ratio for the corresponding percent overshoot value in Damping ratio >.
You must click Update Block before simulating the model.
Parameter:
PercentOvershoot 
Type: character vector 
Value:
[]  10  real scalar between
0 and 100  cell array of real scalars between 0 and
100 . Must be specified inside single quotes
('' ). 
Default:
'[]' for PoleZero Plot block,
'10' for Check PoleZero
Characteristics block. 
Check that the pole locations satisfy approximate secondorder bounds on the damping ratio, specified in Damping ratio >=. The software displays a warning if the poles lie outside the region defined by the damping ratio bound.
This parameter is used for assertion only if Enable assertion in the Assertion tab is selected.
You can specify multiple damping ratio bounds on the linear system. The bounds also appear on the polezero plot. If you clear Enable assertion, the bounds are not used for assertion but continues to appear on the plot.
Default: Off
Check that each pole lies in the region defined by the damping ratio bound, during simulation.
Do not check that each pole lies in the region defined by the damping ratio bound, during simulation.
Clearing this parameter disables the damping ratio bounds and the software stops checking that the bounds are satisfied during simulation. The bounds are also greyed out on the plot.
If you specify other bounds, such as settling time, percent overshoot or natural frequency, but want to exclude the damping ratio bound from assertion, clear this parameter.
To only view the bounds on the plot, clear Enable assertion.
Parameter:
EnableDampingRatio 
Type: character vector 
Value:
'on'  'off' 
Default:
'off' 
Damping ratio of the secondorder system.
Default:
[]
Minimum: 0
Maximum: 1
Finite positive real scalar for single damping ratio bound.
Cell array of finite positive real scalars for multiple damping ratio bounds.
The damping ratio ζ, and percent overshoot p.o are related as:
$$p.o.=100{e}^{\pi \zeta /\sqrt{1{\zeta}^{2}}}.$$
To assert that the damping ratio bounds are satisfied, select both Include damping ratio bound in assertion and Enable assertion.
You can add or modify damping ratio bounds from the plot window:
To add a new damping ratio bound, rightclick the plot and
select Bounds > New Bound. Select Damping ratio
in Design requirement type and specify the
value in Damping ratio >.
To modify a damping ratio bound, drag the corresponding bound segment or rightclick it and select Bounds > Edit. Specify the new value in Damping ratio >.
You must click Update Block before simulating the model.
Parameter:
DampingRatio 
Type: character vector 
Value:
[]  finite positive real scalar between 0 and
1  cell array of finite positive real scalars
between 0 and 1 . Must be specified inside single quotes
('' ). 
Default:
'[]' 
Check that the pole locations satisfy approximate secondorder bounds on the natural frequency, specified in Natural frequency (rad/sec). The natural frequency bound can be greater than, less than or equal one or more specific values. The software displays a warning if the pole locations do not satisfy the region defined by the natural frequency bound.
This parameter is used for assertion only if Enable assertion in the Assertion tab is selected.
You can specify multiple natural frequency bounds on the linear system. The bounds also appear on the polezero plot. If Enable assertion is cleared, the bounds are not used for assertion but continue to appear on the plot.
Default: Off
Check that each pole lies in the region defined by the natural frequency bound, during simulation.
Do not check that each pole lies in the region defined by the natural frequency bound, during simulation.
Clearing this parameter disables the natural frequency bounds and the software stops checking that the bounds are satisfied during simulation. The bounds are also greyed out on the plot.
If you also specify settling time, percent overshoot or damping ratio bounds and want to exclude the natural frequency bound from assertion, clear this parameter.
To only view the bounds on the plot, clear Enable assertion.
Parameter:
NaturalFrequencyBound 
Type: character vector 
Value:
'on'  'off' 
Default:
'off' 
Natural frequency of the secondorder system.
Default:
[]
Finite positive real scalar for single natural frequency bound.
Cell array of finite positive real scalars for multiple natural frequency bounds.
To assert that the natural frequency bounds are satisfied, select both Include natural frequency bound in assertion and Enable assertion.
You can add or modify natural frequency bounds from the plot window:
To add a new natural frequency bound, rightclick the plot and
select Bounds > New Bound. Select Natural
frequency
in Design requirement
type and specify the natural frequency in
Natural frequency.
To modify a natural frequency bound, drag the corresponding bound segment or rightclick it and select Bounds > Edit. Specify the new value in Natural frequency.
You must click Update Block before simulating the model.
Parameter:
NaturalFrequency 
Type: character vector 
Value:
[]  positive finite real scalar 
cell array of positive finite real scalars . Must be
specified inside single quotes ('' ). 
Default:
'[]' 
Save one or more linear systems to perform further linear analysis or control design.
The saved data is in a structure whose fields include:
time
— Simulation times at which the linear systems are
computed.
values
— Statespace model representing the linear system. If
the linear system is computed at multiple simulation times,
values
is an array of statespace models.
operatingPoints
— Operating points corresponding to each linear
system in values
. This field exists only if Save
operating points for each linearization is checked.
The location of the saved data structure depends upon the configuration of the Simulink model:
If the Simulink model is not configured to save simulation output as a single object, the data structure is a variable in the MATLAB workspace.
If the Simulink model is configured to save simulation output as a single object, the
data structure is a field in the Simulink.SimulationOutput
object
that contains the logged simulation data.
To configure your model to save simulation output in a single object, in the Simulink editor, on the Modeling tab, click Model Settings. Then, in the Configuration Parameters dialog box, select the Single simulation output parameter.
For more information about data logging in Simulink, see Export Simulation Data and the Simulink.SimulationOutput
reference page.
Default: Off
Save the computed linear system.
Do not save the computed linear system.
This parameter enables Variable name.
Parameter:
SaveToWorkspace 
Type: character vector 
Value:
'on'  'off' 
Default:
'off' 
Name of the data structure that stores one or more linear systems computed during simulation.
The location of the saved data structure depends upon the configuration of the Simulink model:
If the Simulink model is not configured to save simulation output as a single object, the data structure is a variable in the MATLAB workspace.
If the Simulink model is configured to save simulation output as a single object, the
data structure is a field in the Simulink.SimulationOutput
object
that contains the logged simulation data.
The name must be unique among the variable names used in all data logging model blocks, such as Linear Analysis Plot blocks, Model Verification blocks, Scope blocks, To Workspace blocks, and simulation return variables such as time, states, and outputs.
For more information about data logging in Simulink, see Export Simulation Data and the Simulink.SimulationOutput
reference page.
Default: sys
Character vector.
Save data to workspace enables this parameter.
Parameter: SaveName 
Type: character vector 
Value: sys 
any character vector. Must be specified inside single quotes ('' ). 
Default: 'sys' 
When saving linear systems to the workspace for further analysis
or control design, also save the operating point corresponding to
each linearization. Using this option adds a field named operatingPoints
to
the data structure that stores the saved linear systems.
Default: Off
Save the operating points.
Do not save the operating points.
Save data to workspace enables this parameter.
Parameter: SaveOperatingPoint 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Enable the block to check that bounds specified and included for assertion in the Bounds tab are satisfied during simulation. Assertion fails if a bound is not satisfied. A warning, reporting the assertion failure, appears at the MATLAB prompt.
If assertion fails, you can optionally specify that the block:
Execute a MATLAB expression, specified in Simulation callback when assertion fails (optional).
Stop the simulation and bring that block into focus, by selecting Stop simulation when assertion fails.
For the Linear Analysis Plots blocks, this parameter has no effect because no bounds are included by default. If you want to use the Linear Analysis Plots blocks for assertion, specify and include bounds in the Bounds tab.
Clearing this parameter disables assertion; that is, the block no longer checks that specified bounds are satisfied. The block icon also updates to indicate that assertion is disabled.
In the Simulink model, in the Configuration Parameters dialog box, the Model Verification block enabling parameter lets you enable or disable all model verification blocks in a model, regardless of the setting of this option in the block.
Default: On
Check that bounds included for assertion in the Bounds tab are satisfied during simulation. A warning, reporting assertion failure, is displayed at the MATLAB prompt if bounds are violated.
Do not check that bounds included for assertion are satisfied during simulation.
This parameter enables:
Simulation callback when assertion fails (optional)
Stop simulation when assertion fails
Parameter: enabled 
Type: character vector 
Value: 'on'  'off' 
Default: 'on' 
MATLAB expression to execute when assertion fails.
Because the expression is evaluated in the MATLAB workspace, define all variables used in the expression in that workspace.
No Default
A MATLAB expression.
Enable assertion enables this parameter.
Parameter: callback 
Type: character vector 
Value: ''  MATLAB expression 
Default: '' 
Stop the simulation when a bound specified in the Bounds tab is violated during simulation, i.e., assertion fails.
If you run the simulation from the Simulink Editor, the Simulation Diagnostics window opens to display an error message. Also, the block where the bound violation occurs is highlighted in the model.
Default: Off
Stop simulation if a bound specified in the Bounds tab is violated.
Continue simulation if a bound is violated with a warning message at the MATLAB prompt.
Because selecting this option stops the simulation as soon as the assertion fails, assertion failures that might occur later during the simulation are not reported. If you want all assertion failures to be reported, do not select this option.
Enable assertion enables this parameter.
Parameter: stopWhenAssertionFail 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Output a Boolean signal that, at each time step, is:
True (1
) if assertion succeeds; that is, all bounds are
satisfied
False (1
) if assertion fails; that is, a bound is violated.
The output signal data type is Boolean only if, in the Simulink model, in the Configuration Parameters dialog box, the Implement logic signals as Boolean data parameter is selected. Otherwise, the data type of the output signal is double.
Selecting this parameter adds an output port to the block that you can connect to any block in the model.
Default:Off
Output a Boolean signal to indicate assertion status. Adds a port to the block.
Do not output a Boolean signal to indicate assertion status.
Use this parameter to design complex assertion logic. For an example, see Verify Model Using Simulink Control Design and Simulink Verification Blocks.
Parameter: export 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Open the plot window instead of the Block Parameters dialog box when you doubleclick the block in the Simulink model.
Use this parameter if you prefer to open and perform tasks, such as adding or modifying bounds, in the plot window instead of the Block Parameters dialog box. If you want to access the block parameters from the plot window, select Edit or click .
For more information on the plot, see Show Plot.
Default: Off
Open the plot window when you doubleclick the block.
Open the Block Parameters dialog box when you doubleclick the block.
Parameter: LaunchViewOnOpen 
Type: character vector 
Value: 'on'  'off' 
Default: 'off' 
Open the plot window.
Use the plot to view:
System characteristics and signals computed during simulation
You must click this button before you simulate the model to view the system characteristics or signal.
You can display additional characteristics, such as the peak response time, by rightclicking the plot and selecting Characteristics.
Bounds
You can specify bounds in the Bounds tab of the Block Parameters dialog box or rightclick the plot and select Bounds > New Bound. For more information on the types of bounds you can specify, see the individual reference pages.
You can modify bounds by dragging the bound segment or by rightclicking the plot and selecting Bounds > Edit Bound. Before you simulate the model, click Update Block to update the bound value in the block parameters.
Typical tasks that you perform in the plot window include:
Opening the Block Parameters dialog box by clicking or selecting Edit.
Finding the block that the plot window corresponds to by clicking or selecting View > Highlight Simulink Block. This action makes the model window active and highlights the block.
Simulating the model by clicking . This action also linearizes the portion of the model between the specified linearization input and output.
Adding a legend on the linear system characteristic plot by clicking .
Note
To optimize the model response to meet design requirements specified in the Bounds tab, open the Response Optimizer by selecting Tools > Response Optimization in the plot window. This option is only available if you have Simulink Design Optimization™ software installed.
Open the Response Optimizer to optimize the model response to meet design requirements specified in the Bounds tab.
This button is available only if you have Simulink Design Optimization software installed.
Design Optimization to Meet Step Response Requirements (GUI) (Simulink Design Optimization)
Design Optimization to Meet TimeDomain and FrequencyDomain Requirements (GUI) (Simulink Design Optimization)