ProgrammableSignals:Alpha - Revision history

Orudge: Reformat and update

2011-06-15T16:07:56Z

Reformat and update

← Older revision		Revision as of 16:07, 15 June 2011
Line 1:		Line 1:


	=Programmable Signals=

	Permits user-provided additional conditions for forcing a signal to red.		Permits user-provided additional conditions for forcing a signal to red.

Line 60:		Line 56:

	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: Bot: Automated text replacement (--= +==)

2011-06-15T11:08:34Z

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

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

	'''''Additional user-provided conditions for forcing a signal to red'''''

	=Programmable Signals=		=Programmable Signals=
Line 8:		Line 7:
	2.6 alpha 0 r1646 or later		2.6 alpha 0 r1646 or later

	-=Switch=-		==Switch==

	Configuration file: psignals on\|off		Configuration file: psignals on\|off
Line 14:		Line 13:
	Command line: -ZU		Command line: -ZU

	-=Description=-		==Description==

	This features overrides the normal presignal system, allowing the user to specify that a signal should be red under various conditions.		This features overrides the normal presignal system, allowing the user to specify that a signal should be red under various conditions.

	Unlike [[RoutingRestrictions:Alpha\|routing restrictions]], this feature does nominally block a train from passing, and cannot test any properties of the approaching train. However, with PathBasedSignalling, a train will pass a red signal if it can find a path, so in PBS blocks, the invalid exits must be restricted. On the other hand, entrances to a PBS block can safely be programmed to always red.		Unlike [[RoutingRestrictions:Alpha\| routing restrictions]], this feature does nominally block a train from passing, and cannot test any properties of the approaching train. However, with PathBasedSignalling, a train will pass a red signal if it can find a path, so in PBS blocks, the invalid exits must be restricted. On the other hand, entrances to a PBS block can safely be programmed to always red.

	If you attempt to program an entrance or combo signal, it will be demoted to a normal or exit signal, respectively, until the programming is removed.		If you attempt to program an entrance or combo signal, it will be demoted to a normal or exit signal, respectively, until the programming is removed.
Line 50:		Line 49:
	This returns the number of exit and combo signals that match the specified condition and would affect an entrance or combo signal in the same location as the programmed signal.		This returns the number of exit and combo signals that match the specified condition and would affect an entrance or combo signal in the same location as the programmed signal.

	The ~~"~~Number of (green/red) exit & combo signals~~"~~ tests will count both one-way and two-way signals. The other four will count only one-way signals or only two-way signals, depending on which is selected. The simplest programmed equivalent to the conventional entrance or combo signal is ~~ "~~Number of green exit & combo signals is 0~~"~~.		The "Number of (green/red) exit & combo signals" tests will count both one-way and two-way signals. The other four will count only one-way signals or only two-way signals, depending on which is selected. The simplest programmed equivalent to the conventional entrance or combo signal is "Number of green exit & combo signals is 0".

	==Boolean Operators==		==Boolean Operators==

	Boolean operators work exactly as for [[RoutingRestrictions:Alpha#Boolean_Operators\|routing restrictions]].		Boolean operators work exactly as for [[RoutingRestrictions:Alpha#Boolean_Operators\| routing restrictions]].

	==Signal Status==		==Signal Status==

	Due to technical limitations, the signal referenced by a signal status condition should be a exit or combo signal that would affect a presignal in the same location as the programmed signal. Other than that, signal status works exactly as for [[RoutingRestrictions:Alpha#Signal_Status\|routing restrictions]].		Due to technical limitations, the signal referenced by a signal status condition should be a exit or combo signal that would affect a presignal in the same location as the programmed signal. Other than that, signal status works exactly as for [[RoutingRestrictions:Alpha#Signal_Status\| routing restrictions]].

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

Orudge: 3 revisions

2011-06-12T19:09:51Z

3 revisions

← Older revision	Revision as of 19:09, 12 June 2011
(No difference)

dmccoy at 16:24, 11 March 2008

2008-03-11T16:24:45Z

← Older revision		Revision as of 16:24, 11 March 2008
Line 58:		Line 58:
	==Signal Status==		==Signal Status==

	Due to technical limitations, ~~programmed~~ ~~signals~~ should ~~not~~ ~~depend~~ on ~~signals~~ that would ~~not~~ affect a presignal in the same location as the programmed signal. Other than that, signal status works exactly as for [[RoutingRestrictions:Alpha#Signal_Status\|routing restrictions]].		Due to technical limitations, the signal referenced by a signal status condition should be a exit or combo signal that would affect a presignal in the same location as the programmed signal. Other than that, signal status works exactly as for [[RoutingRestrictions:Alpha#Signal_Status\|routing restrictions]].

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

dmccoy at 20:09, 10 October 2007

2007-10-10T20:09:51Z

← Older revision		Revision as of 20:09, 10 October 2007
Line 25:		Line 25:

	The available variables which can be tested are:		The available variables which can be tested are:
		⚫	*Number of (green/red) exit & combo signals

	Number of (green/red) exit & combo signals		*Number of (one-way/two-way) (green/red) exit & combo signals
		⚫	*Entered side of tile

		⚫	*Signal status: SW, SE, NW or NE
⚫	Number of ~~(one-way/two-way)~~ (green/red) exit & combo signals

⚫	Entered side of tile

⚫	Signal status: SW, SE, NW or NE

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

dmccoy at 16:37, 8 October 2007

2007-10-08T16:37:03Z

New page

'''''Additional user-provided conditions for forcing a signal to red'''''

=Programmable Signals=

Permits user-provided additional conditions for forcing a signal to red.

2.6 alpha 0 r1646 or later

-=Switch=-

Configuration file: psignals on|off

Command line: -ZU

-=Description=-

This features overrides the normal presignal system, allowing the user to specify that a signal should be red under various conditions.

Unlike [[RoutingRestrictions:Alpha|routing restrictions]], this feature does nominally block a train from passing, and cannot test any properties of the approaching train. However, with PathBasedSignalling, a train will pass a red signal if it can find a path, so in PBS blocks, the invalid exits must be restricted. On the other hand, entrances to a PBS block can safely be programmed to always red.

If you attempt to program an entrance or combo signal, it will be demoted to a normal or exit signal, respectively, until the programming is removed.

The criteria of programmed signals are viewed and set by clicking the 'Routefinding' button at the bottom of the signal gui window [[ExperimentalFeatures:Alpha]]. The same window serves for both routing restrictions and signal programming. When both switches are enabled, the window will default to Routing Restrictions. To switch to signal programming, click the button on the far right, which says 'Signal'. To switch back, click that button again, which now says 'Routefinding'.

The available variables which can be tested are:

Number of (green/red) exit & combo signals

Number of (one-way/two-way) (green/red) exit & combo signals

Entered side of tile

Signal status: SW, SE, NW or NE

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 signal, the mouse icon will change, indicating that you may click on the appropriate tile.

A signal will show red if the test(s) set are satisfied.

The share and copy buttons are used to share or copy respectively criteria sets with existing programmed 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 programming of a signal, without affecting any shared signals, as if the signal had been deleted and reconstructed.

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

==Number of ... exit and combo signals==

This returns the number of exit and combo signals that match the specified condition and would affect an entrance or combo signal in the same location as the programmed signal.

The "Number of (green/red) exit & combo signals" tests will count both one-way and two-way signals. The other four will count only one-way signals or only two-way signals, depending on which is selected. The simplest programmed equivalent to the conventional entrance or combo signal is  "Number of green exit & combo signals is 0".

==Boolean Operators==

Boolean operators work exactly as for [[RoutingRestrictions:Alpha#Boolean_Operators|routing restrictions]].

==Signal Status==

Due to technical limitations, programmed signals should not depend on signals that would not affect a presignal in the same location as the programmed signal. Other than that, signal status works exactly as for [[RoutingRestrictions:Alpha#Signal_Status|routing restrictions]].

This feature was contributed by Jonathan G. Rennison.