User guide

12-16
Delays and Timing
module_instance_name, Value = StE
port_name ---> port_name = 10;
8. At time 60 the output transitions to 0.
Pulse control sometimes blurs the distinction between inertial and
transport delays. In this example the results would have been the
same if you also included the +transport_path_delays option.
Specifying Pulse on Event or Pulse on Detect Behavior
Asymmetric delays, such as different rise and fall times for a module
path delay, can cause schedule cancellation problems for pulses.
These problems persist when you specify transport delay and can
persist for a wide range of percentages that you specify for the pulse
control options.
For example for a module that models a buffer, if you specify a rise
time of 4 and a fall time of 6 for a module path delay a narrow value
0 pulse can cause scheduling problems, as illustrated in Figure 12-7.
Figure 12-7 Asymmetric Delays and Scheduling Problems