
5 Designing Paths for Entities
5-14
to be notified of the change is the first to advance an entity to the Path Combiner
block. The Input port precedence parameter determines which of the block's entity
input ports is first in the notification sequence. For the list of options, see the online
reference page for the Path Combiner block.
Significance of Input Port Precedence
Consider the sequence of blocks in the figure below, in which a Path Combiner block
merges three small queues into a single large queue.
Suppose the server is busy serving an entity, the single large queue (FIFO Queue4)
is full, and each of the three small queues is nonempty. In this situation, the Path
Combiner block's entity output port is blocked. When the entity in the server departs,
an entity from the large queue advances to the server. The large queue is no longer full,
so its entity input port becomes available. As a result, the Path Combiner block's entity
output port changes from blocked to unblocked. The Path Combiner block uses the Input
port precedence parameter to determine the sequence by which to notify entity input
ports of the change. The sequence of notifications determines which of the three small
queues is the first to advance an entity to the large queue via the Path Combiner block.
The Input port precedence parameter is relevant only when the entity output port
changes from blocked to unblocked; the parameter is irrelevant in other situations. For
example, if the large queue has infinite capacity, or if at most one of the three small
queues is nonempty at any given time during the entire simulation, then all settings for
the Input port precedence produce the same behavior.
Kommentare zu diesen Handbüchern