Reactis Simulator enables users to visualize execution of Simulink/Stateflow models. Simulator's user interface is similar to those of traditional debuggers from programming languages: it enables users to execute their models step-by-step (or even block-by-block), as well as set breakpoints. Simulator can also:
Load your model in Reactis and then click the green button in the
tool bar.
Simulator startup consists of three phases: Model import, type inference
and initialization. Model import and type inference may take a significant
amount of time for large models. Watch the bottom left corner of the
Reactis Window for status messages during Simulator startup. If caching is
enabled for a model, the imported model will be stored in a file (with a
.mwi suffix) which means that import can be skipped on subsequent
invocations (if the no modifications were made to the model).
For any data item (Simulink block, signal or Stateflow variable), at any point during a simulation run, you can:
This can be done as follows:
Alternatively, you could generate a test execution report as follows:
Right-click on a Simulink block, Stateflow state, Stateflow transition,
C source line, or Embedded MATLAB source line in the main panel and select
Toggle Breakpoint. You can also right-click on a Simulink or
Stateflow block in the model hierarchy display panel of the main Reactis
window and select Toggle Breakpoint.
Reactis has two primary modes of operation. The current mode of
operation depends on whether Simulator is enabled or disabled.
Certain buttons are disabled in each of the modes. When Simulator
is off, the buttons that control a simulation (play, fast forward,
reverse step, ...) are not active. When Simulator is enabled, any
buttons (and some menu items) related to modifying the .rsi file are
disabled.
This menu item becomes enabled only when Simulator is enabled and
the Coverage, Show Details menu item is selected.
This rectangle appears when a region has been selected for printing
(this is done in the main Reactis panel by holding down the CTRL key, left-clicking and
dragging). To remove the rectangle, select menu item
File, Remove Print Region , or press the Escape (ESC) key.
The probable explanation is that your model was modified after the tests were generated, but before they were run. In this case, feeding in the input values from the test might yield different responses from the model. To update a test suite so that the new model responses are recorded in the tests, load the model and test suite in Simulator and then select Test Suite, Update Outputs...
Another possible explanation for the differences is that the model
contains an S-function that maintains its own state from one call to
the next. (For example, the S-function might modify global or
statically allocated variables.) During the test-generation process
Reactis repeatedly restarts simulations from intermediate model
configurations. In order to restore configurations for S-functions
appropriately, Reactis must be able to extract any persistent state
information the function might have. Reactis can do this if the S-
function adheres to the constraints described in
Chapter Preparing Models for Use with Reactis of the Reactis User's Guide and only uses storage allocated by
mdlInitializeSizes() to store information between calls to
the S-function.