|
|
|
| R2012a Documentation → SimEvents | |
Learn more about SimEvents |
|
| Contents | Index |
Single step in discrete-event simulation
step
step in
step over
step out
step or step in, at the SimEvents debugger command prompt, advances the simulation by the smallest possible step in the debugger.
step over advances the simulation to the next message at the same level in the simulation log.
step out advances the simulation to the next independent operation that appears in the simulation log.
The figure illustrates the two-level hierarchy of the simulation log to help you distinguish among syntaxes.
An independent operation is one of these operations:
Initialization of the model or any Time-Based Entity Generator blocks in the model. For more information, see Initialization Messages.
Execution of an event on the event calendar. However, if the application executes an event without scheduling it on the event calendar, the event cannot be the basis of an independent operation. To learn which events are on the event calendar, see Role of the Event Calendar.
Detection by a reactive port or a monitoring port of a relevant update in a time-based input signal. You can think of these relevant updates as zero crossings or level crossings. However, if the input signal is an event-based signal or if the input port is not a reactive or monitoring port, the update is not an independent operation.
For more information, see Independent Operations and Consequences in the Debugger.
Learn how you can use SimEvents discrete-event simulation capabilities through these technical resources.
Get free kit| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |