RoutingRestrictions:Alpha - Revision history

Orudge: Reformat and update

2011-06-15T16:07:37Z

Reformat and update

← Older revision		Revision as of 16:07, 15 June 2011
Line 1:		Line 1:
		⚫	Enables train routetracing to be restricted according to user criteria.

	=Routing Restrictions=

⚫	Enables train routetracing to be restricted according to user criteria

	2.6 alpha 0 r1078 or later		2.6 alpha 0 r1078 or later
Line 127:		Line 124:
	==Examples==		==Examples==

	See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\| TTDPatch Signalling Guide] for examples how to use routing restrictions (and other signalling stuff).		See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en TTDPatch Signalling Guide] for examples how to use routing restrictions (and other signalling stuff).

	This feature was contributed by Jonathan G. Rennison.		This feature was contributed by Jonathan G. Rennison.
			[[Category:Patches]][[Category:Infrastructure Patches]][[Category:TTDPatch]][[Category:TTDPatch Manual]]

Pm-bot: /* Examples */ no nocache here

2011-06-15T11:34:41Z

Examples: no nocache here

← Older revision		Revision as of 11:34, 15 June 2011
Line 127:		Line 127:
	==Examples==		==Examples==

	See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\| TTDPatch Signalling Guide~~\| nocache~~] for examples how to use routing restrictions (and other signalling stuff).		See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\| TTDPatch Signalling Guide] for examples how to use routing restrictions (and other signalling stuff).

	This feature was contributed by Jonathan G. Rennison.		This feature was contributed by Jonathan G. Rennison.

Pm-bot: style fix

2011-06-15T11:34:14Z

style fix

← Older revision		Revision as of 11:34, 15 June 2011
Line 1:		Line 1:


	=Routing Restrictions=		=Routing Restrictions=
Line 90:		Line 89:
	SE&NE;=Signal in SE direction		SE&NE;=Signal in SE direction

	{\|		\|\|
	!

	NW=West side facing North		NW=West side facing North
Line 129:		Line 127:
	==Examples==		==Examples==

		⚫	See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\| TTDPatch Signalling Guide\| nocache] for examples how to use routing restrictions (and other signalling stuff).
	\|-
⚫	\|See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\|\|TTDPatch Signalling Guide\| nocache] for examples how to use routing restrictions (and other signalling stuff).

	This feature was contributed by Jonathan G. Rennison.		This feature was contributed by Jonathan G. Rennison.

Pm-bot: Bot: Automated text replacement (--= +==)

2011-06-15T11:08:14Z

Bot: Automated text replacement (--= +==)

← Older revision		Revision as of 11:08, 15 June 2011
Line 1:		Line 1:

	'''''Enables train routetracing to be restricted according to user criteria'''''

	=Routing Restrictions=		=Routing Restrictions=
Line 8:		Line 7:
	2.6 alpha 0 r1078 or later		2.6 alpha 0 r1078 or later

	-=Switch=-		==Switch==

	Configuration file: tracerestrict on\|off		Configuration file: tracerestrict on\|off
Line 14:		Line 13:
	Command line: -ZZ		Command line: -ZZ

	-=Description=-		==Description==

	This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.		This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.
Line 91:		Line 90:
	SE&NE;=Signal in SE direction		SE&NE;=Signal in SE direction

	\|\|		{\|
			!

	NW=West side facing North		NW=West side facing North
Line 115:		Line 115:
	==PBS block entered from==		==PBS block entered from==

	When not in a PBS block, the condition ~~"~~Entered tile of the PBS block is...~~"~~ will always return false/prevent a train from passing; the condition ~~"~~Entered tile of the PBS block is not...~~"~~ will always return true/permit a train to pass.		When not in a PBS block, the condition "Entered tile of the PBS block is..." will always return false/prevent a train from passing; the condition "Entered tile of the PBS block is not..." will always return true/permit a train to pass.

	Current technical limitations:		Current technical limitations:
Line 129:		Line 129:
	==Examples==		==Examples==

			\|-
	See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\|TTDPatch Signalling Guide\|nocache] for examples how to use routing restrictions (and other signalling stuff).		\|See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en\|\|TTDPatch Signalling Guide\| nocache] for examples how to use routing restrictions (and other signalling stuff).

	This feature was contributed by Jonathan G. Rennison.		This feature was contributed by Jonathan G. Rennison.

Orudge: 7 revisions

2011-06-12T19:10:35Z

7 revisions

New page

'''''Enables train routetracing to be restricted according to user criteria'''''

=Routing Restrictions=

Enables train routetracing to be restricted according to user criteria

2.6 alpha 0 r1078 or later

-=Switch=-

Configuration file: tracerestrict on|off

Command line: -ZZ

-=Description=-

This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.

This feature does not actually block a train from passing, but merely convinces the train's route finding algorithm that the path is a dead end, if a train does not meet the required criteria.

In essence a restricted signal discourages trains which do not meet the criteria from passing.

The criteria of restricted signals are viewed and set by clicking the 'Routefinding' button at the bottom of the signal gui window [[ExperimentalFeatures:Alpha]].

The available variables which can be tested are:
*Number of train carriages (this includes the locomotive)
*Maximum train speed in mph/kph
*Station of current order
*Station of next order
*Last visited station
*Depot of current order
*Depot of next order
*Total train horsepower
*Total train weight (in tonnes)
*Train cargo (can the train carry/not carry the selected cargo)
*Number of tiles from signal
*Signal status: SW, SE, NW or NE
*Train is/is not searching for a depot
*Entered side of tile
*Tile from which the PBS block was entered

The variable is selected from the drop down box opened by pressing the first button, labeled: 'Variable'.

The comparative operator is then selected from the second button, labeled: 'Op', the default operator for all variables except signal status is 'is'.

The value to which the variable is compared is set by pressing the third button, labeled: 'Value'. If the variable is comparing a depot, station or signal, the mouse icon will change, indicating that you may click on the appropriate tile.

A train will pass the signal if it satisfies the comparison test(s) set.

The share and copy buttons are used to share or copy respectively criteria sets with existing restricted signals by clicking on the button and then the signal to copy/share with.

The criteria set is deleted when the last signal which references it is deleted/reset.

The reset button clears the restriction criteria of a signal, without affecting any shared signals, as if the signal had been deleted and reconstructed.

Restricted signals can be distinguished from non-restricted signals using the landinfo window: the text will include the word: 'Restricted'.

==Boolean Operators==

More than one criteria may be used by the use of one of the boolean operators and, or, or xor.

Or is defined as: one or the other, or both.

Xor is defined as: one or the other, but not both.

This is done by clicking on the and, or or xor buttons.

A boolean operator appears directly before and one indent level to the left of the two criteria it operates on.

Boolean operators can be recursed.

Boolean operators can be removed only if at least one of its criteria is not set, and, upon removal, will be replaced by the one which is set, or a blank criteria if neither is set.

A criteria or boolean operator can be selected by clicking it or the line it is on. It can be then deleted using the delete button, or modified. A blank restriction criteria is indicated by a dash. Any blank or incomplete restriction criteria returns true/allows a train to pass.

==Signal Status==

The signal status criteria test whether one of the up to four signals on a tile is red or green. There are four track directions on which signals can be placed. Which signal status criteria is used indicates which signal to test, as shown below:

/

SW&NW;=Signal in SW direction

SE&NE;=Signal in NE direction

\

SW&NW;=Signal in NW direction

SE&NE;=Signal in SE direction

||

NW=West side facing North

NE=East side facing North

SW=West side facing South

SE=East side facing South

=

NW=North side facing West

NE=North side facing East

SW=South side facing West

SE=South side facing East

Non-existent signals are classified as red.

==PBS block entered from==

When not in a PBS block, the condition "Entered tile of the PBS block is..." will always return false/prevent a train from passing; the condition "Entered tile of the PBS block is not..." will always return true/permit a train to pass.

Current technical limitations:

There is a limit on the number of signal restrictions that can be placed on the map. Max 16,384 objects total, including all sub objects, copied objects, binary operators, etc.

Maximum of 256 restricted signals per sixteenth sector of map. 64x64 area.

Shared restrictions only count once for each criteria/binary operator on the first limit.

These limits may be increased in the future if the need arises.

==Examples==

See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en|TTDPatch Signalling Guide|nocache] for examples how to use routing restrictions (and other signalling stuff).

This feature was contributed by Jonathan G. Rennison.

dmccoy at 20:09, 10 October 2007

2007-10-10T20:09:47Z

@@ Line 25: / Line 25: @@
 The available variables which can be tested are:
-Station of current order
+*Depot of current order
 The variable is selected from the drop down box opened by pressing the first button, labeled: 'Variable'.

dmccoy at 00:57, 2 August 2007

2007-08-02T00:57:35Z

New page

'''''Enables train routetracing to be restricted according to user criteria'''''

=Routing Restrictions=

Enables train routetracing to be restricted according to user criteria

2.6 alpha 0 r1078 or later

-=Switch=-

Configuration file: tracerestrict on|off

Command line: -ZZ

-=Description=-

This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.

This feature does not actually block a train from passing, but merely convinces the train's route finding algorithm that the path is a dead end, if a train does not meet the required criteria.

In essence a restricted signal discourages trains which do not meet the criteria from passing.

The criteria of restricted signals are viewed and set by clicking the 'Routefinding' button at the bottom of the signal gui window [[ExperimentalFeatures:Alpha]].

The available variables which can be tested are:

Number of train carriages (this includes the locomotive)

Maximum train speed in mph/kph

Station of current order

Station of next order

Last visited station

Depot of current order

Depot of next order

Total train horsepower

Total train weight (in tonnes)

Train cargo (can the train carry/not carry the selected cargo)

Number of tiles from signal

Signal status: SW, SE, NW or NE

Train is/is not searching for a depot

Entered side of tile

Tile from which the PBS block was entered

The variable is selected from the drop down box opened by pressing the first button, labeled: 'Variable'.

The comparative operator is then selected from the second button, labeled: 'Op', the default operator for all variables except signal status is 'is'.

The value to which the variable is compared is set by pressing the third button, labeled: 'Value'. If the variable is comparing a depot, station or signal, the mouse icon will change, indicating that you may click on the appropriate tile.

A train will pass the signal if it satisfies the comparison test(s) set.

The share and copy buttons are used to share or copy respectively criteria sets with existing restricted signals by clicking on the button and then the signal to copy/share with.

The criteria set is deleted when the last signal which references it is deleted/reset.

The reset button clears the restriction criteria of a signal, without affecting any shared signals, as if the signal had been deleted and reconstructed.

Restricted signals can be distinguished from non-restricted signals using the landinfo window: the text will include the word: 'Restricted'.

==Boolean Operators==

More than one criteria may be used by the use of one of the boolean operators and, or, or xor.

Or is defined as: one or the other, or both.

Xor is defined as: one or the other, but not both.

This is done by clicking on the and, or or xor buttons.

A boolean operator appears directly before and one indent level to the left of the two criteria it operates on.

Boolean operators can be recursed.

Boolean operators can be removed only if at least one of its criteria is not set, and, upon removal, will be replaced by the one which is set, or a blank criteria if neither is set.

A criteria or boolean operator can be selected by clicking it or the line it is on. It can be then deleted using the delete button, or modified. A blank restriction criteria is indicated by a dash. Any blank or incomplete restriction criteria returns true/allows a train to pass.

==Signal Status==

The signal status criteria test whether one of the up to four signals on a tile is red or green. There are four track directions on which signals can be placed. Which signal status criteria is used indicates which signal to test, as shown below:

/

SW&NW;=Signal in SW direction

SE&NE;=Signal in NE direction

\

SW&NW;=Signal in NW direction

SE&NE;=Signal in SE direction

||

NW=West side facing North

NE=East side facing North

SW=West side facing South

SE=East side facing South

=

NW=North side facing West

NE=North side facing East

SW=South side facing West

SE=South side facing East

Non-existent signals are classified as red.

==PBS block entered from==

When not in a PBS block, the condition "Entered tile of the PBS block is..." will always return false/prevent a train from passing; the condition "Entered tile of the PBS block is not..." will always return true/permit a train to pass.

Current technical limitations:

There is a limit on the number of signal restrictions that can be placed on the map. Max 16,384 objects total, including all sub objects, copied objects, binary operators, etc.

Maximum of 256 restricted signals per sixteenth sector of map. 64x64 area.

Shared restrictions only count once for each criteria/binary operator on the first limit.

These limits may be increased in the future if the need arises.

This feature was contributed by Jonathan G. Rennison.