Replicating Entities on Multiple Paths
Sample Use Cases
The Replicate block enables you to distribute
copies of an entity on multiple entity paths. Replicating entities
might be a requirement of the situation you are modeling. For example,
copies of messages in a multicasting communication system can advance
to multiple transmitters or multiple recipients, as in the fragment
below.
Similarly, copies of computer jobs can advance to multiple computers
in a cluster so that the jobs can be processed in parallel on different
platforms.
In some cases, replicating entities is a convenient modeling
construct. For example, the MAC Controller subsystems in the Ethernet Local Area Network demo
send one copy of an entity for processing and retain another copy
of the same entity for the purpose of observing the state of the channel.
Back to Top
Modeling Notes
Unlike the Output Switch block, the Replicate block
has departures at all of its entity output ports that are not blocked,
not just a single selected entity output port.
If your model routes the replicates such that they
use a common entity path, then be aware that blockages can occur during
the replication process. For example, connecting all ports of a Replicate block, Path
Combiner block, and Single Server block in
that sequence can create a blockage because the server can accommodate
at most one of the replicates at a time. The blockage causes fewer
than the maximum number of replicates to depart from the block.
Each time the Replicate block replicates
an entity, the copies depart in a sequence whose start is determined
by the Departure port precedence parameter. Although all copies
depart at the same time instant, the sequence might be significant
in some modeling situations. For details, see the reference page for
the Replicate block.
Back to Top
 | Combining Entities | | Working with Events |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
Get this Simulink Kit
Store 
