Route Assignment Table: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
This table enables you to assign a route to an item. Routes are used to tell trains which stations to go to on a track network.
A Route can be manually assigned using the Route option in the change object.<br>


The table has two modes of operation. By default it is in Global mode.
Routes are used to tell trains which stations to go to on a track network.  


'''Global Indexing Mode'''
The Route Assignment Dialog displays a list of all of the Routes that you have specified in your model.


All routes in the model are listed together with their index values (defined at the time the route was created).
In this list of Routes, each Route has a unique index number, which was defined at the time the route was created.  


You use the ">" button to configure an Attribute Reference to select which route you want to assign. The default is a constant one. It is common to use an item attribute which has been set by preceeding train scheduling logic.
== Selector Reference<br> ==


The Delete button clears the route assignment (so no assignment occurs).
Below the Routes list is a "Selector Reference" Attribute. This provides a value for which a matching Route index value is sought.  


Clicking the Options button will display a menu with 2 options:
When an item passes through the Change Object, the Route whose index value matches the value of this Selector Reference Attribute will be assigned to the train item.


Index Value Source: Global
You use the "&gt;" button to configure the Selector Reference Attribute. Its default is a constant value of 1. <br>
selecting this enables you to change to Local Indexing


Export Names
More common would be to use an item attribute which has been set in routine code before the train item arrives at this change object.<br>


Enables you to export the route names and indicies to a text file.
Because the Selector Reference is an Attribute, you can point to an attribute that varies during a model run.  


e.g. You can create an Item Attribute called "Trip_Name". Each item can be given a different trip_name value, and each item will be assigned a different Route when it passes through this change object.<br>


Local Indexing Mode
<br>


In this mode, routes are added and indexed locally to this object. Extra buttons will appear to facilitate this.
== Selector Reference Enables Multiple Choices<br>  ==


You use the ">" button to configure an Attribute Reference to select which route you want to assign. The default is a constant one. It is common to use an item attribute which has been set by preceeding train scheduling logic.
The Selector Reference can be pointed to a Table. This enables a number of routes to be specified and they will be tested sequentially, with the first "accepting" route taken by an item.  


Use the Add button to select a route and add it to the table.
*The reference must be to the entire table.
Likewise Remove will remove the highlighted route from the table.
*The route index values to test are specified in column 1 of the table.  
*The rows in this column should be set to the route IDs to test.


The Options button now has 3 options
== Row Limit Attribute  ==


Index Value Source: Local
When you are using the table-based multiple choice Selector Reference, you can set an additional "row limit" attribute.


Selecting this enables you to change to Global Indexing. Doing this will lose the route/index assignments currently in this object.
You use the "&gt;" button to configure the Row Limit Attribute. Its default is a constant value of 1.  


Rebuild From Visible
This provides a convenient means of limiting the number of rows tested.  
Selecting this will add all routes that are using objects that are visible to the table. This may be useful in track models where several panels contain routes. The change object can be constructed on the panel with the routes, the routes added using this option then the object can be copied (typically into the portals which are the terminals in the network).


Export Names
This is useful because the table needs to be prepared and available during lookahead, during which time rows cannot be added/ removed from a table.  
Enables you to export the route names and indicies to a text file.


The Delete button clears the route assignment (so no assignment occurs). The customised route indicies within this route table are lost.
The default of -1 for the row limit will scan all rows in the table.<br>
----


== Delete Button<br>  ==


The Delete button clears the route assignment function in this change object (so it performs no route


----


<font size="2">idkbase note 10160</font>
----


[[Category:Track]]
[[Category:Track]] [[Category:Context_Help]]
[[Category:Context Help]]

Latest revision as of 17:57, 9 May 2011

A Route can be manually assigned using the Route option in the change object.

Routes are used to tell trains which stations to go to on a track network.

The Route Assignment Dialog displays a list of all of the Routes that you have specified in your model.

In this list of Routes, each Route has a unique index number, which was defined at the time the route was created.

Selector Reference

Below the Routes list is a "Selector Reference" Attribute. This provides a value for which a matching Route index value is sought.

When an item passes through the Change Object, the Route whose index value matches the value of this Selector Reference Attribute will be assigned to the train item.

You use the ">" button to configure the Selector Reference Attribute. Its default is a constant value of 1.

More common would be to use an item attribute which has been set in routine code before the train item arrives at this change object.

Because the Selector Reference is an Attribute, you can point to an attribute that varies during a model run.

e.g. You can create an Item Attribute called "Trip_Name". Each item can be given a different trip_name value, and each item will be assigned a different Route when it passes through this change object.


Selector Reference Enables Multiple Choices

The Selector Reference can be pointed to a Table. This enables a number of routes to be specified and they will be tested sequentially, with the first "accepting" route taken by an item.

  • The reference must be to the entire table.
  • The route index values to test are specified in column 1 of the table.
  • The rows in this column should be set to the route IDs to test.

Row Limit Attribute

When you are using the table-based multiple choice Selector Reference, you can set an additional "row limit" attribute.

You use the ">" button to configure the Row Limit Attribute. Its default is a constant value of 1.

This provides a convenient means of limiting the number of rows tested.

This is useful because the table needs to be prepared and available during lookahead, during which time rows cannot be added/ removed from a table.

The default of -1 for the row limit will scan all rows in the table.

Delete Button

The Delete button clears the route assignment function in this change object (so it performs no route

Retrieved from ‘https://wiki.planimate.com/index.php?title=Route_Assignment_Table&oldid=3836’