Delay: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==   MultiServer: Multiple servers in one object  ==
==   Delay: One or more servers in one object  ==


<onlyinclude>[[Image:MultiServerIconLg.jpg]]  
<onlyinclude>[[Image:MultiServerIconLg.jpg]]


In simulation, objects that can hold an item and apply a process delay time before releasing the item are known as '''Servers'''. The Planimate '''MultiServer '''object has the ability to delay one <u>or more</u> items at a time.</onlyinclude>
In simulation, objects that can hold an item and apply a process delay time before releasing the item are known as '''Servers'''.


MultiServers are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together. The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.  
The Planimate '''Delay '''object has the ability to delay one <u>or more</u> items at a time.</onlyinclude>


<br>
Delays are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together. The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.


The number of items that may be held in the MultiServer can be varied in the model over time. This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.
<br>


MultiServer process delays are edited in Interaction View.
The number of items that may be held in the Delay can be varied in the model over time. This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.


During a model run (but not in User Mode) clicking on a MultiServer icon (or its head in "road" mode)&nbsp; enables you to browse its items. You can see:
The process delay is configured via the object's context menu and can be set per item class.
 
During a model run (but not in User Mode) clicking on a Delay's icon (or its head in "road" mode)&nbsp; enables you to browse its items. You can see:


'''Item Entry Time;&nbsp; Item class;&nbsp; Item ID;&nbsp; Time-till-departure.'''
'''Item Entry Time;&nbsp; Item class;&nbsp; Item ID;&nbsp; Time-till-departure.'''


Clicking on a line in this list will show the item details for that item.<br>[[Image:MultiServer_As_Road_with_Data.jpg|center|500px]]
Clicking on a line in this list will show the item details for that item.<br>[[Image:Multiserver As Road with Data.jpg|center|500px]]


=== MultiServer States  ===
=== States  ===


MultiServer Objects have four different states:  
Delay Objects have these states:


[[Image:MultiServer-Idle.jpg]]&nbsp; '''Idle&nbsp;&nbsp; '''No items are currently in the MultiServer.  
[[Image:MultiServer-Idle.jpg]]&nbsp; '''Idle&nbsp;&nbsp; '''No items are currently in the Delay.


[[Image:MultiServer-Busy.jpg]]&nbsp; '''Busy&nbsp;&nbsp; '''At least one item is currently in the MultiServer.  
[[Image:MultiServer-Busy.jpg]]&nbsp; '''Busy&nbsp;&nbsp; '''At least one item is currently in the Delay.


[[Image:MultiServer-Blkd.jpg]]&nbsp; '''Blocked&nbsp;&nbsp; '''One or more items are blocked from leaving the MultiServer.  
[[Image:MultiServer-Blkd.jpg]]&nbsp; '''Blocked&nbsp;&nbsp; '''One or more items are blocked from leaving the Delay.


[[Image:MultiServer-Unav.jpg]]&nbsp; '''Unavailable&nbsp;&nbsp; '''The MultiServer has entered a period of zero server availability.  
[[Image:MultiServer-Unav.jpg]]&nbsp; '''Unavailable&nbsp;&nbsp; '''The Delay has entered a period of zero server availability.


<br>  
'''Stopped'''&npsb;&nbsp; The Delay has been suspended/interrupted by the Control attribute being set to 0.
<br>


''Note: A MultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.''
''Note: A MultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.''


== MultiServer Settings  ==
== Delay Settings  ==


=== Capacity  ===
=== Capacity  ===


Enables the capacity of the MultiServer to be set. <br>The Capacity of a MultiServer may be determined in a range of ways:  
Enables the capacity of the MultiServer to be set. <br>The Capacity of a MultiServer may be determined in a range of ways:


*As a constant value that does not change.  
*As a constant value that does not change.
*By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.  
*By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.
*Using an Attribute reference will enable the capacity to be changed during a model run.
*Using an Attribute reference will enable the capacity to be changed during a model run.


For example, when an item enters the MultiServer the Attribute it is carrying can determine the new MultiServer capacity.
For example, when an item enters the MultiServer the Attribute it is carrying can determine the new MultiServer capacity.


=== Server Limit  ===
=== Control ===
 
This setting enables Planimate® to allocate memory to accommodate the maximum number of servers you expect to be in the MultiServer during the run.
 
This sets a hard limit on how many items can undergo a delay at the MultiServer at the same time.
 
You then use the Capacity setting to vary the capacity dynamically over time, it you wish.
 
You need to ensure that the maximum Capacity you expect to provide is less than or equal to the Server Limit value.
 
If the Capacity value of the multi-server exceeds this Server Limit, the Server Limit is applied.


The maximum specifiable server limit of a MultiServer is 99,999.  
An attribute can stop and resume a Delay. When the control attribute is set to zero, the delay is stopped and all items in the Delay are suspended and resume the delay they were performing when the control attribute becomes non zero.


== MultiServer Options  ==
== Delay Options  ==


=== Show as Road  ===
=== Show as Road  ===


This option enables a MultiServer to animate [[Item]] process delays along a straight line.  
This option enables a Delay to animate [[Item]] process delays along a straight line.


You can adjust the line using the [[Position Exit]] option of the [[Object Edit Menu]].
You can adjust the line using the [[Position Exit]] option of the [[Object Edit Menu]].


Items with varying delay times are displayed overtaking each other and moving at different speeds.  
Items with varying delay times are displayed overtaking each other and moving at different speeds.


Adjust the model's [[Update Interval]] to adjust the smoothness of your animation.
Adjust the model's [[Update Interval]] to adjust the smoothness of your animation.
Line 75: Line 68:
With this option set, you are also able to adjust the number, and spacing of "Lanes" the items can use as they travel along the line. (Lane Selection will be random during a model run).
With this option set, you are also able to adjust the number, and spacing of "Lanes" the items can use as they travel along the line. (Lane Selection will be random during a model run).


=== Pausable 0 Delay ===
=== Pausable 0 Delay ===


{{Breakout|Pauseable Zero Delay Multiservers}}
{{Breakout|Pauseable Zero Delay Delays}}


=== No Blocking between Items Option  ===
=== No Blocking between Items Option  ===


MultiServers have an option to prevent a blocked item from blocking other finished items.  
Delays have an option to prevent a blocked item from blocking other finished items.
 
This makes it act more like a dispatcher when many items are finished and one is blocked.
 
No blocking between items option is on by default for new servers.
 
''This option is on by default. ''
 
If you turn this option off, you create a single exit point for a Delay.


This makes it act more like a dispatcher when many items are finished and one is blocked.  
Then, whenever an item is blocked from leaving a multi-server, ALL subsequent items in the Delay become blocked. This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.


No blocking between items option is on by default for new servers.
== Delay Time  ==


If you turn this option off, you create a single exit point for a MultiServer.  
The delay an item undergoes is specific to its item class. Hence if multiple item classes use a Delay, you need to configure them separately.


Whenever an item is blocked from leaving a multi-server, ALL subsequent items in the MultiServer become blocked.  
The context menu for the object lists all the classes using the object so they can be edited.


This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.  
The delay is set using a Distribution Pattern Dialog.
<br>Refer to Editing Object Properties for information about editing properties common to all objects. <br>


== Multi-server Interaction Editing  ==


The delay an item undergoes is specific to its class and independent of any other activity in the MultiServer.
== Delay Articles  ==


The delay parameter needs to be set separately for each item class that will use it.
<dpl>
category=Object/Delay
notnamespace=Category
notcategory=FAQ
ordermethod=pagetouched
order=descending
</dpl>


To set the delay time, shift to Interaction Edit View and click on the MultiServer.
<br> <br>


A Distribution Pattern Dialog appears enabling the time to be set
== Delay Object Frequently Asked Questions  ==


The time you set pertains only to the item class displayed in the Item Edit Box, whose paths you can see on the screen.
<dpl>
category=FAQ
titlematch=%Multiserver%|%multiserver%|%Multi-server%|%multi-server%
ordermethod=pagetouched
order=descending
</dpl>


<br>Refer to Editing Object Properties for information about editing properties common to all objects. <br><br>
<br>


[[Category:Object/Multiserver]] [[Category:Object]]
[[Category:Object/Multiserver]] [[Category:Object]]

Latest revision as of 12:49, 26 October 2020

  Delay: One or more servers in one object

MultiServerIconLg.jpg

In simulation, objects that can hold an item and apply a process delay time before releasing the item are known as Servers.

The Planimate Delay object has the ability to delay one or more items at a time.

Delays are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together. The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.


The number of items that may be held in the Delay can be varied in the model over time. This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.

The process delay is configured via the object's context menu and can be set per item class.

During a model run (but not in User Mode) clicking on a Delay's icon (or its head in "road" mode)  enables you to browse its items. You can see:

Item Entry Time;  Item class;  Item ID;  Time-till-departure.

Clicking on a line in this list will show the item details for that item.

States

Delay Objects have these states:

MultiServer-Idle.jpg  Idle   No items are currently in the Delay.

MultiServer-Busy.jpg  Busy   At least one item is currently in the Delay.

MultiServer-Blkd.jpg  Blocked   One or more items are blocked from leaving the Delay.

MultiServer-Unav.jpg  Unavailable   The Delay has entered a period of zero server availability.

Stopped&npsb;  The Delay has been suspended/interrupted by the Control attribute being set to 0.

Note: A MultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.

Delay Settings

Capacity

Enables the capacity of the MultiServer to be set.
The Capacity of a MultiServer may be determined in a range of ways:

  • As a constant value that does not change.
  • By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.
  • Using an Attribute reference will enable the capacity to be changed during a model run.

For example, when an item enters the MultiServer the Attribute it is carrying can determine the new MultiServer capacity.

Control

An attribute can stop and resume a Delay. When the control attribute is set to zero, the delay is stopped and all items in the Delay are suspended and resume the delay they were performing when the control attribute becomes non zero.

Delay Options

Show as Road

This option enables a Delay to animate Item process delays along a straight line.

You can adjust the line using the Position Exit option of the Object Edit Menu.

Items with varying delay times are displayed overtaking each other and moving at different speeds.

Adjust the model's Update Interval to adjust the smoothness of your animation.

With this option set, you are also able to adjust the number, and spacing of "Lanes" the items can use as they travel along the line. (Lane Selection will be random during a model run).

Pausable 0 Delay

Pauseable Zero Delay Delays

For full details refer to this page: Pauseable Zero Delay Delays

No Blocking between Items Option

Delays have an option to prevent a blocked item from blocking other finished items.

This makes it act more like a dispatcher when many items are finished and one is blocked.

No blocking between items option is on by default for new servers.

This option is on by default.

If you turn this option off, you create a single exit point for a Delay.

Then, whenever an item is blocked from leaving a multi-server, ALL subsequent items in the Delay become blocked. This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.

Delay Time

The delay an item undergoes is specific to its item class. Hence if multiple item classes use a Delay, you need to configure them separately.

The context menu for the object lists all the classes using the object so they can be edited.

The delay is set using a Distribution Pattern Dialog.
Refer to Editing Object Properties for information about editing properties common to all objects.


Delay Articles




Delay Object Frequently Asked Questions