Traveling too slow for this curve
#1
Posted 05 September 2018 - 08:51 PM
What is that message about? What parameter values/settings are necessary to make it go away?
#2
Posted 06 September 2018 - 12:00 AM
Genma Saotome, on 05 September 2018 - 08:51 PM, said:
What is that message about? What parameter values/settings are necessary to make it go away?
Have a look at this thread, and the referenced article for a description of the feature in real life.
As you suggest, perhaps a yard would not have superelevated track, and therefore cars toppling over would not be an issue. Therefore ideally there should be no error messages when traversing small switches or curves in yards.
I can think of two possible ways to solve the problem:
i) Set a minimum curve radius before the alarm indicates. So what would be the maximum curve radius used in a yard, but not on a main line? Would 100m be a safe bet?
ii) Disable the alarm indication on switches. This would solve the problem perhaps for yard switches, but I am not sure how to identify whether a car is on a switch or not.
I suspect that i) is the easiest solution, but happy to consider ii) if somebody can suggest how to identify when a switch is under a wagon.
Thanks
#3
Posted 06 September 2018 - 06:20 AM
I don't see a reason for this message.
Also that's why I don't like OR superelevation, because it works for every track, but in real life that's not the case.
Here I've recorded emergency stop at steep curve adjusted to 160 km/h. Nothing happened:
https://youtu.be/PW8AG3Jf67g?t=3189
#4
Posted 06 September 2018 - 08:43 AM
If it is to remain as a feature then I recommend de-coupling it from whatever assumed cant is used for the display of track (we use only one value for software purposes due to the limits of the 3dmodels for track) and instead tying the calculation to an assumed cant based either on the current speed limit alone (which should be based on the tightest curve) or some ratio of speed limit and current curvature (I expect that ratio would need to be a curve). Surely there are formulas that can be found in the engineering literature that present typical cant amounts for various speeds.
I suspect there are also speed limits set so low as to fall under a practical limit of don't bother... for example, if for whatever reason the speed limit in a switching yard is, say, just 10 mph it's pretty safe to either assume no curve has a cant built into it or that the chance of tipping over on whatever slight cant might be present is actually nill. I do not know what value to suggest for such a limit.
If the track doesn't have an assigned speed limit assume it has no cant (e.g., perhaps it's a route under development).
#5
Posted 06 September 2018 - 08:55 AM
That can happen even without much (or any) super if the curve is tight enough and the train improperly built or handled. But as currently implemented it's not very sensitive to conditions; as noted, low speeds are normal (and required!) in a yard, and even if super is applied to the diverging line of a switch (which OR does) it's not going to matter much over the short distance involved. The two alternatives above are good to think about; another possibility might be to make OR aware of "yard limits" and not apply super (or trigger super-related messages) within them.
#6
Posted 07 September 2018 - 04:33 PM
I have now put a limit in to prevent the message appearing on curves of less then 150m radius. Hopefully this should cover all yard type scenarios.
#7
Posted 07 September 2018 - 06:58 PM
#8
Posted 07 September 2018 - 08:35 PM
IMO we should not be seeing the message in any of those situations.
Does the block of code you are working on have access to the speed limit that is presently governing the whole train?
#9
Posted 08 September 2018 - 01:32 PM
#10
Posted 08 September 2018 - 07:58 PM