Home » railML newsgroups » railml.infrastructure » [railML2/3] <trainDetector> for manually operated stations (<trainDetector>)
[railML2/3] <trainDetector> for manually operated stations [message #2595] Sat, 21 November 2020 18:13 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 117
Registered: March 2016
Senior Member
Dear railML-community,

In the Norwegian railway sector we have the need to map "simple entry" (no:"enkelt innkjør") type stations. These are stations where the local dispatcher is the controller.
He has the following assets to his disposal:
1. Simple entry signals
2. Flags to signal pass, halt or departure operations
3. A white/black pole to indicate the clearance point at the switches.
4. A phone to relay telegrams to the neighbouring stations.

We have mapped this in railML2.4 in the following way:
1. Simple entry signals signal with signal@function="home" and @virtual="false"
2. Flags to signal pass, halt or departure operations with a virtual exit signal with signal@function="exit" and @virtual="true"

What we have forgotten is to model the "train detector" in the local dispatcher. We could solve this in multiple ways, in railML2 (and equivalent in railML3):
1. Introduce the attribute @virtual to <trainDetector>
2. Use <trainDetector@medium. There is a value "optical", but I assume this would be used for an optical sensor not the local dispatchers eyes. So we suggest "other:manual" here.
3. Use the white/black pole that indicates the clearance point, where the trainDetector would have been placed at the switches, with signal and the applicable rulecode.

We would prefer the solution with <trainDetector@medium="other:manual">. This has the advantage that it would require no extensions, just a wiki page update.

See also "Rognan" station as an example in NorRailView: https://railoscope.com/tickets/JJzpl9Qv1W67GEuk?modelId=5d1d f4a872b32b08683bc7fb&selectId=28

The UC here is that this "human" way of working works not very good with computer models, in for instance simulation tools. We need to map the intended functions to the applicable locations. This is done with the virtual exit signal and we need to achieve the same with some sort of train detector elements at the clearance. Else the simulations tools create a deadlock.
What does the community think about this topic? Any feedback is highly appreciated.

Kind regards


Torben Brand
Jernbanedirektoratet
Re: [railML2/3] <trainDetector> for manually operated stations [message #2611 is a reply to message #2595] Tue, 08 December 2020 10:57 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 304
Registered: January 2016
Senior Member
Dear Torben,

thank you for bringing up this topic here in the forum. So, my dear community, please let us know your ideas:
How shall a "manual" (visual) train detection by the local dispatcher be modelled?

Thank you very much and best regards
Christian


Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: [railML2/3] <trainDetector> for manually operated stations [message #2655 is a reply to message #2611] Sat, 30 January 2021 10:59 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 117
Registered: March 2016
Senior Member
Dear Christian and the IS community,

As we have received no feedback I would like to propose the following for
railML2.5 and corresponding for railML3.2:

1. Introduce the attribute @virtual (type boolean) to <trainDetector> as
the item as described is not a physical object but an observation described
in item 2 (the local dispatcher)
And for completeness add
2. Extend the enumeration value list <trainDetector>@medium with the value
«manual» for the local dispatchers manual observation.

If there are no objections or alternate modelling suggestions from the
community I hope Christian will add the proposed items in railML2.5 and 3.2
(no need to rush it into the beta).

--
TOBR
Re: [railML2/3] <trainDetector> for manually operated stations [message #2698 is a reply to message #2655] Fri, 09 April 2021 17:17 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 304
Registered: January 2016
Senior Member
Dear Torben,

thank you for your clarifications and ideas on the railML 2.5 implementation. I filed a Trac ticket #469 [1] for this topic incorporating your solution proposal. Hoping for further feedback from the community, this may be a quickly implemented model enhancement.

[1] https://trac.railml.org/ticket/469

Best regards
Christian


Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railMl2] Proposal for new attribute @switchable in <baliseGroup> and wiki refinement
Next Topic: [railML2] extension suggestion for the element <state> for open time period
Goto Forum:
  


Current Time: Sun May 16 02:05:35 CEST 2021