| Contents | Index |
Current operation in discrete-event simulation
currentop
currentop displays the most recent message in the simulation log. If this message represents a dependent operation, the output also includes a message about the most recent independent operation in the simulation log.
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.
A dependent operation is a consequence of an independent operation.
Compare the current operation display with the simulation log:
opts_struct = se_getdbopts;
opts_struct.StartFcn={'step over','step',...
'step', 'currentop','quit'};
sedebug('sedemo_timeout',opts_struct)The output shows that the display of the current operation includes the last entry in the simulation log, which is the current operation. The display also includes the last unindented entry in the simulation log, representing the latest independent operation.


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 |