Spatial Link Scan Depth: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
Line 1: Line 1:
A system attribute limits how deep PL will scan a spatial net looking for the closest route to the target.
A [[system attribute]] limits how deep PL will scan a spatial net looking for the closest route to the target.
 


The attribute needs to be set each time the model is loaded, it is not<br /> saved. The default is 9999999 (ie: dont limit search depth).
The attribute needs to be set each time the model is loaded, it is not<br /> saved. The default is 9999999 (ie: dont limit search depth).


Setting this value means Planimate may not chose the shortest distance<br /> path in a spatial net if it contains more intermediate nodes than an<br /> alternative which is further in distance, and the node limit happens to<br /> be exceeded in scanning the shorter path.
Setting this value means Planimate may not chose the shortest distance<br /> path in a spatial net if it contains more intermediate nodes than an<br /> alternative which is further in distance, and the node limit happens to<br /> be exceeded in scanning the shorter path.


This will be obvious in incorrect animation but should not affect the <br /> item arrival time. In other words, reducing the search depth may<br /> cause PL to chose a route which is not the "shortest". It may also cause<br /> Planimate not to find the correct route at all (if it has too many<br /> intermediate nodes) in which case PL will report a flow error.
This will be obvious in incorrect animation but should not affect the <br /> item arrival time. In other words, reducing the search depth may<br /> cause PL to chose a route which is not the "shortest". It may also cause<br /> Planimate not to find the correct route at all (if it has too many<br /> intermediate nodes) in which case PL will report a flow error.


This attribute has to be set before firing the first item into the spatial net. It doesn't get saved with the model, it resets to a large number when the model is loaded. You can change its setting during the run but probably not something useful to do, if its too low and PL fails to find a target it will stop the modelk with a "no outgoing flow" type message.
This attribute has to be set before firing the first item into the spatial net. It doesn't get saved with the model, it resets to a large number when the model is loaded. You can change its setting during the run but probably not something useful to do, if its too low and PL fails to find a target it will stop the modelk with a "no outgoing flow" type message.
Line 18: Line 14:
<font size="2">idkbase note 16</font>
<font size="2">idkbase note 16</font>


[[Category:Capacity]]
[[Category:Spatial Network]]
[[Category:Spatial Network]]
[[Category:Object/SpatialLink]]
[[Category:Object/SpatialLink]]
[[Category:Runtime Engine]]

Latest revision as of 14:43, 12 January 2008

A system attribute limits how deep PL will scan a spatial net looking for the closest route to the target.

The attribute needs to be set each time the model is loaded, it is not
saved. The default is 9999999 (ie: dont limit search depth).

Setting this value means Planimate may not chose the shortest distance
path in a spatial net if it contains more intermediate nodes than an
alternative which is further in distance, and the node limit happens to
be exceeded in scanning the shorter path.

This will be obvious in incorrect animation but should not affect the
item arrival time. In other words, reducing the search depth may
cause PL to chose a route which is not the "shortest". It may also cause
Planimate not to find the correct route at all (if it has too many
intermediate nodes) in which case PL will report a flow error.

This attribute has to be set before firing the first item into the spatial net. It doesn't get saved with the model, it resets to a large number when the model is loaded. You can change its setting during the run but probably not something useful to do, if its too low and PL fails to find a target it will stop the modelk with a "no outgoing flow" type message.



idkbase note 16