Difference: EditingHoldModules (5 vs. 6)

Revision 62010-02-04 - KatTrevor

Line: 1 to 1

META TOPICPARENT	name="ArenaGuide"

Editing Hold Modules

Line: 7 to 7

Wait for Signal

This hold stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received an entity leaves the Hold module queue.

Added:

>
>

Consider the example of simulating cars queing at a parking building exit while waiting for their prepaid parking tickets to be approved. The cars ( entities) must wait for the signal 10 to be sent in the simulation. When this signal is sent, one car will proceed through the exit.

Scan for Condition

This hold stores entities in a queue until a condition is satisfied. However, the Hold module ONLY checks this condition WHEN A CALENDAR EVENT OCCURS. If the condition is true then the first entity in the queue may leave the Hold module. This generates a new event and the condition is checked again. Each time the condition is true an entity leaves the Hold module queue.

Line: 18 to 20

This hold stores entities in a queue infinitely while the simulation is running.

Added:

>
>

NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).

-- MichaelOSullivan - 25 Aug 2009

Added:

>
>

Hold_for_signal.PNG:

META FILEATTACHMENT	attachment="Hold_Scan_for_Condition.PNG" attr="h" comment="" date="1265238748" name="Hold_Scan_for_Condition.PNG" path="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" size="10013" stream="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" tmpFilename="" user="KatTrevor" version="1"

Added:

>
>

META FILEATTACHMENT	attachment="Hold_for_signal.PNG" attr="h" comment="" date="1265248904" name="Hold_for_signal.PNG" path="U:\Summer Work\Printscreens\Hold for signal.PNG" size="9848" stream="U:\Summer Work\Printscreens\Hold for signal.PNG" tmpFilename="" user="KatTrevor" version="1"

View topic | History: r9 < r8 < r7 < r6 | More topic actions...