Technical data

A
model.rtw
A-4
DirectFeedthrough
Does model require its inputs in the MdlOutput function (yes/no)?
NumContStates
Total number of continuous states in the model. Continuous
states appear in your model when you use continuous components
(i.e., an Integrator block) that have state(s) that must be
integrated by a solver such as
ode45.
NumDiscStates
Total number of discrete states in the model. Discrete states
appear in your model when you use discrete components (i.e., a
Unit Delay block) that have state(s). The model state vector,
X, is
of length
NumContStates plus NumDiscStates and contains the
continuous states followed by the discrete states.
NumModes
Length of the model mode vector (modeVect). The mode vector is
used by blocks that need to keep track of how they are operating.
For example, the discrete integrator configured with a reset port
uses the mode vector to determine how to operate when an
external reset occurs.
ZCFindingDisabled
Is zero-crossing event location (finding) disabled (yes/no)?
This is always
yes for fixed-step solvers.
NumNonsampledZCs
Length of the model nonsampled zero-crossing vectors, one for the
zero-crossing signals (
nonsampledZCs) and one for the
zero-crossing directions (
nonsampledZCdirs). Nonsampled
zero-crossings are derived from continuous signals that have a
discontinuity in their first derivative. Nonsampled zero-crossings
only exist for variable step solvers. The Abs block is an example of
a block that has an intrinsic, nonsampled zero-crossing to detect
when its input crosses zero.
NumZCEvents
Length of the model zero-crossing event vector (zcEvents).
NumRWork
Length of the model real-work vector (rwork). Real-work elements
are used by blocks that need to keep track of “real” variables
between simulation steps. An example of a block that uses
real-work elements is the Discrete Sine Wave block, which has
discrete coefficients that are needed across simulation steps.
Table A-1: Model.rtw File Contents (Continued)
Variable/Record Name Description