User`s guide

Top-Level Model Coverage Report
19-41
Relational Operator Report Format Explanation
[-tol..0)<
[0..tol]
0 is included in the region
above the relational
boundary.
[-tol..0)>=
[0..tol]
0 is included in the region
above the relational
boundary.
[-tol..0]>
(0..tol]
0 is included in the region
below the relational
boundary.
0 is included below the relational boundary for <= but above the relational boundary for
<. This rule is consistent with decision coverage. For instance:
• For the relation input1 <= input2, the decision is true if input1 is less than or
equal to input2. < and = are grouped together. Therefore, 0 lies in the region below
the relational boundary.
• For the relation input1 < input2, the decision is true only if input1 is less than
input2. > and = are grouped together. Therefore, 0 lies in the region above the
relational boundary.
Saturate on Integer Overflow Analysis
On the Coverage tab, if you select the Saturate on integer overflow coverage metric,
the software creates a Saturation on Overflow analyzed table in the model coverage
report. The software creates the table for each block with the Saturate on integer
overflow parameter selected.
The Saturation on Overflow analyzed table lists the number of times a block saturates
on integer overflow, indicating a true decision. If the block does not saturate on integer
overflow, the table indicates a false decision. Outcomes that do not occur are in red
highlighted table rows.
The following graphic shows the Saturation on Overflow analyzed table for the MinMax
block in the Mixing & Combustion subsystem of the Engine Gas Dynamics subsystem in
the sldemo_fuelsys example model.